Re: Pro's and Contra's fom Resources or Coded screens
Posted: Sat Aug 05, 2017 7:27 pm
Carlos,
I actually have 3 dialogs for the large screens, and the user selects which one to use. This is a saved value, so it is only done once. So, for an Invoice dialog, there would be:
INVOICE ( 1024 x 768 )
INVOICEw ( Widescreen - 1920 x 1080 )
INVOICEl ( Tablet - designed for the 10.8 " Surface 3. Though it has a 1920 x 1280 resolution, that is too small to see, so controls are larger )
Any popup or lookup dialogs are 1024 x 768 and only the one is needed. Some capabilities are turned off on a tablet so there is no ....l option.
I know this seems like a lot of work, but it's only done one time, and adjustments are minor. The layouts are not responsive, but remember this is for screens that may have 30 or 40 controls on one dialog.
Marc,
As you can see above, there is one setting for each of 3 display options. I have not had a need for more than that. So ... if I modify an .rc, it automatically is picked up in the new build. All of my testing is done building within Visual Studio 2017, so that means about 15 to 20 seconds to update compiles, link, and display the new program. Releases use the MSFT libraries, but are built with a make file. I also do a build with xHarbour ( builder ). These are all a single keypress from within UE Studio ... so management is really fast and simple.
I don't know that an xbrowse would work out. I'd love to have dialogs be responsive/dynamic but I do have the challenge out there to do it with a heavily populated data screen and have it work well. If someone can show us @ command useage with 30 to 60 controls on a resizeable dialog, that handles it all well, then we certainly should explore a way to create using them ...
Tim
I actually have 3 dialogs for the large screens, and the user selects which one to use. This is a saved value, so it is only done once. So, for an Invoice dialog, there would be:
INVOICE ( 1024 x 768 )
INVOICEw ( Widescreen - 1920 x 1080 )
INVOICEl ( Tablet - designed for the 10.8 " Surface 3. Though it has a 1920 x 1280 resolution, that is too small to see, so controls are larger )
Any popup or lookup dialogs are 1024 x 768 and only the one is needed. Some capabilities are turned off on a tablet so there is no ....l option.
I know this seems like a lot of work, but it's only done one time, and adjustments are minor. The layouts are not responsive, but remember this is for screens that may have 30 or 40 controls on one dialog.
Marc,
As you can see above, there is one setting for each of 3 display options. I have not had a need for more than that. So ... if I modify an .rc, it automatically is picked up in the new build. All of my testing is done building within Visual Studio 2017, so that means about 15 to 20 seconds to update compiles, link, and display the new program. Releases use the MSFT libraries, but are built with a make file. I also do a build with xHarbour ( builder ). These are all a single keypress from within UE Studio ... so management is really fast and simple.
I don't know that an xbrowse would work out. I'd love to have dialogs be responsive/dynamic but I do have the challenge out there to do it with a heavily populated data screen and have it work well. If someone can show us @ command useage with 30 to 60 controls on a resizeable dialog, that handles it all well, then we certainly should explore a way to create using them ...
Tim