Differences

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

--- hasproperty [2020/06/27 19:31] – admin
+++ hasproperty [2020/10/04 13:49] – admin
@@ Line 41: / Line 41: @@
 That is a valid question for sure! The answer is: the community of TAD users would settle on these conventions. We will have a separate section that publishes these conventions and they can be quite extensive. You would need to follow those conventions if you want to ensure that you are leaving behind information that can be examined coherently by future users of your TAD model
-**Where are these conventions for describing //"has"// properties?**\\
+**The 'Has' editor**\\
+When you double  click on that row containing the 'has' properties in the GUI (be it for //Objects// or //Class//) a larger editor is shown, which will allow you to create each section in its own separate line in the editor. You would still need to give the two double commas to identify that the section is ended; at the end of its line.
+So the above example would be seen in the editor as following:
+<code>
+floor,marble,,
+skirting,granite
+</code>
+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.
+**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!
 **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.

Press F1 inside the application to read context-sensitive help directly in the application itself
← ∈

Differences

Page Tools