Hello Everybody First - a good news - I am been able to simulate TBrowse() behavior as far as vertical navigation is concerned. Horizontal navigation - freeze - is practically non-existent in Qt's model/view architect and hence so far I have no clues how to simulate this. Barring "FREEZE" and "FOOTER" everything is working properly. Important to note is that there is no absolutely no memory overhead as is associated with Qt's model/view architect and so is extremely fast rendering has been achieved.
TBrowse.prg has provided me the architect. It could been possible with <::aCellValues> which Przemek thought of and I could exploit it to the maximum. Without <::aCellValues> construct this would have been impossible to achieve this milestone. TBrowse() code is then been modified to XbpBrowse() behavior. So far so good. Second - as I am in a position to provide both TBrowse() and XbpBrowse() approaches, what do you think if I retain both or only XbpBrowse(). Internally, TBrowse() will map itself to XbpBrowse(). Opinions are welcome. Regards Pritpal Bedi -- View this message in context: http://www.nabble.com/QT---HBXBP---XbpBrowse%28%29-vs-TBrowse%28%29-tp24795410p24795410.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
