From: Dave F. <dav...@co...> - 2004-04-09 02:33:05
|
On Thursday 08 April 2004 05:19 pm, joakim verona wrote: > I was wondering if anybody else was trying to compile jazz with wx 2.5.1. > > Im trying because I wanted to try to get rid of the anoying redraw-flicker > you get when scrolling a pianowin or trackwin. > > In wx 2.5, there is a wxBufferedPaintDC that is supposed to fix the > redraw flicker. You might want to try breaking the window down into smaller widgets. It might work. :) I figure I'd like to see a separate widget for each track, and then have a TrackPanel or something that arranges the tracks. It's on my list, of nobody gets to it first, but it's quite a ways down, and I'm not exactly a graphics programmer. :( > jazz wont currently compile agains 2.5, and I think its because of the > xrc stuff. This is a good possibility, since the xrc that's in our source tree is from wx2.4, right? You might want to go into configure.in and set it up to use a local xrc, if that's the problem. Then you can compile the xrc that's in wx2.5's source tree instead of the one in ours. I copied this back to the sourceforge mailing list. ;) Dave -- Visit my website! http://www.davefancella.com/?event=em With a rubber duck, one's never alone. -- "The Hitchhiker's Guide to the Galaxy" |
From: Patrick E. <pa...@pa...> - 2004-04-09 15:35:52
|
On Thursday 08 April 2004 18:19, joakim verona wrote: > I was wondering if anybody else was trying to compile jazz with wx > 2.5.1. > > Im trying because I wanted to try to get rid of the anoying > redraw-flicker you get when scrolling a pianowin or trackwin. > > In wx 2.5, there is a wxBufferedPaintDC that is supposed to fix the > redraw flicker. I think it would solve the problem if we just draw to a memoryDC first, and then blit to the window when the paint event is requested. I believe the Buffered classes in 2.5 just make is slightly simpler to draw, but coding up one of those classes would be pretty easy as far as I can see. You'd create a class that makes a wxMemoryDC in a constructor and writes to that. Later, the destructor would blit the resulting bitmap to a wxClientDC. Patrick |
From: joakim v. <jo...@ve...> - 2004-04-10 08:29:36
|
Yes, I was originally going to code it that way, I guess I should. (just a small note, when I first made the port this method wasnt possible because the OnPaint message didnt work, you could only derive the OnDraw method. I changed the drawing to be based on the OnPaint message now, and it seems to work) But there is another wx2.5 benefit. There is a gtk2 port for wx 2.5. This means proper unicode support is possible. Gtk1.2 apps don't work very well with Swedish characters, which is my native language. The GTK1.2 apps in rh9 look very unimpressive in non english utf-8 locales, for instance Audacity. So I'm going to give it a try to get it compiling in 2.5 without breaking it in 2.4. We can use the wx version variable from configure to ifdef versions of code. Cheers, /Joakim Patrick Earl wrote: >On Thursday 08 April 2004 18:19, joakim verona wrote: > > >>I was wondering if anybody else was trying to compile jazz with wx >>2.5.1. >> >>Im trying because I wanted to try to get rid of the anoying >>redraw-flicker you get when scrolling a pianowin or trackwin. >> >>In wx 2.5, there is a wxBufferedPaintDC that is supposed to fix the >>redraw flicker. >> >> > >I think it would solve the problem if we just draw to a memoryDC >first, and then blit to the window when the paint event is requested. >I believe the Buffered classes in 2.5 just make is slightly simpler >to draw, but coding up one of those classes would be pretty easy as >far as I can see. You'd create a class that makes a wxMemoryDC in a >constructor and writes to that. Later, the destructor would blit the >resulting bitmap to a wxClientDC. > > Patrick > > |
From: Dave F. <dav...@co...> - 2004-04-10 08:47:48
|
Well, in keeping in the spirit of calling for major upgrades to fix minor problems... Why don't all you Swedes just speak English instead? ;) Jokes aside, wxGTK has had experimental GTK2 support for awhile, even in the 2.4 branch. Are you using your own built wxGTK or RedHat's provided package? The Mandrake package is compiled with GTK2 support, and I've loaded Audacity up with other languages and slobbered over the beautiful fonts. Makes me wish I knew Russian or something, you know? Such pretty letters.... And then I couldn't quit the application because I don't know "Close" in Russian. ;) (You *might* be able to install Mandrake's RPM on your RedHat system. I've had it work successfully using RedHat packages on Mandrake, so if you don't mind accidentally trashing your RPM database you could give it a shot) Anyway, you just: ./configure --enable-gtk2 I believe. ./configure --help will show the option somewhere in there. So if you're using your own built wxGTK, I'd try recompiling it with GTK2 support first and playing with localizing Jazz as it is. That said, we will eventually need to support wxGTK2.6. But consider that to get the best localization of Jazz we either have to tell users to compile wxGTK2.5 (experimental at best), or to compile wxGTK2.4 rather than use their distro-provided package that's probably compiled against GTK1.2. Dave On Saturday 10 April 2004 01:29 am, joakim verona wrote: > Yes, I was originally going to code it that way, I guess I should. > > (just a small note, when I first made the port this method wasnt > possible because > the OnPaint message didnt work, you could only derive the OnDraw method. > I changed the drawing to be based on the OnPaint message now, and it > seems to work) > > But there is another wx2.5 benefit. > > There is a gtk2 port for wx 2.5. This means > proper unicode support is possible. > > Gtk1.2 apps don't work very well with Swedish characters, which is my > native language. > The GTK1.2 apps in rh9 look very unimpressive in non english utf-8 locales, > for instance Audacity. > > So I'm going to give it a try to get it compiling in 2.5 without > breaking it in 2.4. > > We can use the wx version variable from configure to ifdef versions of > code. > > Cheers, > /Joakim > > Patrick Earl wrote: > >On Thursday 08 April 2004 18:19, joakim verona wrote: > >>I was wondering if anybody else was trying to compile jazz with wx > >>2.5.1. > >> > >>Im trying because I wanted to try to get rid of the anoying > >>redraw-flicker you get when scrolling a pianowin or trackwin. > >> > >>In wx 2.5, there is a wxBufferedPaintDC that is supposed to fix the > >>redraw flicker. > > > >I think it would solve the problem if we just draw to a memoryDC > >first, and then blit to the window when the paint event is requested. > >I believe the Buffered classes in 2.5 just make is slightly simpler > >to draw, but coding up one of those classes would be pretty easy as > >far as I can see. You'd create a class that makes a wxMemoryDC in a > >constructor and writes to that. Later, the destructor would blit the > >resulting bitmap to a wxClientDC. > > > > Patrick > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > jazzplusplus-devel mailing list > jaz...@li... > https://lists.sourceforge.net/lists/listinfo/jazzplusplus-devel -- Visit my website! http://www.davefancella.com/?event=em There are many intelligent species in the universe, and they all own cats. |
From: joakim v. <jo...@ve...> - 2004-04-10 11:32:27
|
Dave Fancella wrote: >Well, in keeping in the spirit of calling for major upgrades to fix minor >problems... > >Why don't all you Swedes just speak English instead? > > Heh, that would be a downgrade :-P But I agree with your point, wx 2.5 should not be a requirement at this point. ...and the availability of gtk 2 support in wx 2.4 nullifies my second point I guess. hmmm. I guess I'll go back to drawing dialogs then. Anyway, a tidbit of information for you, there is a "no sequencer for gtk availabel" on lad right now. /Joakim >;) > >Jokes aside, wxGTK has had experimental GTK2 support for awhile, even in the >2.4 branch. Are you using your own built wxGTK or RedHat's provided package? >The Mandrake package is compiled with GTK2 support, and I've loaded Audacity >up with other languages and slobbered over the beautiful fonts. Makes me >wish I knew Russian or something, you know? Such pretty letters.... And >then I couldn't quit the application because I don't know "Close" in Russian. >;) (You *might* be able to install Mandrake's RPM on your RedHat system. >I've had it work successfully using RedHat packages on Mandrake, so if you >don't mind accidentally trashing your RPM database you could give it a shot) > >Anyway, you just: >./configure --enable-gtk2 >I believe. ./configure --help will show the option somewhere in there. So if >you're using your own built wxGTK, I'd try recompiling it with GTK2 support >first and playing with localizing Jazz as it is. That said, we will >eventually need to support wxGTK2.6. But consider that to get the best >localization of Jazz we either have to tell users to compile wxGTK2.5 >(experimental at best), or to compile wxGTK2.4 rather than use their >distro-provided package that's probably compiled against GTK1.2. > >Dave > > >On Saturday 10 April 2004 01:29 am, joakim verona wrote: > > >>Yes, I was originally going to code it that way, I guess I should. >> >>(just a small note, when I first made the port this method wasnt >>possible because >>the OnPaint message didnt work, you could only derive the OnDraw method. >>I changed the drawing to be based on the OnPaint message now, and it >>seems to work) >> >>But there is another wx2.5 benefit. >> >>There is a gtk2 port for wx 2.5. This means >>proper unicode support is possible. >> >>Gtk1.2 apps don't work very well with Swedish characters, which is my >>native language. >>The GTK1.2 apps in rh9 look very unimpressive in non english utf-8 locales, >>for instance Audacity. >> >>So I'm going to give it a try to get it compiling in 2.5 without >>breaking it in 2.4. >> >>We can use the wx version variable from configure to ifdef versions of >>code. >> >>Cheers, >>/Joakim >> >>Patrick Earl wrote: >> >> >>>On Thursday 08 April 2004 18:19, joakim verona wrote: >>> >>> >>>>I was wondering if anybody else was trying to compile jazz with wx >>>>2.5.1. >>>> >>>>Im trying because I wanted to try to get rid of the anoying >>>>redraw-flicker you get when scrolling a pianowin or trackwin. >>>> >>>>In wx 2.5, there is a wxBufferedPaintDC that is supposed to fix the >>>>redraw flicker. >>>> >>>> >>>I think it would solve the problem if we just draw to a memoryDC >>>first, and then blit to the window when the paint event is requested. >>>I believe the Buffered classes in 2.5 just make is slightly simpler >>>to draw, but coding up one of those classes would be pretty easy as >>>far as I can see. You'd create a class that makes a wxMemoryDC in a >>>constructor and writes to that. Later, the destructor would blit the >>>resulting bitmap to a wxClientDC. >>> >>> Patrick >>> >>> >>------------------------------------------------------- >>This SF.Net email is sponsored by: IBM Linux Tutorials >>Free Linux tutorial presented by Daniel Robbins, President and CEO of >>GenToo technologies. Learn everything from fundamentals to system >>administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click >>_______________________________________________ >>jazzplusplus-devel mailing list >>jaz...@li... >>https://lists.sourceforge.net/lists/listinfo/jazzplusplus-devel >> >> > > > |
From: Dave F. <dav...@co...> - 2004-04-10 11:58:19
|
On Saturday 10 April 2004 04:32 am, joakim verona wrote: > Anyway, a tidbit of information for you, there is a "no sequencer for > gtk availabel" on lad right now. I'm sure there's a Qt/GTK flamewar in there somewhere about artistic ability and competence... If I were to add to the discussion, all I'd be able to add is that all the Qt sequencers we do have are suffering from a combination of feature creep and bug overload. :( I'm having a hard time believing RoseGarden will ever be stable again. Heh. So, any of them willing to come over and help? ;) Dave -- Visit my website! http://www.davefancella.com/?event=em Yow! Now we can become alcoholics! |
From: joakim v. <jo...@ve...> - 2004-04-10 14:52:34
|
Dave Fancella wrote: >On Saturday 10 April 2004 04:32 am, joakim verona wrote: > > >>Anyway, a tidbit of information for you, there is a "no sequencer for >>gtk availabel" on lad right now. >> >> > >I'm sure there's a Qt/GTK flamewar in there somewhere about artistic ability >and competence... If I were to add to the discussion, all I'd be able to add >is that all the Qt sequencers we do have are suffering from a combination of >feature creep and bug overload. :( I'm having a hard time believing >RoseGarden will ever be stable again. Heh. > >So, any of them willing to come over and help? ;) > > Well, since the thread has now escalated into flame-armageddon, I thought I'd wait until the dust has settled a bit :-P But I agree with you concerns. A sequencer doesnt necessarily have to be lacking in features, but the features present should be sequencer features. I cant find a sequencer with good scripting support for instance, which I really feel would be very useful(like the csound people do for instance, building songs with python scripts) This is a feature I would like to build using, for instance Swig, to generate wrappers around the Jazzpp midi track classes to use within python, ruby, or whatever, scripts. Cheers, /Joakim >Dave > > > |
From: joakim v. <jo...@ve...> - 2004-04-10 11:40:06
|
Dave Fancella wrote: > >You might want to try breaking the window down into smaller widgets. It might >work. :) I figure I'd like to see a separate widget for each track, and >then have a TrackPanel or something that arranges the tracks. It's on my >list, of nobody gets to it first, but it's quite a ways down, and I'm not >exactly a graphics programmer. :( > > > I,ve been thinking along those lines too. For example, the keyboard in the pianowin should be its own widget in its own pane. The drawing of the main event area wont benefit from a split though, only double buffering will help. This is because the flicker is caused by the graphics not being completely redrawn within a vertical refresh cycle. At least thats what I think. /Joakim |