-
Notifications
You must be signed in to change notification settings - Fork 1
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
Eagle 1039 #616
base: master
Are you sure you want to change the base?
Eagle 1039 #616
Conversation
Removing that setting is fine, that was my mistake the fix all and individual fixing of issues in the modal on load are working great. Problems: there is no way to get back to the version of the error modal that displays both, errors in the graph and in the palettes. |
…graph into drawing order.
Eagle 1136
Html graph renderer construct
Remove the requirement for a 'dropclass' field on Constructs
…n is now stored in the graph modelData.
…left floating in empty space
Default value of settings were not reset for 'Student' or 'Component' mode
Make it hard to save a graph with no name (or a bad name)
Removed the 'Description' category from CategoryData.
Factored out some common validation code into a single function within Utils
…do function from taking users back to a previously loaded graph.
…lass of edges that can never be created, even if the user has set 'allow invalid edges' to true.
…ments etc. We don't want the fix function to delete all these, we should rely on the user to switch them input PythonApps
Add new 'Impossible' value to the Eagle.LinkValid enum
removed all d3 stuff except in npm node modules
Could you take a quick look at this. Sorry, its a large code change.
The major changes are to use a common interface (a modal previously used for displaying/fixing graph errors) for three purposes:
It's useful to enable the following settings:
And test:
Also please check that removing line 345 from src/Setting.ts is OK