You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 21, 2023. It is now read-only.
Damn. I messed up. But I think I have an idea on how to fix all of this.
Perhaps I can label every level/folder/addon as a "project" and make a special QAbstractItemModel for such thing. Every model index there will have a type and content. A type is like a filetype, but stored as an enum value declared in C++ and exposed to QML. And content is for the actual content of the item that's selected. For example a script item will have the type "SCRIPT" and the content print("hello world")
In JS I will create a giant switch case with to select the right editor for each filetype using the filetype enum I exposed
The text was updated successfully, but these errors were encountered:
Damn. I messed up. But I think I have an idea on how to fix all of this.
Perhaps I can label every level/folder/addon as a "project" and make a special QAbstractItemModel for such thing. Every model index there will have a type and content. A type is like a filetype, but stored as an enum value declared in C++ and exposed to QML. And content is for the actual content of the item that's selected. For example a script item will have the type "SCRIPT" and the content
print("hello world")
In JS I will create a giant switch case with to select the right editor for each filetype using the filetype enum I exposed
The text was updated successfully, but these errors were encountered: