> In your gif, once you select the choose function, the dropdown list has to clear the elements, could this be a factor?
Not sure what you mean, which elements? Theoretically, the number of objects and variables in the project should not affect system expressions like "choose" at all.
Another possibility is that its actually Chrome that causes these freezes (as Asmodean suggested in his comment), because it does something as I type, like performs a spell check. I disabled the spell check yesterday, but I can't tell yet if it helped or not..
I'm referring to the # of elements in the dropdown list.
I'm wondering if the issue lies in how each of those elements are removed from the list, and I was wondering if that removeChildCall is involved.
To further explain:
In my video example, the blank project has an element list of 1, while the larger project has an element list equal to the total # of groups in the entire project, as the dropdown list shows every single entry, but sorts based on the entries that match closest.
In your gif, you see how the list remains even when you are at "choo"?
This is why I mentioned the preference to set the specificity of the dropdown list to the top (10,20,etc) entries.
When I'm at "choo" while typing, I'd personally only want "choose" and "chooseindex" to populate in the dropdown list, not "clocktext". This is now a list of 2, which presumably would make clearance of the dropdown list much smoother (if that's at all a factor).
(Scrolling all the way to the bottom of the list)
If all entries are populated in the list regardless of what's typed then as a project grows, so does this list.
Of course this doesn't mean it's the issue, but if I had the option to set the dropdown list limit to: 20
And then performed the same test I showed in the video, and I saw an improvement, I'd like to think that suggests the element count in the dropdown list is involved.