-
Notifications
You must be signed in to change notification settings - Fork 50
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
State file name overwritten in Behavior source code when saving #14
Comments
After doing some further testing this seems to just be a bug with flexbe_full.launch. I am able to save the behavior and also make online edits to the state source file when using flexbe_ocs.launch without any issues. I can then open flexbe_full.launch to run the behavior. However, if i make any changes which require me to resave the behavior when in flexbe_full, the file name of the state will be overwritten as detailed above. |
Thank you for reporting! I will look at this as soon as possible.
… |
I was able to reproduce the issue and it looks like the following is going on: When using some editor commands, for example "subl -n $FILE" for sublime, all works fine. However, when using some other editor commands, including the default one "gedit --new-window $FILE +$LINE", the described issue occurs. The reason is that gedit creates a temporary file called ".goutputstream-xxxxxx", changes this file, and finally renames it to the target file again. As a consequence, the "change" event assumes a wrong file name. |
I changed the condition to determine whether a state definition update should be performed. It works for me now. Can you confirm? |
Thanks @pschillinger , that did it. Works a treat! |
I have pulled the latest development repo in order to utilise the new 'update state when source code changes' feature. However I seem to have come across a bug which prevents me from running the behavior. Every time I save the behavior the file name of the State ( in this case- jp_picking_main.py) changes in the behavior source code. As seen below on 2nd last line.
Expected Behavior Source Code:
Actual Behavior Source Code:
I then proceed to get the following output when running the behavior :
Any thoughts? cheers!
The text was updated successfully, but these errors were encountered: