TBC Macros and Extensions

Is there anyway of updating the Assign Name By Layer Command Macro for v5.90?  Or has anyone done this and can supply it?

I've brought this up several times as an improvement to be included in every version of TBC as it's an extreme time saver especially for big projects.

I used to be able to just copy and paste the old .py and .xaml file into the Program Data - Trimble - Macrocommand folder and it would work fine but now I just get varying errors when opening the software.

Has anyone dealt with this or have a fix?

If you have a Toolbox license you can use RenameObjects to achieve this:

Just switch to advanced mode put {layer} as your new name.

https://tbcanz.com/docs/Rename_Objects.pdf

https://www.youtube.com/watch?v=QsLoHWwNJDg

Is there anyway of updating the Assign Name By Layer Command Macro for v5.90?  Or has anyone done this and can supply it?

I've brought this up several times as an improvement to be included in every version of TBC as it's an extreme time saver especially for big projects.

I used to be able to just copy and paste the old .py and .xaml file into the Program Data - Trimble - Macrocommand folder and it would work fine but now I just get varying errors when opening the software.

Has anyone dealt with this or have a fix?

I don't have access to the ANZ Toolbox features.  Like I said though, the Name by Layer command always worked until recently, so not sure why it can't just be included in the software.  I know for myself and many others that is a very handy tool and time saver to have.  

Hate to spend $600 on RPS or whatever ANZ Toolbox costs for one command that was previously included with the software.  I'm sure it's not a hard fix but I'm not a coder.  Guess I'll have to learn it if I want some support.  Seems like customers keep losing commands and features but have to spend more for the software every year.

If you have a Toolbox license you can use RenameObjects to achieve this:

Just switch to advanced mode put {layer} as your new name.

https://tbcanz.com/docs/Rename_Objects.pdf

https://www.youtube.com/watch?v=QsLoHWwNJDg

Is there anyway of updating the Assign Name By Layer Command Macro for v5.90?  Or has anyone done this and can supply it?

I've brought this up several times as an improvement to be included in every version of TBC as it's an extreme time saver especially for big projects.

I used to be able to just copy and paste the old .py and .xaml file into the Program Data - Trimble - Macrocommand folder and it would work fine but now I just get varying errors when opening the software.

Has anyone dealt with this or have a fix?

Here's an updated version that runs in 5.90. I haven't done a lot of testing with it. Provided as is where is without warranty!

Hope this helps.

I don't have access to the ANZ Toolbox features.  Like I said though, the Name by Layer command always worked until recently, so not sure why it can't just be included in the software.  I know for myself and many others that is a very handy tool and time saver to have.  

Hate to spend $600 on RPS or whatever ANZ Toolbox costs for one command that was previously included with the software.  I'm sure it's not a hard fix but I'm not a coder.  Guess I'll have to learn it if I want some support.  Seems like customers keep losing commands and features but have to spend more for the software every year.

If you have a Toolbox license you can use RenameObjects to achieve this:

Just switch to advanced mode put {layer} as your new name.

https://tbcanz.com/docs/Rename_Objects.pdf

https://www.youtube.com/watch?v=QsLoHWwNJDg

Is there anyway of updating the Assign Name By Layer Command Macro for v5.90?  Or has anyone done this and can supply it?

I've brought this up several times as an improvement to be included in every version of TBC as it's an extreme time saver especially for big projects.

I used to be able to just copy and paste the old .py and .xaml file into the Program Data - Trimble - Macrocommand folder and it would work fine but now I just get varying errors when opening the software.

Has anyone dealt with this or have a fix?