eric.hawkins
2006-05-02, 11:00 PM
Ok, this seems to be a pretty rare error, but I figure I'll give it a shot on here. Sorry if I am overly detailed in this, but i want to be as clear as possible. This is AutoCAD 2006.
We are currently developing a palette menu system for our company. Meet me, the test version creator. (yeehaw right?) We have hundreds of users, so I'm using the method of creating a folder system on the server, then aiming the palette path in options at the folder i want, which brings up a blank palette, then populating, then switching folders etc etc. This way there is no importing, moving folders or anything...once it's built, it's built. It remembers everything i put on. Pretty standard.
I am creating buttons on the palettes that switch the tool palette path under options. This lets me jump between palettes (example department to department) by using icons on the palettes themselves instead of creating a custom toolbar. I am currently doing this by copying the lisp routine item off of the 'commands' palette that comes with AutoCAD, and pasting it on my new palettes to save trouble. I can then edit the command line and of course I'm using the beloved ^C^C*_toolpalettepath blah blah blah etc etc. This works great, I love it!
It wasn't until i decided to test it on another machine that the trouble started. He played with them for a bit, rearranging icons, nothing major and then Bam! we get an error that says:
Unable to execute tool. Possible causes are:
-The tool is not registered properly, Please check your installation.
-The tool is from another application and is incompatible with the current application.
"OK"
I know what you're thinking, why didn't i lock them down before having him test them? Cause i didn't think of that first duh! So i go back to my machine from there. Works fine for a few palette changes, then i get the same error.
I've found that if i re-aim the palette location to some other location on the server unrelated to this build, and then reload the path that just gave me problems before, the buttons will start working again. If i click slowly,, i can change between two palettes that reference each other endlessly.
However, if i start clicking very quickly between two palettes (almost double click speed) I will get the error within 4-5 clicks every time if not instantly. What is causing this? It honestly seems to be clicking speed, and if clicking speed is going to break the palette command buttons thats a HUGE problem because we have lots of 'old' users that double click everything anyways.
I have tried switching to read only and all writable, but it never changes the situation, it will always get that error if i click quick enough.
Looking for any input i can get here as to what is happening. Can it not write the palette files fast enough to keep up with a quick click? Is it because all these paths are in the same root?
Example of structure:
G:\Development\Index
G:\Development\Departments\Mechanical
G:\Development\Departments\Plant Design
Thanks for any help.
We are currently developing a palette menu system for our company. Meet me, the test version creator. (yeehaw right?) We have hundreds of users, so I'm using the method of creating a folder system on the server, then aiming the palette path in options at the folder i want, which brings up a blank palette, then populating, then switching folders etc etc. This way there is no importing, moving folders or anything...once it's built, it's built. It remembers everything i put on. Pretty standard.
I am creating buttons on the palettes that switch the tool palette path under options. This lets me jump between palettes (example department to department) by using icons on the palettes themselves instead of creating a custom toolbar. I am currently doing this by copying the lisp routine item off of the 'commands' palette that comes with AutoCAD, and pasting it on my new palettes to save trouble. I can then edit the command line and of course I'm using the beloved ^C^C*_toolpalettepath blah blah blah etc etc. This works great, I love it!
It wasn't until i decided to test it on another machine that the trouble started. He played with them for a bit, rearranging icons, nothing major and then Bam! we get an error that says:
Unable to execute tool. Possible causes are:
-The tool is not registered properly, Please check your installation.
-The tool is from another application and is incompatible with the current application.
"OK"
I know what you're thinking, why didn't i lock them down before having him test them? Cause i didn't think of that first duh! So i go back to my machine from there. Works fine for a few palette changes, then i get the same error.
I've found that if i re-aim the palette location to some other location on the server unrelated to this build, and then reload the path that just gave me problems before, the buttons will start working again. If i click slowly,, i can change between two palettes that reference each other endlessly.
However, if i start clicking very quickly between two palettes (almost double click speed) I will get the error within 4-5 clicks every time if not instantly. What is causing this? It honestly seems to be clicking speed, and if clicking speed is going to break the palette command buttons thats a HUGE problem because we have lots of 'old' users that double click everything anyways.
I have tried switching to read only and all writable, but it never changes the situation, it will always get that error if i click quick enough.
Looking for any input i can get here as to what is happening. Can it not write the palette files fast enough to keep up with a quick click? Is it because all these paths are in the same root?
Example of structure:
G:\Development\Index
G:\Development\Departments\Mechanical
G:\Development\Departments\Plant Design
Thanks for any help.