Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
hasproperty [2020/06/30 20:32] adminhasproperty [2023/04/22 20:59] (current) – external edit 127.0.0.1
Line 53: Line 53:
 As there are only two sections, the second section need not end in the double-commas. As you can see; it is now much easier to properly edit the //has// property thru the editor; instead of typing in directly into the GUI -- the space there is limited and you may strain your eyes. As there are only two sections, the second section need not end in the double-commas. As you can see; it is now much easier to properly edit the //has// property thru the editor; instead of typing in directly into the GUI -- the space there is limited and you may strain your eyes.
  
-**Where are these conventions for describing //"has"// properties?**\\+**Using a database to store properties**\\ 
 +If the very first field in a particular property is //db// then TAD assumes that particular field is inside an external database. This is [[databases|described separately here]] 
 + 
 +**Where are other conventions for describing //"has"// properties?**\\
 They are being made and will get cooperatively edited and published on one of the TAD websites. Till such time, you can give your valuable feedback and for all you know; your way of describing flooring, skirting etc may become the standard! They are being made and will get cooperatively edited and published on one of the TAD websites. Till such time, you can give your valuable feedback and for all you know; your way of describing flooring, skirting etc may become the standard!
  
 **What about earlier versions of TAD?**\\ **What about earlier versions of TAD?**\\
 Models made in earlier versions of TAD will have no problem being loaded in this version. In fact, in the earlier version you could still use such //has// properties -- b ut in those versions you would have to manually type it out in the ARDELA editors of the class and object -- wherever you felt like enriching. From version 6.8 onwards it has a convenient GUI for you to describe the //'"has"// property. That ensures uniformity among TAD users and more chances of it getting standardized right across all architects. Models made in earlier versions of TAD will have no problem being loaded in this version. In fact, in the earlier version you could still use such //has// properties -- b ut in those versions you would have to manually type it out in the ARDELA editors of the class and object -- wherever you felt like enriching. From version 6.8 onwards it has a convenient GUI for you to describe the //'"has"// property. That ensures uniformity among TAD users and more chances of it getting standardized right across all architects.

Press F1 inside the application to read context-sensitive help directly in the application itself
Last modified: le 2023/04/22 20:59