Hello Viktor <<< You have to think about GTs where the windows are not separated physically, but handled inside one common buffer (GTTRM). Just like in CTWIN. Also, the whole low level API needs to be extended with window handles otherwise there is no way to write anywhere else than the selected window. >>>
I think I could not get your point from the very begining. GTWVW exactly does the same as I posted and you confirmed that this appears to be near your approach. Anyhow, I do not know about a single buffer and windowing. Did you check /contrib/gtwvg/tests/demogwg.prg and opened its first menu option which opens a big window with 3 browsers, 2 get entries and other GUI stuff? There you can move around either by tabs or mouse click. Is that the same in concept you have in your mind? How far CTWIN matches/differs your point of view. As I know nothing about GTTRM I cannot comment about it. Even if this multi-window concept does not match your imagination, do it becomes candidate for incusion in the core? This I may need to extend GTWVG. If it does not harm or interfere with existing layers, I vote for its inculsion in the core code. Regards Pritpal Bedi -- View this message in context: http://www.nabble.com/Multi-Window-GT---New-Implementation-tp17855569p17864416.html Sent from the Harbour - Dev mailing list archive at Nabble.com. _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
