Hello Przem, Viktor <<< BTW When we verify that current TBrowse is working correctly I plan to make some internal reorganization and separate screen output for easier creating GUI TBrowse subclasses. >>>
Good thoughts. Please keep in mind, while rearranging, which I am sure you must already have thought of, that all screen output functions must be converted to methods of Tbrowse and from within those methods, GT functions be called. This Multi-GT protocols will be easier to manage and subclassing will be easier. For example, DispOut(...) is spead in the whole Tbrowse code. It will be nice to call ::DispOut() which will be responsible to call direct GT functions. I know this has some speed penalty, but it will help to move to Multi-GT and GUI easily and faster. Regards Pritpal Bedi, INDIA-USA -- View this message in context: http://www.nabble.com/TBrowse-subclassing-vs-HIDDEN-vars-tp17258042p17265654.html Sent from the Harbour - Dev mailing list archive at Nabble.com. _______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
