You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I want to add a new .soar file to me agent, my routine is to right-click the folder and select new file. Then I go to the load.soar file and and a "source new-file.soar" line to it. (As an aside...is there a better, "approved" way to do this? Under the old Soar IDE, there was an "Add Soar file" option, with a checkbox for "Automatically add the new file to load.soar").
As soon as I create this new file, the SLS output console reports a null point exception...my best guess is that it is complaining because this file is not (yet) on the load path for the agent. After I add the new file to load.soar, this null pointer exception appears to go away.
At the very least, it seems like there ought to be some exception handling to avoid the null pointer exception. Even better, though, might be a pop-up that warns you that this file is not currently loaded, and asking if you would like to add it to load.soar (maybe with a checkbox to select an ngs-style load or a regular "source" command).
The text was updated successfully, but these errors were encountered:
When I want to add a new .soar file to me agent, my routine is to right-click the folder and select new file. Then I go to the load.soar file and and a "source new-file.soar" line to it. (As an aside...is there a better, "approved" way to do this? Under the old Soar IDE, there was an "Add Soar file" option, with a checkbox for "Automatically add the new file to load.soar").
As soon as I create this new file, the SLS output console reports a null point exception...my best guess is that it is complaining because this file is not (yet) on the load path for the agent. After I add the new file to load.soar, this null pointer exception appears to go away.
At the very least, it seems like there ought to be some exception handling to avoid the null pointer exception. Even better, though, might be a pop-up that warns you that this file is not currently loaded, and asking if you would like to add it to load.soar (maybe with a checkbox to select an ngs-style load or a regular "source" command).
The text was updated successfully, but these errors were encountered: