Viktor <<<<< Okey, I see what you mean, but my opinion is still the same regarding window selection. Window selection should be a separate command IMO. >>>>>
Sure this can be if we guarantee that end-user will not click on window#2 while our code is executing on window#3. We need a mechanism to detect which window has the INPUT focus and which window has the DISPLAY focus. This holds good for current Clipper GT commands. What if we need to open a browser at the corner of the screen which is auto scrolling while user has clicked on window where he is entering a record ? We need to devise a mechanism to tie a GT command to a window/GT either FORCED or AUTO DETECTED. This way we retain the Clipper compatibility as well as controlled behavior. <<<<< We're not extending (which essentially means changing) existing CA- Cl*pper functions as a rule in Harbour. >>>>> Believe me, I too do not want to change half-a-million lines of source code. But surely I love to modify certain parts to adjust to multi-GT. I did this with Xbase++ and I was 95% success. What eluded me 5% was Xbase++ faulty message dispatching which I could never synchronize and which eventually led me to drop development on that platform. I even incorporated GUI interface on their consoles just like I did with GTWVT. The result was a magnificent power in my applns. Since then I ever wished to have the same magic in (x)Harbour which, now, appears to be materialized. <<<<<<<< nOldWnd := hb_gtwvg_WSelect( nDetails ) DispOut(...) hb_gtwvg_WSelect( nMyOtherWindow ) DispOut(...) hb_gtwvg_WSelect( nOldWnd ) >>>>>>>>> This is what code dictates. In real world it is the user who dictates. What is the fun of having multi-windows where user has no control to work in. If this is the case then I do not see any deficiency in using CT window functions. <<<<<<<<< Since apps are usually using one window at a time, switching between them this way is not a performance or coding problem. >>>>>>>>> Please read above. <<<<<<<<< As an alternative, you can also implement such thing locally for your GT: hb_gtwvg_DispOut( nMyWindow, "hello" ) >>>>>>>>> Our goal is to transfer as much code to the GT core. For sure some components will be relevant on the local GT but even to accomlish so base GT code must have the necessary construct to support it. And this is what Przemek is doing. He pointed out that right now only GTTRM is supporting multi-windows. Just study it and you will realize the immense possibilities it offers. Let him finish with GTWVG and I will extend demo program how it will be used in real world. Regards Pritpal Bedi, INDIA-USA -- View this message in context: http://www.nabble.com/2007-12-07-11%3A39-UTC%2B0100-Przemyslaw-Czerpak-%28druzus-at-priv.onet.pl%29-tf4961411.html#a14227419 Sent from the Harbour - Dev mailing list archive at Nabble.com. _______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
