[ACK] Collection search box shrinks when entering non-matching characters

Graham Criddle

This is with 6.2 beta 4 on Windows 8.1

I have the Collections tool open and click the "Open" button to search for one of my collections.

When I enter a search string which matches one of my collections everything is fine

When I enter a search string which doesn't match, the drop-down menu contracts

The screencast at http://screencast.com/t/GOkoLzDrcv demonstrates this

Find more posts tagged with

Comments

Keep Smiling 4 Jesus :)

This is with 6.2 beta 4 on Windows 8.1

Also happens in 6.2 Beta 4 on Windows 7, but not OS X 10.10.2

Keep Smiling [:)]

Rosie Perera

Yeah, it's done that forever. It is kind of odd, but it's never really bothered me. The width is wide enough to show the content of the listbox, and when nothing matched, the content is nil so the width can shrink. It probably doesn't need to shrink as there's nothing wrong with showing a too-wide empty list box.

Since this only happens when you type in characters that don't match any of your collections, and there's nothing getting truncated in the narrow width listbox, I'm guessing they will decide this isn't worth their spending time fixing. Unless there's one or two lines of code doing this intentionally that they decide really don't need to be there and can just be yanked out without breaking anything.

Angela Murashov

When I enter a search string which doesn't match, the drop-down menu contracts

This is a Windows only issue. I'll create a case for a Developer to take a look at it [:)]

Graham Criddle

https://community.logos.com/discussion/comment/712008#Comment_712008

When I enter a search string which doesn't match, the drop-down menu contracts

This is a Windows only issue. I'll create a case for a Developer to take a look at it

Thanks Angela

Nice to know we have some unique issues on Windows[:D]

Graham

Dave Hooton

https://community.logos.com/discussion/comment/712008#Comment_712008

Not fixed in Beta 3

Angela Murashov

https://community.logos.com/discussion/comment/721913#Comment_721913

Not fixed in Beta 3

We will update this thread once the issue is fixed.