Hi

You have been allways very clear on your concepts =)


Thanks, but not as accurate as one should be...



> But I'm a pragmatic man so I don't think we have to stick with all AS 
> design choices so...
> I propose you to create a new class: xbpForm() or xbpGetDialog() based 
> on QDialog() to make upon all our get screens easier and compatible with 
> qtDesigner's .ui form loading.
> 

This way you are supporting extensions to Xbase++ language.
XbpHbDialog() or XbpQDialog() seems to be the right name and will base
itself on 
QDialog() instead of QMainWindow(). It will also have a :drawigArea
which will point to itself to facilitate not to rewrite the already tested
code.

So you are supporting Xbase class extension ?
Groups opinion ?

Regards
Pritpal Bedi

-- 
View this message in context: 
http://old.nabble.com/SF.net-SVN%3A-harbour-project%3A-13687--trunk-harbour-tp27290744p27299085.html
Sent from the Harbour - Dev mailing list archive at Nabble.com.

_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to