Why can't we edit the labels for the default client information yet?


 Share

Go to solution Solved by Alaskan_Son,

Recommended Posts

FWIW, I have a macro hidden on my Layout Template (page 0) that reads the text file(s) an get's all the info.  It executes when the Layout is opened but it's coded so that it will only execute once.

 

It stores that data in $Global variables that can be used in anyplace in both plan and layout.  The text files are unique to each project.

 

Basically, it just expands the functionality missing in the Designer/Client Info tool.  It would be a lot better if this sort of functionality was built-in to Chief.

  • Upvote 2
Link to comment
Share on other sites

  • Solution

I have my own systems for creating custom project information "fields".  Information is all entered in a single location in the plan or layout file, custom fields can be created on the fly, and I don't use globals anymore.  That being said, I'm a little curious why more people don't just use plain old non-evaluated text macros.  Its a very very easy way to create custom fields that can be exported/imported as well.

1305851961_pic1.thumb.jpg.13f33c0adbf908255ba3ff9e33375a6d.jpg

  • Upvote 1
Link to comment
Share on other sites

On 7/9/2025 at 11:35 AM, Alaskan_Son said:

That being said, I'm a little curious why more people don't just use plain old non-evaluated text macros.  Its a very very easy way to create custom fields that can be exported/imported as well.

That's what I do for detail parameters, but after I saw Rene's point and click system for details, I did realize his is a lot nicer (no typing, and not looking at a long list of macros in the TMM), which is why I thought if we could actually write to the text based macros, with a macro, then it is one and done.

 

But I did forget about the import function. For those that store data outside in files, good question, why not just import directly into the text macro...formatting maybe?

 

 

Link to comment
Share on other sites

On 7/9/2025 at 1:35 PM, Alaskan_Son said:

I have my own systems for creating custom project information "fields".  Information is all entered in a single location in the plan or layout file, custom fields can be created on the fly, and I don't use globals anymore.  That being said, I'm a little curious why more people don't just use plain old non-evaluated text macros.  Its a very very easy way to create custom fields that can be exported/imported as well.

1305851961_pic1.thumb.jpg.13f33c0adbf908255ba3ff9e33375a6d.jpg


I’m marking this as the solution only because it’s the most elegant and duplicatable way to make up for Chief’s severe deficiency in this aspect of the program.  
 

Even a newbie could use this method, thanks!   
 

Pretty sad I couldn’t figure this out myself since X6. 
 

It seems like this could take a programmer all of 5 minutes to bake into the client info dialogue box.
At least allow us to edit the filed names?

 

come on X18…

 

I realize there’s always a Chief dude coming in and saying that there’s too many requests and topics to follow to keep up, but may I suggest they follow Alaskan Son and René rabbit at the very least?
they don’t post that much on a daily basis.

 

  • Like 1
Link to comment
Share on other sites

1 hour ago, Michael_Gia said:

It seems like this could take a programmer all of 5 minutes to bake into the client info dialogue box.

thats what I suggested in the first post I made on this topic. a special class of text macro to show up in the client form. Then you could create as many as you'd like

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share