For uninitialized globals at the opening of a program

[Renerabbitt]

Who has some clever methods to initialize globals without the need of opening an object?
I would love it if I didnt have to remember to open something in order for my schedules to populate from initalized macros. I know Joe has asked for this a billion times. Has anyone come up with workarounds?
 

[Joe_Carrick]

3 hours ago, Renerabbitt said:

Who has some clever methods to initialize globals without the need of opening an object?
I would love it if I didnt have to remember to open something in order for my schedules to populate from initalized macros. I know Joe has asked for this a billion times. Has anyone come up with workarounds?
 

Just put a macro in the label of something in page 0 (or the page template of tthe title sheet) of your layout.  Hint:

• A Rectangle works well.  Just make sure you macro ends with "" so it doesn't show.
• I always open my projects with the Layout.

Edited Thursday at 03:26 AM by Joe_Carrick

[Renerabbitt]

5 hours ago, Joe_Carrick said:

Just put a macro in the label of something in page 0 (or the page template of tthe title sheet) of your layout.  Hint:

• A Rectangle works well.  Just make sure you macro ends with "" so it doesn't show.
• I always open my projects with the Layout.

Ended up figuring out something else, but I’ve got another question for you so windows, doors, cabinets, and rooms will all go look at a hash full of user options on how and the end-user wants to display their labels and what conventions are used and then all of those objects, then get pushed to a remap function Which remap some of the character outputs to a different part of a font, and it turns out that this was creating a major bottleneck..a lineup if you will at the font remapped which pushed me to change the user options to a global hash as well as the font remapped to a global call But can you think of maybe another method for the font remapped to keep it lightweight and accessible without having to write it into each individual macro that utilizes its function? Can a lambda be accessed simultaneously by all objects like a global can?

Edited Thursday at 08:34 AM by Renerabbitt

[Joe_Carrick]

In order to use differnt fonts I simply use different Layersets.  OTOH, if you just want to make certain characters like 0-9 as superscript characters you can set up a global like this:

• $ss = ["\u2070", "\u00B9", "\u00B2", "\u00B3", "\u2074", "\u2075", "\u2076", "\u2077", "\u2078", "\u2079"]

Then a superscript character "4" would be $ss[4] which can then be used in other macros to display widths and heights in feet and inches such as

• 3⁰6⁸

• 2⁶6⁸

• etc

I have several macros that cover all such opening labels.  My default labels for openings differintiate base on the object type and layerset (view_type which unfortunately is not an NVP).  Here's an example using both Callouts and Labels.

Edited Thursday at 01:44 PM by Joe_Carrick

[Renerabbitt]

7 hours ago, Joe_Carrick said:

I have several macros that cover all such opening labels.

I'm doing it a bit differently Joe. I am actually remapping for full height superscript and rich-text like outputs:

[Joe_Carrick]

Pretty cool, but for me that takes too much room on a Layout.  I'm essentially providing all the same information but in Door and Window Schedules.  I don't usually show the elevations but OTOH, I do provide the number of King Studs and Trimmers.

 

It's no unusual for me to have up to 20 different Doors and a simila number of different Windows.

Edited 22 hours ago by Joe_Carrick

[Renerabbitt]

4 minutes ago, Joe_Carrick said:

Pretty cool, but for me that takes too much room on a Layout

People can always remove the 3d column... This was more for illustrating the font remapping