¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

SMW User Modules not showing up in the library


 

Hi All,
So the ultimate take-away is that I should suffer what I know and not try to eliminate and suffering...:(
I tried moving to work only with project libraries, because my ancient/bloated SMW library was causing 'eternal' SMW start times and open project times...well that definitely fixed that issue, but the when it came to development and trying to retrieve previously created User modules that had other user modules and S+ embedded in them, it was just way too much of a beating to be worth it, so I've gone back to the devil I know...

Of course now I have a new problem, that I never had before all this rigmarole, that I'd like to see if anyone has seen:
Some User Modules will not show up in 4-series, and when opening a project with said module, the module is commented out and not visible to re-add in the SMW library. - Thus making the project unusable without some sort of resolution to this issue...:(

*** I understand about Project Header/Target Control Classes, even for sub modules and S+ ***

I worked thru one issue with Crestron Support last week and found that there was an S+ module that, although was set to 3/4-series and was re-Built/Save+Compile, we had to do an S+ 'Recompile ALL' to get it to work.
So when I ran into a similar issue yesterday, I dutifully checked all the internal item settings and did a recompile all on the (1) S+ module in the User Module.
Still Nothing!!!

Has anyone seen anything like this? or have any other secret hand-shakes??

TIA!!


 

¿ªÔÆÌåÓý

Every time I have run into this problem, which has been more times than I care to count, I have always traced it to a problem with settings for the target control system in unc and s+ files.? If you have lots of nesting then it can be PITA to trace all the dependencies and get them fixed.?

Sorry I can't offer any alternatives but when I've run into the issue it has always come down to the same solution.

Jay

On 2/27/2022 5:29 PM, ckangis wrote:

Hi All,
So the ultimate take-away is that I should suffer what I know and not try to eliminate and suffering...:(
I tried moving to work only with project libraries, because my ancient/bloated SMW library was causing 'eternal' SMW start times and open project times...well that definitely fixed that issue, but the when it came to development and trying to retrieve previously created User modules that had other user modules and S+ embedded in them, it was just way too much of a beating to be worth it, so I've gone back to the devil I know...

Of course now I have a new problem, that I never had before all this rigmarole, that I'd like to see if anyone has seen:
Some User Modules will not show up in 4-series, and when opening a project with said module, the module is commented out and not visible to re-add in the SMW library. - Thus making the project unusable without some sort of resolution to this issue...:(

*** I understand about Project Header/Target Control Classes, even for sub modules and S+ ***

I worked thru one issue with Crestron Support last week and found that there was an S+ module that, although was set to 3/4-series and was re-Built/Save+Compile, we had to do an S+ 'Recompile ALL' to get it to work.
So when I ran into a similar issue yesterday, I dutifully checked all the internal item settings and did a recompile all on the (1) S+ module in the User Module.
Still Nothing!!!

Has anyone seen anything like this? or have any other secret hand-shakes??

TIA!!


 

Another, "I don't know why it works, but sometimes it does" thing to try is deleting the SPlsWork subfolder in your program folder.?

I've had the same thing, where I've double-checked all targets, recompiled all, etc. and it didn't work until I closed the program, deleted the SPlsWork folder, reopened and Recompiled ALL (Alt+F12). It doesn't fix other problems (nesting, wrong target, etc.), but sometimes when nothing else makes sense it works.

Another "This shouldn't fix anything, but sometimes it does" is just rename the program, save it to another folder and start again in a "fresh place", copy/paste in any needed modules, etc and Recompile ALL again

Final item that shouldn't work, but has saved me a few times is replacing the processor in the program: If you have a Pro3, replace with AV3, save, replace back to Pro3, save, recompile all.? Again, this *shouldn't* fix anything, but it has for me when nothing else made sense. Double-check the program it didn't add anything helpful during the replace like a CEN-IO to make up for port differences.??

I think those are all the secret handshakes I remember.

Good luck,
Micah Thurlow


 

Another item to check, is to double check the "category" that the module is assigned to.? If an S+ module is set to category "0", the module will be hidden and not available in your library even though you have the correct files in the project directory.? Hope this helps.