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:
toggle quoted message
Show quoted text
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!!