Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Null pointer exception when creating a new .soar file that is not (yet) in the load path #205

Open
rjonessoar opened this issue Dec 11, 2019 · 2 comments
Labels
bug Something isn't working

Comments

@rjonessoar
Copy link

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).

@marinier
Copy link
Contributor

I believe Bryan (@sirnuke) is working on issues related to creating new files. He has hours this month, so hopefully progress is made.

@marinier
Copy link
Contributor

Possibly related to #164

@marinier marinier added the bug Something isn't working label Sep 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants