Syntax search lemma entry field should not resize

When trying to pick a lemma to use in a syntax search using the drop-down menu as below:

the width of the pick box automatically changes as you scroll down to show the full size of the lemma and its gloss.

This is not - in my opinion - ideal as if you are using the scroll bar to scroll down you suddenly find the cursor over a word (as opposed to the bar) and this is picked for you.

The same is true for the pick menu in Bible Word Study and - I presume - elsewhere.

Could this behaviour be changed to use a horizontal scroll bar when the lemma+gloss won't fit in the default size box?

Graham

Find more posts tagged with

Comments

Dave Hooton

Hmmm. I also hadn't noticed it until I tried g:pros from a post in another forum[:D].

I did not inadvertently pick a word when scrolling with the width changing but noticed that when it had fully re-sized it stayed that way. If I stopped scrolling a word might be selected but you have to click to pick (!) so a horizontal scroll bar would be unnecessary.

Graham Criddle

https://community.logos.com/discussion/comment/166749#Comment_166749

Hmmm. I also hadn't noticed it until I tried g:pros from a post in another forum.

Yes, it was this that made me do something about it.

I found that the box resized both outwards and inwards to match the size of the text.

When scrolling down by clicking the arrow at the bottom of the vertical scroll bar I find myself either clicking on a word inside the "outwardly-extended" box and hence selecting it, or clicking outside the "inwardly-reduced" box and finding my focus has moved to a totally different resource which was behind it.

Graham

Melissa Snyder

https://community.logos.com/discussion/comment/166751#Comment_166751

This is an issue with some suggested match drop-down lists, which may be fixed in the future.

Graham Criddle

https://community.logos.com/discussion/comment/166882#Comment_166882

Hi Melissa

I see that 4.3 B4 has a fix for the bug which caused collection drop-down menus to change width (as you noted at http://community.logos.com/forums/p/14417/246096.aspx#246096)

The problem reported here (change in width of lemma dropdowns in Syntax Search menus) is still present in 4.3 B4.

Was this a different problem or should the fix have extended to this case as well?

Thanks, Graham

Rosie Perera

https://community.logos.com/discussion/comment/246188#Comment_246188

Hi Melissa

I see that 4.3 B4 has a fix for the bug which caused collection drop-down menus to change width (as you noted at http://community.logos.com/forums/p/14417/246096.aspx#246096)

The problem reported here (change in width of lemma dropdowns in Syntax Search menus) is still present in 4.3 B4.

Was this a different problem or should the fix have extended to this case as well?

Thanks, Graham

It's probably the same problem but needed to be fixed in multiple places (who knows: there might still be others which haven't been found). This is likely a case where having a single object with inheritance for the different ways in which it is used could have saved some development time and avoided missing this other instance of the bug.

Melissa Snyder

https://community.logos.com/discussion/comment/246188#Comment_246188

Hi Melissa

I see that 4.3 B4 has a fix for the bug which caused collection drop-down menus to change width (as you noted at http://community.logos.com/forums/p/14417/246096.aspx#246096)

The problem reported here (change in width of lemma dropdowns in Syntax Search menus) is still present in 4.3 B4.

Was this a different problem or should the fix have extended to this case as well?

Thanks, Graham

I'm not sure whether these are the same problem; however, the reason the Collections 'Open' drop-down width issue was addressed was because it caused inadvertent Collection deletions. There is a future case for these other drop-downs, but they don't have the same priority.

Graham Criddle

https://community.logos.com/discussion/comment/246198#Comment_246198

I'm not sure whether these are the same problem; however, the reason the Collections 'Open' drop-down width issue was addressed was because it caused inadvertent Collection deletions. There is a future case for these other drop-downs, but they don't have the same priority.

Thanks Melissa

Absolutely understand that the collections one was higher priority.

Just wanted to flag that this variation was still not resolved in case it was believed that they had all been fixed (which I fully admit wasn't stated in the release notes[:)])

Graham

Rosie Perera

https://community.logos.com/discussion/comment/246198#Comment_246198

I'm not sure whether these are the same problem; however, the reason the Collections 'Open' drop-down width issue was addressed was because it caused inadvertent Collection deletions. There is a future case for these other drop-downs, but they don't have the same priority.

The inadvertent Collection deletions problem was solved a while back by removing the red X when hovering over a collection name on that menu, so you now have to right click on one and choose Delete to delete it. Still, it was annoying to have the list box width change as you were scrolling, because if you clicked twice in rapid succession, you could miss the scroll bar on the second click and dismiss the dropdown. I'm glad this remaining aggravating problem was fixed, but I don't think it was necessarily higher priority than other places in the software where the same problem occurs. It seems to me that fixing them all at the same time would have been more efficient and less error prone, and less likely to leave the other instances indefinitely without ever fixing them.