Re: Pro's and Contra's fom Resources or Coded screens
Posted: Fri Aug 04, 2017 4:42 pm
Here is the problem. If you look at the examples, they usually do not use resources. Suddenly we have a new problem. We have to determine which type of resource control to use and redefine for the command function. It takes extra time to figure this out.
I use almost all resources. My screens are large and complex, and this keeps them accurate. However, it would help to have all the docs include the proper control syntax for an .rc file along with the REDEFINE commands. tBar is a perfect example ... it changed with the many wonderful improvements from what was originally in docs and samples.
Antonio, relative spacing is still a guessing game. I do have a challenge for you. All the examples are always with just a few controls, but in business applications, they are far more complex. Try this: Build a DIALOG ( not Window ) with 30 controls of various types ( labels, text fields, list boxes, radio controls, comboboxes, browse, etc ). Even using your relative positioning for @ commands, 1) Are all of the controls aligned properly on the horizontal lines, 2) Are all input fields of the same height, 3) Is the same font used in all of them, and 4) Are all column positions matching ? My experience in the past was that sizes varied, and different relative positions had to be used to get proper alignment. Again .. in the business world we input a huge amount of data on a single screen, very much unlike the simple samples we test with in FWH. It is precisely these problems that have prevented me from using the @ syntax.
Tim
I use almost all resources. My screens are large and complex, and this keeps them accurate. However, it would help to have all the docs include the proper control syntax for an .rc file along with the REDEFINE commands. tBar is a perfect example ... it changed with the many wonderful improvements from what was originally in docs and samples.
Antonio, relative spacing is still a guessing game. I do have a challenge for you. All the examples are always with just a few controls, but in business applications, they are far more complex. Try this: Build a DIALOG ( not Window ) with 30 controls of various types ( labels, text fields, list boxes, radio controls, comboboxes, browse, etc ). Even using your relative positioning for @ commands, 1) Are all of the controls aligned properly on the horizontal lines, 2) Are all input fields of the same height, 3) Is the same font used in all of them, and 4) Are all column positions matching ? My experience in the past was that sizes varied, and different relative positions had to be used to get proper alignment. Again .. in the business world we input a huge amount of data on a single screen, very much unlike the simple samples we test with in FWH. It is precisely these problems that have prevented me from using the @ syntax.
Tim