I'd suggest to do this after the release if gtwvt is also involved.
On 3/12/09, Przemyslaw Czerpak <dru...@acn.waw.pl> wrote: > On Thu, 12 Mar 2009, Pritpal Bedi wrote: > > Hi, > >> I am almost done with buffered console on GTWVG. >> By "buffered console" I mean all paint operations are >> done in memory and only final output is transferred to >> console on screen. In Clipper parlance you can >> think it synonymous as DispBegin()/DispEnd() but >> not exactly the same. Under this protocol you may >> experience a very smooth window even with verycomplx >> GUI elements, i.e., bitmaps, gradient rectangles, boxes, etc. >> No more flickering. > > GTXWC internally uses bitmap with the whole screen contents > so expose messages are served as simple coping from the internal > screen image to real screen. > I guess you want to make the same in GTWVT/GTWVG plus change > save/rest screen methods to operate on bitmaps instead of > character buffers. > Am I right? > Or maybe you are thinking about sth different? > Please note that using CTWin like API in practice eliminates > SAVESCREEN/RESTSCREEN making the whole code much simpler. > GTWVW was addressing this aspect. > >> It may need some tweaking in the existing code which >> primarily exploits overlapping windows as with >> SaveScreen() | RestScreen() mechanism. One has to >> upgrade his code to use multiple consoles. I have a demo >> in place to show this. > > As long as user does not try to manipulate the contents of > the screen buffer returned by savescreen then it should not > cause any problems. Anyhow some window oriented GTs like > CTWIN will not work correctly because they use own itenral > buffers which are character oriented. They will have to be > modified to work with bit map screen buffers what is not easy > job but it's possible. Though probably it will be easier to > leave CTW as is and create new similar GT for GTWVG and other > GTs which will operate on bitmaps. > >> My question is: How many of you are using GTWVG and are >> willing to adopt to new prorocol. Believe me, it will be very >> little effort to change the exiting code but the results will be >> truely rewarding. Once this is done, I may think to port >> GTWVW in GTWVG if get a substantial number of confirmations >> which may persuade me to port GTWVW. > > I think that many people will find it as very interesting. > >> So please post your vote here under this thread so that I could >> make up my mind to port GTWVW. Please note, the number >> must be substancial. > > I use Windows Harbour builds very seldom so I'm not good person to > answer but looking at xharbour.news I'm finding that many people are > intersting in GTWVW port. > > best regards, > Przemek > _______________________________________________ > Harbour mailing list > Harbour@harbour-project.org > http://lists.harbour-project.org/mailman/listinfo/harbour > _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour