Hello all,
I've recently installed Configurator 1.0 and created my first panel as a collection of menu commands and tools I most often use. The panel is 800x130 (HxW) pixels. I'm running Vista 64 Ultimate with PS CS4 32-bit & 64-bit installed, and have observed that with the panel exported to both versions of PS, it will open in each at a 214-pixel width as the application initializes, but then very quickly resize to the 130-pixel width I defined. However, while consistently true for 64-Bit PS, that is not the case for 32-Bit, where the panel commonly remains at the 214-pixel width as often as not. This does not seem to be affected by whether the panel is docked or undocked, or whether I've resaved a workspace or even created a new one with the panel active. I'm not certain of this, but it seems that if I close the panel in 32-bit PS before closing the application, then it is more likely that if I reopen the application and then enable the panel, it will initialize to the correct size. Oh, and when it is at the 214-pixel width, I cannot resize it manually. Similarly, when the panel is reopened for editing in Configurator, it always opens at the correct 130-pixel width.
Note that the panels for each version of PS were separately exported to the respective Plug-ins/Panels folder and I even tried replacing the folder under the 32-bit PS with a hard link (junction) to the Panels folder in the 64-bit PS. That made no difference in the observed behavior other than that it does allow one exported panel location to serve both applications. I tried the same with a shortcut in lieu of of a junction, but that didn't seem to work insofar as the Panels extensions being loaded.
Has anyone seen such behavior as this? It is really no more than a nuisance, but I'd like to avoid it if possible.
Thanks,
Daryl
I've recently installed Configurator 1.0 and created my first panel as a collection of menu commands and tools I most often use. The panel is 800x130 (HxW) pixels. I'm running Vista 64 Ultimate with PS CS4 32-bit & 64-bit installed, and have observed that with the panel exported to both versions of PS, it will open in each at a 214-pixel width as the application initializes, but then very quickly resize to the 130-pixel width I defined. However, while consistently true for 64-Bit PS, that is not the case for 32-Bit, where the panel commonly remains at the 214-pixel width as often as not. This does not seem to be affected by whether the panel is docked or undocked, or whether I've resaved a workspace or even created a new one with the panel active. I'm not certain of this, but it seems that if I close the panel in 32-bit PS before closing the application, then it is more likely that if I reopen the application and then enable the panel, it will initialize to the correct size. Oh, and when it is at the 214-pixel width, I cannot resize it manually. Similarly, when the panel is reopened for editing in Configurator, it always opens at the correct 130-pixel width.
Note that the panels for each version of PS were separately exported to the respective Plug-ins/Panels folder and I even tried replacing the folder under the 32-bit PS with a hard link (junction) to the Panels folder in the 64-bit PS. That made no difference in the observed behavior other than that it does allow one exported panel location to serve both applications. I tried the same with a shortcut in lieu of of a junction, but that didn't seem to work insofar as the Panels extensions being loaded.
Has anyone seen such behavior as this? It is really no more than a nuisance, but I'd like to avoid it if possible.
Thanks,
Daryl