> This means that a developer needs to change every ROW, COL value to X, > Y and add the WIDTH value.
Personally, I did some tests in the past with hwgui and used the text based coordinates as multipliers of font height and width... WIDTH value can be calculated... code can be taken from the GET system, since it calculates the screen area to use... just multiply by font width.. PICTURE are a problem since there is non compatibility with Qt... I don't use complex picture string, just some "@!"... VALID and WHEN are a completely diffent subject since you have to create a layer that handles object focus... more, I did not understand if there is already a system (hbxbp???) to interface memory variables with "widgets" Example, setting a variable value inside a widget is "easy"... but then the widget must set the new value back, possibly in a clipper compatible way.... Or otherwise we should change programing paradigm, a new style of programming, at least the screen interface... > And what about tbrowses, achoices, prompts, > menus? Well, if they were incapsulated in your functions, you may try to adapt them to hbqt... In the long end, it would be difficult to adapt an old application without serious changes in the code.... Francesco _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
