TBC Macros and Extensions

Hello Gary,

thanks for the information.

The enhanced security though is a deal breaker and no-go. I was already wondering what was going on when I installed the Beta version on my private laptop and couldn't properly access the folder although I'm the admin on my private machine.

At my workplace do only our IT guys have admin rights and need to login to our machines to install TBC. And for each update/program/settings change we want we need to call them and they have to login again, if they are available that is. We can't even change the desktop background, or delete icons from it when they were placed there during an admin session.

For some things I actually have to use my private laptop, i.e. running the ASCII file generator from a batch file. 

With that "enhanced" security everybody in our company who is using my macros would have to call IT each and every time I update something. I couldn't even create a new one without calling them.

Please reconsider that move, that's going to cause troubles for a lot of users.

Cheers

Ronny

Hello Gary,

thanks for the information.

The enhanced security though is a deal breaker and no-go. I was already wondering what was going on when I installed the Beta version on my private laptop and couldn't properly access the folder although I'm the admin on my private machine.

At my workplace do only our IT guys have admin rights and need to login to our machines to install TBC. And for each update/program/settings change we want we need to call them and they have to login again, if they are available that is. We can't even change the desktop background, or delete icons from it when they were placed there during an admin session.

For some things I actually have to use my private laptop, i.e. running the ASCII file generator from a batch file. 

With that "enhanced" security everybody in our company who is using my macros would have to call IT each and every time I update something. I couldn't even create a new one without calling them.

Please reconsider that move, that's going to cause troubles for a lot of users.

Cheers

Ronny

@Ronny Schneider

I had the some thoughts yesterday. Those IT people, they're the same everywhere :) How about:

TBC does support macro folder redirection. If you define an environment variable named "TBC_Macro3Path", the value of the variable should be the folder where TBC should search for macros (instead of C:\ProgramData\Trimble\MacroCommands3). Environment variable "TBC_Macro3Path2" can be used to define a folder that TBC searches in addition to the normal folder.

Can we have our own macro folder? c:\scr_macros ?

Hello Gary,

thanks for the information.

The enhanced security though is a deal breaker and no-go. I was already wondering what was going on when I installed the Beta version on my private laptop and couldn't properly access the folder although I'm the admin on my private machine.

At my workplace do only our IT guys have admin rights and need to login to our machines to install TBC. And for each update/program/settings change we want we need to call them and they have to login again, if they are available that is. We can't even change the desktop background, or delete icons from it when they were placed there during an admin session.

For some things I actually have to use my private laptop, i.e. running the ASCII file generator from a batch file. 

With that "enhanced" security everybody in our company who is using my macros would have to call IT each and every time I update something. I couldn't even create a new one without calling them.

Please reconsider that move, that's going to cause troubles for a lot of users.

Cheers

Ronny

Also needs to be done by IT during installation. That would mean they'd have to have a procedure what to do, which they'll probably never "remember/follow". So, the user who gets TBC installed needs to be aware of it and make sure they do. Either way it means the user needs to kick IT's butt to either create that environment variable or to unlock the macro folder. Third party TBC macros won't work out of the box anymore since some companies force their IT regulations on all of us. Instead of locking the folder themselves, if they really need this, they force the rest of us to unlock it.

Trimble should add a tickbox into the setup.exe GUI, default unlocked of course. The handful of IT departments out there that really need this can tick that one during installation and have it their way but leave the rest of us unmolested.

@Ronny Schneider

I had the some thoughts yesterday. Those IT people, they're the same everywhere :) How about:

TBC does support macro folder redirection. If you define an environment variable named "TBC_Macro3Path", the value of the variable should be the folder where TBC should search for macros (instead of C:\ProgramData\Trimble\MacroCommands3). Environment variable "TBC_Macro3Path2" can be used to define a folder that TBC searches in addition to the normal folder.

Can we have our own macro folder? c:\scr_macros ?

Hello Gary,

thanks for the information.

The enhanced security though is a deal breaker and no-go. I was already wondering what was going on when I installed the Beta version on my private laptop and couldn't properly access the folder although I'm the admin on my private machine.

At my workplace do only our IT guys have admin rights and need to login to our machines to install TBC. And for each update/program/settings change we want we need to call them and they have to login again, if they are available that is. We can't even change the desktop background, or delete icons from it when they were placed there during an admin session.

For some things I actually have to use my private laptop, i.e. running the ASCII file generator from a batch file. 

With that "enhanced" security everybody in our company who is using my macros would have to call IT each and every time I update something. I couldn't even create a new one without calling them.

Please reconsider that move, that's going to cause troubles for a lot of users.

Cheers

Ronny

Amen @Ronny Schneider , amen!

Also needs to be done by IT during installation. That would mean they'd have to have a procedure what to do, which they'll probably never "remember/follow". So, the user who gets TBC installed needs to be aware of it and make sure they do. Either way it means the user needs to kick IT's butt to either create that environment variable or to unlock the macro folder. Third party TBC macros won't work out of the box anymore since some companies force their IT regulations on all of us. Instead of locking the folder themselves, if they really need this, they force the rest of us to unlock it.

Trimble should add a tickbox into the setup.exe GUI, default unlocked of course. The handful of IT departments out there that really need this can tick that one during installation and have it their way but leave the rest of us unmolested.

@Ronny Schneider

I had the some thoughts yesterday. Those IT people, they're the same everywhere :) How about:

TBC does support macro folder redirection. If you define an environment variable named "TBC_Macro3Path", the value of the variable should be the folder where TBC should search for macros (instead of C:\ProgramData\Trimble\MacroCommands3). Environment variable "TBC_Macro3Path2" can be used to define a folder that TBC searches in addition to the normal folder.

Can we have our own macro folder? c:\scr_macros ?

Hello Gary,

thanks for the information.

The enhanced security though is a deal breaker and no-go. I was already wondering what was going on when I installed the Beta version on my private laptop and couldn't properly access the folder although I'm the admin on my private machine.

At my workplace do only our IT guys have admin rights and need to login to our machines to install TBC. And for each update/program/settings change we want we need to call them and they have to login again, if they are available that is. We can't even change the desktop background, or delete icons from it when they were placed there during an admin session.

For some things I actually have to use my private laptop, i.e. running the ASCII file generator from a batch file. 

With that "enhanced" security everybody in our company who is using my macros would have to call IT each and every time I update something. I couldn't even create a new one without calling them.

Please reconsider that move, that's going to cause troubles for a lot of users.

Cheers

Ronny

Found another class that has been moved around:

until 5.81 -  Trimble.Vce.UI.ScanningCommands.CreateBestFitLine

from 5.90 - Trimble.Vce.Alignment.Linestring.CreateBestFitLine

usage has changed slightly as well

V5.81

V5.90

Amen @Ronny Schneider , amen!

Also needs to be done by IT during installation. That would mean they'd have to have a procedure what to do, which they'll probably never "remember/follow". So, the user who gets TBC installed needs to be aware of it and make sure they do. Either way it means the user needs to kick IT's butt to either create that environment variable or to unlock the macro folder. Third party TBC macros won't work out of the box anymore since some companies force their IT regulations on all of us. Instead of locking the folder themselves, if they really need this, they force the rest of us to unlock it.

Trimble should add a tickbox into the setup.exe GUI, default unlocked of course. The handful of IT departments out there that really need this can tick that one during installation and have it their way but leave the rest of us unmolested.

@Ronny Schneider

I had the some thoughts yesterday. Those IT people, they're the same everywhere :) How about:

TBC does support macro folder redirection. If you define an environment variable named "TBC_Macro3Path", the value of the variable should be the folder where TBC should search for macros (instead of C:\ProgramData\Trimble\MacroCommands3). Environment variable "TBC_Macro3Path2" can be used to define a folder that TBC searches in addition to the normal folder.

Can we have our own macro folder? c:\scr_macros ?

Hello Gary,

thanks for the information.

The enhanced security though is a deal breaker and no-go. I was already wondering what was going on when I installed the Beta version on my private laptop and couldn't properly access the folder although I'm the admin on my private machine.

At my workplace do only our IT guys have admin rights and need to login to our machines to install TBC. And for each update/program/settings change we want we need to call them and they have to login again, if they are available that is. We can't even change the desktop background, or delete icons from it when they were placed there during an admin session.

For some things I actually have to use my private laptop, i.e. running the ASCII file generator from a batch file. 

With that "enhanced" security everybody in our company who is using my macros would have to call IT each and every time I update something. I couldn't even create a new one without calling them.

Please reconsider that move, that's going to cause troubles for a lot of users.

Cheers

Ronny