http://bugs.winehq.org/show_bug.cgi?id=18920
Summary: WhereIsIt shows no search results Product: Wine Version: 1.1.23 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: comdlg32 AssignedTo: wine-bugs@winehq.org ReportedBy: Wintershade@gmail.com CC: bunglehead@gmail.com
When making a search in WhereIsIt, no results are shown. The summary in the status bar finds a number of found items, but no items appear on the list.
Flagged as minor since I don't know which other applications are affected with the new comctl32; however, this is one of the main features of WhereIsIt - this bug renders it almost unusable.
The regression test shows the following info:
475dcb81f58ed8d479ab3a37a811567d583d7701 is first bad commit commit 475dcb81f58ed8d479ab3a37a811567d583d7701 Author: Nikolay Sivov bunglehead@gmail.com Date: Fri Jun 5 13:55:19 2009 +0400
comctl32/listview: Improve column scrolling.
:040000 040000 bfbe0a31d12cf3d01997c50bc4682be7da18246f 99fb1e8668f24b317f26322d58c2dc5989c4bcd0 Mdlls
http://bugs.winehq.org/show_bug.cgi?id=18920
Nikolay Sivov bunglehead@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|comdlg32 |comctl32
--- Comment #1 from Nikolay Sivov bunglehead@gmail.com 2009-06-12 18:34:44 --- Hi, Dorian.
I got some troubles with that patch too, that's why it's reverted in current git.
Could you try to test with your own build?
http://bugs.winehq.org/show_bug.cgi?id=18920
--- Comment #2 from Dorian Faust Wintershade@gmail.com 2009-06-12 18:42:40 --- Hello Nikolay, thank you for your swift answer. I haven't built the current git repository yet, will do so in the morning, I can barely look right now. I'll post results here.
http://bugs.winehq.org/show_bug.cgi?id=18920
--- Comment #3 from Nikolay Sivov bunglehead@gmail.com 2009-06-12 18:50:52 --- (In reply to comment #2)
Hello Nikolay, thank you for your swift answer. I haven't built the current git repository yet, will do so in the morning, I can barely look right now. I'll post results here.
Ok. Here is a reverting commit if you are interested in:
http://source.winehq.org/git/wine.git/?a=commit;h=839b31fccef3961364e5d8458a...
http://bugs.winehq.org/show_bug.cgi?id=18920
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|major |minor
http://bugs.winehq.org/show_bug.cgi?id=18920
--- Comment #4 from Dorian Faust Wintershade@gmail.com 2009-06-13 06:05:07 --- OK, I've compiled the latest Wine from the git repository and it's ok again. Looks like you were right, this should be implemented in a different manner.
Sorry I can't be of more help.
http://bugs.winehq.org/show_bug.cgi?id=18920
Nikolay Sivov bunglehead@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #5 from Nikolay Sivov bunglehead@gmail.com 2009-06-13 06:09:29 --- (In reply to comment #4)
OK, I've compiled the latest Wine from the git repository and it's ok again.
Good.
Looks like you were right, this should be implemented in a different manner.
Yeah, I'm still working on it.
http://bugs.winehq.org/show_bug.cgi?id=18920
Nikolay Sivov bunglehead@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #6 from Nikolay Sivov bunglehead@gmail.com 2009-06-13 06:09:53 --- Closing.
http://bugs.winehq.org/show_bug.cgi?id=18920
Ken Sharp kennybobs@o2.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |kennybobs@o2.co.uk
--- Comment #7 from Ken Sharp kennybobs@o2.co.uk 2009-06-13 08:48:08 --- Why is this marked invalid? It looks like it was fixed, very quickly (if I'm following what happened correctly).
http://bugs.winehq.org/show_bug.cgi?id=18920
--- Comment #8 from Nikolay Sivov bunglehead@gmail.com 2009-06-13 08:51:28 --- (In reply to comment #7)
Why is this marked invalid? It looks like it was fixed, very quickly (if I'm following what happened correctly).
Bug is definitely present in 1.1.23, but was reported after fixing commit. So it's not present at point it was reported.
http://bugs.winehq.org/show_bug.cgi?id=18920
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|INVALID |FIXED
--- Comment #9 from Dmitry Timoshkov dmitry@codeweavers.com 2009-06-14 02:40:50 --- (In reply to comment #8)
Bug is definitely present in 1.1.23, but was reported after fixing commit. So it's not present at point it was reported.
Then it should be marked as a duplicate of an existing bug (if any), or as a fixed one.