Thanks.? I actually always do a recompile all (Alt-F12) vs a recompile (F12).? I think the safety of knowing that everything is coordinated is worth the additional compile time wait because I am constantly jumping into C# and S+ modules.
That being said, recompile all didn't fix the problem.
Thanks again
Jay
toggle quoted message
Show quoted text
On 9/27/2024 12:53 PM, MSTC via groups.io wrote:
F12 (recompile all) may have worked also.
On Sep 27, 2024, at 11:30 AM, jbasen <jay.m.basen@...> wrote:
I deleted a signal from the output of a .umc module in one of my SimplWindows programs and replace it with "//" so the module is complete. The signal is no longer being used so it has been completely removed from everywhere in my SimplWindows program. The Argument Definition of the .umc file looks like this:
[~BeginGroup~]Master_Bedroom_Window_Settings
Leave_MBed_Window_Open
[~EndGroup~]Master_Bedroom_Window_Settings
When I compile the SimplWindows program I get a warning that the signal name that I deleted has no driving source and a notice that the signal has no destination. When I double click on either of these in program compilation dialog it takes me to the [~BeginGroup~]Master_Bedroom_Window_Settings output of the module.
I've tried exiting / restarting SimplWindows along with deleting the SPIsWork Folder.
Any ideas on how to get SimplWindows to realize that this signal has really been deleted would be greatly appreciated.
Thanks in advance for the help
Jay
