From: Miguel <mig...@te...> - 2002-11-25 01:58:33
Attachments:
edittool.diff
|
Subject pretty much says it all, the context menu triggered by the right mouse button in the Notation View was not reappearing when you selected a different EditTool with it (at least for me). The attached simple fix seems to work. -- Miguel |
From: Guillaume L. <gla...@te...> - 2002-11-25 10:14:01
|
On Monday 25 November 2002 02:58, Miguel wrote: > Subject pretty much says it all, the context menu triggered by the > right mouse button in the Notation View was not reappearing when you > selected a different EditTool with it (at least for me). The > attached simple fix seems to work. Which version of Qt are you using ? It works here (3.0.5, have yet to test = at=20 home with 3.1), and exec() is the right method to call, AFAICT. =2D-=20 Guillaume http://www.telegraph-road.org |
From: Miguel <mig...@te...> - 2002-11-25 12:10:38
|
> Which version of Qt are you using ? It works here (3.0.5, have yet > to test at home with 3.1), and exec() is the right method to call, > AFAICT. 3.0.5. It turns out the problem is quite harder to reproduce than I had thought, though by the moment I've only been able to reproduce it with ->exec() and not with ->popup(). As to which one is the right method to call, I admit I've barely done any KDE or Qt programming, but in the examples in the Qt documentation QPopupMenu::exec() seems to be used only when the popup is going to be destroyed immediately afterwards, while popup()'s usage is similar to the one intended by EditTool, AFAICT. -- Miguel |
From: Guillaume L. <gla...@te...> - 2002-11-25 14:26:07
|
On Monday 25 November 2002 13:10, Miguel wrote: > As to which one is the right method to call, I admit I've barely done > any KDE or Qt programming, but in the examples in the Qt > documentation QPopupMenu::exec() seems to be used only when the popup > is going to be destroyed immediately afterwards, while popup()'s > usage is similar to the one intended by EditTool, AFAICT. I'm not sure of that. The Qt docs says exec() is to show the menu=20 synchronously, i.e. to get a user selection on it immediately, and then=20 return. popup() is to just show the menu without asking the user for a=20 selection in it. Can you try to update to Qt 3.0.6 ? =2D-=20 Guillaume http://www.telegraph-road.org |
From: Mark K. <mk...@co...> - 2002-11-25 18:37:15
|
Hi, I hope you guys won't jump to some version of Qt that isn't supported with an RPM for Redhat. If you do, you'll leave guys like me that are dependant on RPM's behind. Maybe I'm out to lunch here. Just worried. Mark -----Original Message----- From: ros...@li... [mailto:ros...@li...]On Behalf Of Guillaume Laurent Sent: Monday, November 25, 2002 2:14 AM To: ros...@li... Subject: Re: [Rosegarden-devel] [PATCH] Context menu was not reappearing in the Notation View On Monday 25 November 2002 02:58, Miguel wrote: > Subject pretty much says it all, the context menu triggered by the > right mouse button in the Notation View was not reappearing when you > selected a different EditTool with it (at least for me). The > attached simple fix seems to work. Which version of Qt are you using ? It works here (3.0.5, have yet to test at home with 3.1), and exec() is the right method to call, AFAICT. -- Guillaume http://www.telegraph-road.org ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Rosegarden-devel mailing list Ros...@li... https://lists.sourceforge.net/lists/listinfo/rosegarden-devel |
From: Chris C. <ca...@al...> - 2002-11-26 09:46:23
|
Mark Knecht wrote: > I hope you guys won't jump to some version of Qt that isn't supported > with an RPM for Redhat. If you do, you'll leave guys like me that are > dependant on RPM's behind. If we did, it would be by accident and we'd be depending on guys like you to point out our mistake. We haven't even officially moved away from Qt 2 yet, although we seem to be having a spot of bother with it lately. It's certainly unfortunate for you that all these errors with the new config stuff are cropping up just as you're trying to build afresh on your new machine. Please bear with us, we'll get the glitches ironed out before long. We certainly aren't consciously disregarding the requirements of people using RedHat or Qt 3.x or GNOME or whatever else, we just have trouble testing all the possible combinations ourselves. Chris |
From: Mark K. <mar...@at...> - 2002-11-26 11:33:18
|
Chris, Glad to hear this. Don't worry too much about the build problems. I'm=20 surprised we're having them, but I understand it's a complicated process= ,=20 and really the Achilles Heal of Linux. We just have to deal with it. Thanks, Mark On Tuesday 26 November 2002 01:45 am, Chris Cannam wrote: > Mark Knecht wrote: > > I hope you guys won't jump to some version of Qt that isn't supported > > with an RPM for Redhat. If you do, you'll leave guys like me that are > > dependant on RPM's behind. > > If we did, it would be by accident and we'd be depending on guys > like you to point out our mistake. We haven't even officially > moved away from Qt 2 yet, although we seem to be having a spot of > bother with it lately. > > It's certainly unfortunate for you that all these errors with the > new config stuff are cropping up just as you're trying to build > afresh on your new machine. Please bear with us, we'll get the > glitches ironed out before long. We certainly aren't consciously > disregarding the requirements of people using RedHat or Qt 3.x or > GNOME or whatever else, we just have trouble testing all the > possible combinations ourselves. > > > Chris > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Get the new Palm Tungsten T > handheld. Power & Color in a compact size! > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en > _______________________________________________ > Rosegarden-devel mailing list > Ros...@li... > https://lists.sourceforge.net/lists/listinfo/rosegarden-devel |