Hi Pritpal,
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
No, I'm not thinking in GUI or controls. Also, a "window" - as per this context - is not a separate GUI window, it's simply a output area which is handled separately, and the actual representation can vary, and _may_ be a GUI a window, but this is up to the GT, but it may be just a subarea inside the regular 80x25 console screen.
point of view. As I know nothing about GTTRM I cannot comment about it.
Please check contrib/hbct/tests/ctwtest.prg to see how CT windowing works. This is exactly what I have in mind, with per-window buffers as an addition.
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.
I vote no. You've added a few new functions and some GTWVT specific additions, which are barely scratching the surface of this feature IMO. There is no need to rush, let's think about it. Brgds, Viktor _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
