Palettes won't swap unless AutoCAD 2019 is closed and reopened

Palettes won't swap unless AutoCAD 2019 is closed and reopened

Anonymous
Not applicable
902 Views
2 Replies
Message 1 of 3

Palettes won't swap unless AutoCAD 2019 is closed and reopened

Anonymous
Not applicable

Hi.

We have been using the *_TOOLPALETTEPATH method for swapping palettes (network wide) for a few years without any issues at all. Upgrading from 2016 to 2018 caused no issues what so ever - in fact, some users were using 2016 and others using 2018 at one stage, and both versions worked fine with the same network palettes. No upgrade of palettes was required at all for 2018 to run the 2016 palettes via the network. Happy days.

Recently, some PCs were upgraded to 2019 (from 2018).  The palette swap no longer works unless AutoCAD is closed and reopened. The palettes do swap and everything within the palettes appear as they should, in the order that they should and they function as they should, but only after closing and reopening AutoCAD.

Can anyone shed any light on this please.

Many thanks.

0 Likes
Accepted solutions (1)
903 Views
2 Replies
Replies (2)
Message 2 of 3

scot-65
Advisor
Advisor
A shot in the dark...
Perhaps convert the code to employ 'vla-put-ToolPalettePath'?

One will need to close the tool palettes, apply the new path,
then either command-s "TPNAVIGATE"... or command-s "TOOLPALETTES"?

Apply new path:
(vla-put-ToolPalettePath (vla-get-Files (vla-get-Preferences (vlax-get-acad-object))) %NewPaths%)

[nowhere in my code did I employ the phrase "_toolpalettepath"]

???

Scot-65
A gift of extraordinary Common Sense does not require an Acronym Suffix to be added to my given name.

0 Likes
Message 3 of 3

Anonymous
Not applicable
Accepted solution

Cheers Scot-65.

 

I've resolved this issue. I tried the vla method and got the same result. I then tried the good old fashioned way (manually changing palette path in the options dialog box) and ditto.  The palettes did not swap out. So I figured something's changed in 2019 version and the way it handles these things. And it would seem that was indeed the case.

 

I say "was" the case, because that was happening in the 2019 first release version. After patching to 2019.1.2 the problem went away.  Seems Autodesk were onto it.

 

So solution = patch to 2019.1.2 or later.

 

0 Likes