[Bug 27983] New: Starcraft 2 Editor: Newly created items in the trigger treeview don't get marked for renaming.
http://bugs.winehq.org/show_bug.cgi?id=27983 Summary: Starcraft 2 Editor: Newly created items in the trigger treeview don't get marked for renaming. Product: Wine Version: 1.3.25 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comctl32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: florian(a)fkoeberle.de When you create in the Starcraft 2 Editor a new variable, folder, action, function etc. in the trigger tree the newly created item doesn't get marked for renaming. Workaround: - Press F2 once you created an item: This will mark the item for renaming. The bug doesn't occur with native comctl32. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=27983 --- Comment #1 from Nikolay Sivov <bunglehead(a)gmail.com> 2011-09-17 09:36:10 CDT --- Some message sequence problem most likely or notifications mess. Please attach +treeview,+tid with empty treeviews preferably when you try to add first item to it. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=27983 --- Comment #2 from Florian <florian(a)fkoeberle.de> 2011-09-20 07:18:05 CDT --- I did some tests adding a "variable" to an empty trigger view: The selection for renaming works correctly if I add it to an empty trigger view. If the treeview isn't empty the bug does still occur. I also noticed that the bug only occurs if I use the Contextmenu to add variables. The bug does not occur if I use the toolbar buttons to add a variable. I created a log of the following situation: 1.) I loaded a map with an empty trigger editor window (except the huge library tree at the top left). 2.) I used wc to determine the size of the log: 566483 3251660 44599636 3.) I created a variable using the context menu: I got successfully asked to choose a name and named it "first variable". 4.) I used wc to determine the size of the log: 597497 3445445 47171060 5.) I created a second variable using the context menu and the bug occured. 6.) I forgot to run wc but nothing much got printed to command line like it used to happen after I chose a name. 7.) I created a third variable using a button and I got successully asked to choose a name. I named it "third variable". 8.) I used wc to determine the size of the log: 639645 3711687 50672335 Since the compressed log is to large (1.2 MB) to attach it I will send it to you via email. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=27983 Daniel Jelinski <djelinski1(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |djelinski1(a)gmail.com --- Comment #3 from Daniel Jelinski <djelinski1(a)gmail.com> 2012-10-17 03:16:15 CDT --- The context menu message sequence was improved some time ago. Is this still an issue in current wine? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=27983 Florian <florian(a)fkoeberle.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED --- Comment #4 from Florian <florian(a)fkoeberle.de> 2012-10-17 17:15:41 CDT --- I tested the current git version and it worked. The bug does no longer occur. The git version I used for testing was 29b39020f789fad042824822b5aa05ec0470438a. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=27983 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #5 from Alexandre Julliard <julliard(a)winehq.org> 2012-10-26 13:30:32 CDT --- Closing bugs fixed in 1.5.16. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
participants (1)
-
wine-bugs@winehq.org