Hi

>Exactly what I had in mind.

This almost requires a rewrite of almost all the methods
of TBrowse just rendering subclassing futile. It is because
of DispOut | DispOutAt methods scattered all over. 
In the past I had suggested to corner these calls to a 
method of Tbrowse but the idea was declined, probably,
for the reason of performance, because of one more 
layer to GT calls.

I plan this extension for GTQTC++ family of GT's.

BTW Tbrowse class is fairly stable at this moment so we can 
take a chance to organise it as above and then subclass to 
hb_Tbrowse. Then it will be only a couple of methods to 
rewrite in subclass .

Regards
Pritpal Bedi


-- 
View this message in context: 
http://www.nabble.com/Alternate-line-colors-for-tbrowse-tp23233265p23237147.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

Reply via email to