-
Notifications
You must be signed in to change notification settings - Fork 3
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
Feature request: Unload FASM file #8
Comments
Hi! |
Awesome!
As long as this is the case, I suggest that a warning should appear, telling the user that the defined highlighting is overwritten.
So if I understand this correctly, the highlighting only changes for any wire defined in the I don't know how the highlighting is stored internally, but maybe a simple solution for letting the user decide what to keep would be to save all user defined highlighting, then overwrite it with the FASM-defined highlighting and then reapply the saved highlighting (if the user chose to keep the user defined highlighting). The two configuration could then be seen as two "masks" that just overwrite the wires defined in it, but leave all other wires untouched. This would even make it possible to switch between the two views! (Again, I have no clue if this is viable with the current implementation or maybe also resource hungry). Let me know what you think of this! |
What I mean here is any wire affected by the highlighting due to the |
It would be nice if unloading a
.fasm
file was possible, so that all connections set in it are not longer visible. All user defined connections or colours should however be preserved. This might cause conflict if the user changed connections previously set by the.fasm
file, so it has to be decided whether those connection should be kept or deleted.The text was updated successfully, but these errors were encountered: