Search message disappears before anybody can read it -- set minimum time of life for fleeting items

[jidanni]

I do CTRL+f and search for "modified".
Some window pops up for 0.1 second and disappears before I can read
it.

I look at the invoking shell's STDERR and there is nothing there
either.

Nor is there a 'console' window where I might have a chance to see
what it said.

It couldn't have said "No results" because I really did modify
something.

Therefore I hereby declare the search command broken.

[Don-vip]

Thanks for your report, however your ticket is incomplete and therefore not helpful in its current form.

Please add all needed information according to this list:

• The required parts of the Status Report from your JOSM.
  • Please, use Report Bug from Help menu and copy & paste.
• Describe what behaviour you expected.
• Describe what did happen instead.
• Describe if and how the issue is reproducible.
• Add any relevant information like error messages or screenshots.

To ensure that all technical relevant information is contained, create new tickets by clicking in JOSMs Main Menu on Help → Report Bug.

Remember: This is a generic notice so we don't need to write the same stuff again and again. It may only apply in parts to the specific case!

[Klumbumbus]

Thats the progess bar window which closes very fast again as you probably have a small dataset.

Try searching for "dsakhubcaklhs" and you'll see this window staying open together with the "no results found" window.

[jidanni]

Indeed.
But I believe faster is not always better.
In fact I'm sure the "pro designers" all set a minimal time too for such items. At least 1/2 a second.
That way users would all see a uniform pattern of a fleeting progress bar and not some static electricity etc. unknown blip.

[jidanni]

In the Objects window, if one right clicks search key/value, or
key/value/type, on an item that has <13 different>, some message appears
then disappears before one can read it.

Yes the user should not have tried it. But he will never know and think
that it must be some bug.

Also the message could be printed in some console or STDERR so one
could check later.