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
Describe the project you are working on:
My project has a GUI containing a large number of inter-operating custom controls and related logic modules. There is a need for the various controls and logic modules to inter-communicate.
Describe the problem or limitation you are having in your project:
If I use type definitions (e.g. class names as method parameter types) widely the editor throws errors saying scripts cannot be fully loaded due to cyclic references. If I remove type definitions no errors are raised and my code runs fine but without the benefit of type checking. The parser does not recognize that some cyclic references will not cause runtime problems.
Currently I am using a massive number of group calls to allow the GUI controls and logic modules to talk. The group call approach is not easily managed due to the need to assure that every GC method is uniquely named (e.g. problem of the same method names in multiple call-groups and multiple call-group membership).
Describe the feature / enhancement and how it helps to overcome the problem or limitation:
Make the parser "smarter" (is the parser multi-pass?) to ignore type definitions.
Describe how your proposal will work, with code, pseudocode, mockups, and/or diagrams:
The parser will not throw a script loading error just because two classes have type references to each other.
If this enhancement will not be used often, can it be worked around with a few lines of script?:
The only work around is to not use type definitions.
Is there a reason why this should be core and not an add-on in the asset library?:
I don't believe this can be done as an add-on.
The text was updated successfully, but these errors were encountered:
Describe the project you are working on:
My project has a GUI containing a large number of inter-operating custom controls and related logic modules. There is a need for the various controls and logic modules to inter-communicate.
Describe the problem or limitation you are having in your project:
If I use type definitions (e.g. class names as method parameter types) widely the editor throws errors saying scripts cannot be fully loaded due to cyclic references. If I remove type definitions no errors are raised and my code runs fine but without the benefit of type checking. The parser does not recognize that some cyclic references will not cause runtime problems.
Currently I am using a massive number of group calls to allow the GUI controls and logic modules to talk. The group call approach is not easily managed due to the need to assure that every GC method is uniquely named (e.g. problem of the same method names in multiple call-groups and multiple call-group membership).
Describe the feature / enhancement and how it helps to overcome the problem or limitation:
Make the parser "smarter" (is the parser multi-pass?) to ignore type definitions.
Describe how your proposal will work, with code, pseudocode, mockups, and/or diagrams:
The parser will not throw a script loading error just because two classes have type references to each other.
If this enhancement will not be used often, can it be worked around with a few lines of script?:
The only work around is to not use type definitions.
Is there a reason why this should be core and not an add-on in the asset library?:
I don't believe this can be done as an add-on.
The text was updated successfully, but these errors were encountered: