Misspellings in 'Find Type' dialog

[Stokes]

I don't know how many other people find this rather annoying but when you misspelled in the 'Find Type' dialog in Jade 6 it still found what you wanted most of the time. In Jade 7 this has changed.

For example if you go to the RootSchema class browser and push F4, then type "FileNa" - In Jade 7 this will not be found. But in Jade 6 it will come up with FileNode. I liked the way Jade 6 worked where it was a bit more lenient

[BeeJay]

I'd not noticed this change in behaviour but it would seem the old Jade 6 behaviour was a better user experience keeping the focus on the last matched entry rather than resetting back to the top of the list.

Perhaps put a contact in Parsys regarding the change in behaviour and see what they have to say about the new behaviour.

Cheers,
BeeJay.

PS: I changed the subject for this topic to more accurately reflect the IDE functionality in question.

[Stokes]

Thanks for that BeeJay - will log this with Parsys and let you know what they say

[BeeJay]

Now that you've brought it to my attention and I'm more aware of the change in behaviour, I probably had been noticing it and just not realising that it had changed from the Jade 6 behaviour..... probably because I've been on Jade 7 for so long now that I'd already adjusted to the 'new normal' for this behaviour....

Of course Murphy's Law dictates that now I'll keep encountering the 'misbehaviour' and getting more annoyed by it now that I know what it used to be like.

Cheers,
BeeJay.

[Stokes]

This is the formal reply I got from Parsys (patched in 7.0.10 & 7.1):

Formal Reply
The find types dialog was changed so that if the text entered did not match any name in the list, the current selection in the list box was removed. This was intentional to indicate to the user the name could not be found.

This behaviour will remain, however a change has been made so that the currently displayed names will remain in view rather than reset the list to display from the beginning.


Not ideal but an improvement. I think if the name could not be found it would be better just to display a message <Class not found> or something like that at the top of the list box