Getting Started Common Acronyms FAQ Forum Help Forum TipsSecure File Upload Helpful GuidelinesInserting and Attaching images, videos, or files to postsProduct Community Directory SELECTsupport
Lots of factors in my view ...
SSCLOUD is really old, and there may be a couple versions around compilied for v7 and v8.
The big thing no one seems to mention is there is an associated .RSC for the MDL. After use, if you unload of the MDL, the .RSC is created in the MDL location if it does not exist - if the user can write there! When the MDL and RSC are in a read-only location, load of the MDL could result in " Unable to load dialog whose id is 1". Executing the key ins for the MDL then generate "Unable to load/create dialog item of type 'ToggleButton', id = 1 from dialog "SSCLOUD" ". After selecting OK , the command is active and can be used, but the settings window for the command does not open.
Copy the same MDL/RSC (or better yet JUST the MDL to C:) and use browse to load ... a menu with two commands opens! The Icons execute the two keyins. A settings window should allow you to adjust radius for both commands, provides a copy option using convert, and there is an information button identifying Scott Nesin of Texas as the author.
The way you load the MDL seems to make a difference ... Without being loaded, if you drag it onto the graphics window to load it nothing happens, and you need to key in "place cloud" or convert cloud ... you should see the settings window has settings for placement radius. No command menu ever appears.
Bottom line - for the app to work it needs to be loaded with full path (mdl l fullpatfile) or using browse and from a read write location if you want to access the settings or command icons.
gday Bear, that explains alot, is this a one off with ssloud or all mdlapps? just wondering what i should take off the network and run locally. So far this is the only problem i have noticed.
This is a known issue with sscloud and have been around for a little while now. If you do a search on the forum for sscoud there is a thread where I posted up a replacement vb app. sscloud, as it stands, will not run with multi users across the network. It can be run locally though.
I have found that i receive the same error message with microstation on a network when another machine is running an instance of sscloud.
(does the mdl become read only once it is being used)
I have two machines rigged up on this network. If i open microstation first i can use sscloud without any dramas, but if i open microstation with the other machine already running i get the error:
Unable to load/create dialog item of type 'ToggleButton', id = 1 from dialog "SSCLOUD
But once you click ok the cloud tool will work.
Any Help would be geat.
I think I need to return to the parallel thread in the Road & Land Development forum.
I was able to get everything working (almost) by starting MicroStation and InRoads from the InRoads shortcut. I had determined that if I unload every non-esential MDL and then load InRoads the program runs normally. So my sollution appears to be to not load InRoads once MicroStation is running. Far from ideal, but workable. Now I have other issues that appear to be 100% InRoads issues.
Anything else you can think of?
I created a brand new UPF and even moved all customizations out of the default wsui folder.
One more thing. At the office, Google's spell check appears blocked by some IT setting.
OK, I've posted both versions in PDF form using Notepad++ with its color coded syntax enabled.
The summaries are sorted alphabetically.
I've also posted the same data sucked into Excel, each with its own tab.
I tried keeping all software on the local PC. There are CFG variables that let you put certain InRoads files on the network. Basically, I tried having the two main PRF files on the network. Keep in mind, I am doing the testing before a roll out to the users. I have read write access to everything and it still happens. I used the V8 workspace model to modify the SE configuration adding certain variables that are not ordinarily in SE and then pointed the traditional SE variables to those variables and there locations.
As I undertook my trouble shooting efforts, I started restoring local parts to certain variables and the problem persisted. I finally restored 100% local workspace and the problem went away.
I tried creating new UPF and new WSUI modules before going the local route, all without success.
How much of IR do you have on the network? Is it a read only area?
Ideally, you only need preferences and setting files on the network. There are some applications, like the issues with sscloud, that don't like this style of setup when trying to create dialogs.
I have determined that something in my efforts to setup a network workspace with SE is possigbly the cause. When I revert back to 100% local, the messages stop.
In SE, I'm running the old MDL version if InRoads and keep getting this message.
Is there a fix for this?