Project Information Suggestions/Issues

[Renerabbitt]

[Joe_Carrick]

 

I do like the sort and macro suggestions.  I'm not sure however that I would need to insert macros into field values.  In most cases I will just enter the values as text - or copy the macro results from TMM into the field value.  

 

For the most part it's pretty easy to duplicate classes and copy field values.  To be honest, I am so happy to get this as provided that I basically overlooked the slight annoyances you outlined above.  

 

What I really want is for the field values to be returned as actual data strings.  Currently I have use a bit of ledgerdemain to get editable values.

 

 

Edited yesterday at 03:03 AM by Joe_Carrick

[Renerabbitt]

19 hours ago, Joe_Carrick said:

I'm not sure however that I would need to insert macros into field values.

I was on a training call yesterday and, as I often do, I started by giving you big compliments. But I also mentioned that no one could simply pick up one of your layouts or plans and immediately understand how everything works. The workflow is incredibly specific, with a lot of knowledge required to perform even simple tasks, plus all the unique layers and layer sets involved. You and I wouldnt need this but its nice for end-use

All that to say, leaving a macro call inside a value is a smart way for the template to automate a task while still giving the end user one easy place to override that automation when needed.
In other words, its great for scalability without the need for unique training.
 

19 hours ago, Joe_Carrick said:

For the most part it's pretty easy to duplicate classes and copy field values.  To be honest, I am so happy to get this as provided that I basically overlooked the slight annoyances you outlined above.  

I always hear Kevin Transue screaming from the rooftops "inheritanceeeeeee"
Why this dbx was designed in a way that didnt just inherit properties from other similar dbx is what he would be referring to. Why isnt there a "user input dbx standard" module thats just plug and play so that it behaves similarly to the project browser/library browser or the "add lights" dbx?

 

 

19 hours ago, Joe_Carrick said:

Currently I have use a bit of ledgerdemain to get editable values.

as in a displayed polyline or other object with a label that says %$chief_project_zipcode="%project.zip/postal_code%";""% yeah...same wish +1000
 

[Renerabbitt]

11 hours ago, Joe_Carrick said:

Do you have Michael's hack for this?  I put mine in a the Label of a Polyline on sheet 0 of my layout.

yeah he posted it here on chieftalk somewhere a long time ago. I have a bunch of pages of notes in onedrive from things all of the macro guys have said over the years.
I use it in a plan file. the plan file is setup for all title block info and spec writing on your general sheet so its easy to swap out when i change jurisdictions or who I am drafting for etc. 
all of this gets sent to different parts of layout

and this polyline has all of the captures

[Joe_Carrick]

Mine is in the label of a polyline on my Layout Template.  That way it's executed as soon as the Layout is opened.

ps:  The polyline dbx really needs to have a label box with at least 10 lines of space to prevent the need for so much scrolling.

[Renerabbitt]

7 hours ago, Joe_Carrick said:

The polyline dbx really needs to have a label box with at least 10 lines of space to prevent the need for so much scrolling.

YES YES YES YES YES and more YES
 

 

7 hours ago, Joe_Carrick said:

That way it's executed as soon as the Layout is opened.

Mine also executes as soon as layout is opened, without ever opening the plan file  because the polyline is alongside of those information blocks and they are sent to layout