-
Notifications
You must be signed in to change notification settings - Fork 23
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
Score update problem #64
Comments
Dear G Sorry but i am not sure to understand you well here:
When you say going inside and edit you mean changing notes? and then close it? Thank you Best |
Dear Goncalo, Ok i could see the problem. It is macosx related. I have fixed it and will issue a new patch tomorrow.
Best |
Thanks so much. Yes, using MacOS here. |
Now the patch is available. Best |
Hello. It seems that, with the new patch, score objects are not editable by selecting the note and using the arrows: this generates a popup window with an error message. Also, it seems that CHORD-SEQ-ANALYSIS is having trouble outputting an SDIFFILE. There is this message in the Listener: "Removing files:" and then the path to the newly-generated file (in ~/Library tempchords, and workspace out-files/chordseqs.sdif) is listed... This is probably why it can't pass the sdif file to the SDIFFILE object. |
Arrow issue seems to happen only with the NOTE object. |
Dear Goncalogato, Please can you be more specific here?
Best |
Dear G, Thank you again. Your feedback is really appreciated. Best Regards |
Dear K, With the latest patch_191224.lisp I still get the error message in NOTE, while using the arrows inside. Thank you |
Yes you're right. Best |
Dear G Can you now replace the pathc by the new one? Best |
This is now working correctly. Thank you so much. Best |
Hello,
When you change a score object by going inside and edit, it does not display the change when you close it. It does update when you click m two times (thus hiding and showing the content again). This can slow down visualisation inside OM.
thanks
g
The text was updated successfully, but these errors were encountered: