-
Notifications
You must be signed in to change notification settings - Fork 716
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
Extension variables #6557
Extension variables #6557
Conversation
e6a1aed
to
1258a76
Compare
1258a76
to
623ddcf
Compare
Local | ||
Local, | ||
ExtensionGlobal, | ||
Extension |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As discussed, maybe
Extension | |
ExtensionScene | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(someone could say that there is no reason "Extension" would mean something tied to the scene, the default "Extension" could as well mean "global variables" that live forever because the extension lives forever when the game runs)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree but I used a different enum value because I was afraid of a confusion in the generator. Maybe we can try to refactor later?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You mean a confusion if you rename Extension to ExtensionScene?
That should be fairly safe now, the compiler will let you know all the changes to do?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, I meant using existing Scene
and Global
+ the scope as there is no "any" variable that can be both Global
and ExtensionGlobal
but I'm not sure if it would be better or not (or even feasible).
@@ -39,6 +44,12 @@ export default function OptionsEditorDialog({ | |||
title={<Trans>{eventsFunctionsExtension.getName()} options</Trans>} | |||
secondaryActions={[ | |||
<HelpButton key="help" helpPagePath="/extensions/create" />, | |||
<RaisedButton |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok for now but we really need to move it to a tree item soon then! :)
Changes
ArbitraryEventsWorkerWithContext
inheritance to avoid bad segment crashes.data.json