[<<] [<] Page 1 of 1 [>] [>>] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
other fltk issues
From: "Greg Haerr" ####@####.#### Date: 8 Mar 2000 17:13:29 -0000 Message-Id: <00e601bf8920$02915160$15320cd0@gregh> Shane, I think I finally understand what fltk is doing internally, and why all the strange clipregion klugery. Very late last night I implemented CS_OWNDC dc's, which basically are private DC's that don't need getting and releasing. This was done because fltk is built around X11, and the private DC model is closer to X11. The problem is, that, without private DC's fltk will crash in certain circumstances because ReleaseDC is called twice. (ReleaseDC does nothing for private DC's.) So I added private DC's and now the clock demo runs without crashing. Now, at 2 am I found myself reading the win32 tech manual, and it says: when private dc's are used, the update region is not kept up, the user application has to intersect the update region with the clip region themselves [snip]... Well, when I had SelectClipRgn commented in, nothing ran because it was selecting in a empty region, which clipped all drawing, since I commented out all the other region code. So, tonight, I'm going to add GetUpdateRgn, the only api piece still missing, then add all the region code back in, and I think then everything will be groovy ;-) If you want to get the clock demo running better, you might hack a PeekMessage for Microwindows. Also, I haven't been able to figure out why it draws on top of itself... This also happens with the valuators dial control. I think this might be related to the region clipping, I'm hoping. Regards, Greg | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: other fltk issues
From: ####@####.#### Date: 8 Mar 2000 17:39:26 -0000 Message-Id: <20000308150049.B11763@www.easysolutions.net> Greg, > If you want to get the clock demo running better, you might > hack a PeekMessage for Microwindows. Also, I haven't > been able to figure out why it draws on top of itself... > This also happens with the valuators dial control. I think > this might be related to the region clipping, I'm hoping. > > Regards, > > Greg The strange thing Greg is that only one of the two clocks draws over itself... yet they appear to have the similar drawing routine... very strange. Anyway, that's what I was looking at this morning. I'll probably work on the align text thing, and leave you to the PeekMessage thing. Once you plug in that other function for clipping we'll see how the clock thing does, and if it's still screwed, I'll look through it again. (I think the Round clock is fine, the other one is messed up) Thanks Greg, Shane. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: ####@####.#### > For additional commands, e-mail: ####@####.#### > | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
RE: other fltk issues
From: Greg Haerr ####@####.#### Date: 8 Mar 2000 17:59:06 -0000 Message-Id: <C1962B36D9BBD311B0F80060083DFEFB080CD0@SYS.CenSoft.COM> :The strange thing Greg is that only one of the two clocks draws over :itself... yet they appear to have the similar drawing routine... very :strange. Anyway, that's what I was looking at this morning. Actually, both clocks draw incorrectly. The tabs control may sometimes redraw the background, which is why it appears to work. I'll :probably work on the align text thing, and leave you to the :PeekMessage thing. I tried changing the alignment late last night, without much success. It's probably better to grab some X11 fonts (perhaps the one that fltk-x11 uses, and convert it for Microwindows). Greg : | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: other fltk issues
From: ####@####.#### Date: 8 Mar 2000 18:15:36 -0000 Message-Id: <20000308153659.D11763@www.easysolutions.net> > Actually, both clocks draw incorrectly. The tabs control > may sometimes redraw the background, which is why it > appears to work. No, in the clock demo on my machine, the round clock screws up when drawing, and the standard Fl_Clock does not. Don't know why just now, but do both clocks mess up on your computer? Only one does here. I just checked again, opened up a bunch of clock's of different types, and only the Round clocks messed up. Thanks, Shane. > > > > I'll > :probably work on the align text thing, and leave you to the > :PeekMessage thing. > > I tried changing the alignment late last night, without > much success. It's probably better to grab some X11 > fonts (perhaps the one that fltk-x11 uses, and convert > it for Microwindows). > > Greg > : | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
RE: other fltk issues
From: Rosimildo daSilva ####@####.#### Date: 9 Mar 2000 00:43:15 -0000 Message-Id: <200003090033.QAA04230@www1.xoommail.com> Good show dudes !!! This is looking incredible nice !!!. Rosimildo. ______________________________________________________ Get your free web-based email at http://www.xoom.com Birthday? Anniversary? Send FREE animated greeting cards for any occasion at http://greetings.xoom.com | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
[<<] [<] Page 1 of 1 [>] [>>] |