[GRANTED]Programmable <AutoText> + Labels = Joyful AutoLabel

[marcdurant]

Hi Tommy-

Glad you like the new capabilities. The LayOut team was just wrapping up our design meetings for the new feature when you started this thread back in May. We still have a list of features that we'd like to add to the tool, so feel free to share any ideas you have after you've had some time to get familiar with LO 2015.

-m

[Bruce Watt]

I would like a custom AutoText that would create consecutive numbers and automatically update if an additional Autotext would be inserted within the existing set. ( to reflow the numbers after the new insertion)

Let me explain,

All my drawings have a title and a number, (Site Plan / 1, Block Plan / 2, Ground Floor Plan / 3 etc) At times I have to insert other drawings within the existing set of drawings and thus I have to re number all drawings after the new insertions. I could use point ie 1.1, 1.2, 1.3 to accomplish this but prefer to keep it simple. I hope that make sense.

[marcdurant]

Hi Bruce-

If you envision having one of the these tags per page, then what you describe may be possible with the current PageNumber Auto-Text tags. However, if you'd like to sequentially number multiple drawings on a page, then it's not possible with the current system. Could you clarify?

Thanks,
Marc

[Bruce Watt]

@marcdurant said:

Hi Bruce-

If you envision having one of the these tags per page, then what you describe may be possible with the current PageNumber Auto-Text tags. However, if you'd like to sequentially number multiple drawings on a page, then it's not possible with the current system. Could you clarify?

Thanks,
Marc

Hi Marc,

Thanks for your reply,

There is more than 1 per page. (when referencing; page number and then separate drawing number within the page) The indexing system would have to keep track of all instances across all pages. Would that be possible?

[marcdurant]

If there's more than one per page I don't see a way to achieve it with the current system. I'll add this to the feature request list if it isn't there already.

Thanks,
Marc

[Bruce Watt]

@marcdurant said:

If there's more than one per page I don't see a way to achieve it with the current system. I'll add this to the feature request list if it isn't there already.

Thanks,
Marc

Thanks for the clarification,

I guess the indexing system would be like the page numbering system but not related to the pages. The indexing system would relate to each other instance of that specific ''index autotext'. This system in addition to the above, could possibly relate to the location on the page vertically or horizontally or clockwise or anti clockwize or manual override.

TommyK; Sorry to hyjak the thread.

[TommyK]

@bruce watt said:

TommyK; Sorry to hyjak the thread.

No problem! This sounds like a good place for your query.

@marcdurant said:

We still have a list of features that we'd like to add to the tool, so feel free to share any ideas you have after you've had some time to get familiar with LO 2015.
-m

Well, if you insist!

1. Not really a feature request, but cleaning up what is existing. I notice that fundamentally, you add <autotext> into the label string, and LO just replaces that autotext with the relevant information from the model. This is fundamentally sound. It provides you the flexibility to add custom suffixes and prefixes within the label text and string several pieces of information together. There seems to be a limitation on getting attributes from only one nesting level per label - i.e. when you select the <ComponentDefinition> of a toilet, you cannot add information from its parent (Bathroom, for example) within the same label - only other attributes of the toilet.

2. Make the asterisk * that allows you to add further <autotext> bigger or more prominent! I keep missing it! Or better still, replace it with a plus (+) sign. It was not immediately obvious that you could add further attributes by clicking on this tiny button.

3. You can get attributes of geometry, but what about the Scene? Again, it would add that flexibility without complicating things.

4. Model Info. Attributes at the model level are not included. If you are doing a schedule of products, you could have a table with a list of Sketchup components (as downloaded from 3D warehouse, for example). As much of the important information is stored at the model level, this information is not accessible via autolabel. I can imagine making a table with the label arrows being set to invisible (0% opacity). Adding this level of information would add further flexibility without adding complexity, I think.

5. Units - I use millimetres for lengths, square metres for area, cubic metres for volume. The ability to use autolabel to show volumes and areas is great, but I don't show floor areas in square millimetres! Choice of units will be great. Perhaps The Sketchup model info dialog should have options for "Area Units" and "Volume Units".

6. Moving the label pointer to a new object. Now I am getting picky, but I like those moments when I think - "I wonder if it could do that?" and the answer comes back "Yes!". I think when you move the pointer of the autolabel to a new object, it should update with information from the new object. If you are thinking "what nesting level?", then I would say the same level as the original pointed object (if that object has the attribute you originally pointed at). I hope that makes sense. What I can imagine doing is when labelling up a wall build up, I use autolabel to get info from the outer skin of brickwork, copy array down that autolabel, then simply amend the pointer of each copied label to each layer of the wall. It would save me from selecting the information type I want from an object. It would make annotations SO fast.

7. There needs to be a way of resizing the label text box without resizing the label pointer. Actually, this is a bit of a bug, I think, and should be fixed this version....

8. Open it up to developers! I use Skalp, for instance, which creates fantastic graphical sections in LO. When I use autolabel on the section cut faces, though, I can't get the information from the components from which they are cut - just face information. If their section cuts could simply reference the objects they cut through for autolabel to work its magic, Skalp and LO could work much better together. See http://sketchucation.com/forums/viewtopic.php?f=323%26amp;t=58685%26amp;start=60#p543147

All in all, the design of what you have done so far makes the implementation of the above seem quite simple and intuitive from where I am standing. I'm looking forward to using it for a real project.

[marcdurant]

For #7, double-click on the leader line to enter the new Label Manipulator - this will allow you to edit individual points in the leader line, change how the leader line connects to the text box, and change the size of the text box. It's a bit of a "hidden feature", so I'm working on a better way to get the word out.

[marcdurant]

#2 is a bug - that asterisk is a redraw artifact of what should be a button with a drop-down arrow on it. You can see what it's supposed to look like when you enter the text editor on a label but before you start typing.

thanks,
marc

[Krisidious]

Is scale an option here? scale of the model in layout?