Move initialization from api.rs to the Editor backend #656
Assignees
Milestone
Comments
Keavon
added a commit
that referenced
this issue
Jul 30, 2023
…o widgets (#702) * unfinished implementation * Add frontend for the empty panel screen * Add an icon for Folder based on NodeFolder * fixed messages causing peicees of ui not to render on new document * Standardize nextTick syntax * WIP generisization of component subscriptions (not compiling yet) * Fix crash when loading font and there is no active document * Only advertise tool actions with a document * Fix failure to create new document * Initalise the properties panel * Fix highlight tab, canvas jump, warns and layer tree * Fix tests * Possibly fix some things? * Move WorkingColors layout definition to backend * Standardize action macro formatting * Provide typing for widgets in TS/Vue and associated cleanup * Fix viewport positioning initialization * Fix menu bar init at startup not document creation * Fix no viewport bounds bug * Change !=0 to >0 * Simplify the init system Closes #656 Co-authored-by: Keavon Chambers <[email protected]> Co-authored-by: 0hypercube <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently we call a bunch of messages in
api.rsto initialize the application. It would probably be better for this to call a single initialization message into the Editor backend, and then it can be in charge of dispatching that to the relevant sub-messages within the Editor. Maybe try and find some related initialization-related parts of the Editor codebase and standardize them into one system while working on this also.The text was updated successfully, but these errors were encountered: