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
This is a bit of a stretch, but it would be very cool: Make OpenGUI just as capable of in-line GUI programming as it is in GameObject-based form.
That is, we'd create methods like OG:Button ( String, Rect, ... ) : bool and call them from OGPage:DrawPage (), which would essentially be OpenGUI's version of OnGUI (). This needs a bit of restructuring, and there are some issues with material passes that need to be addressed, but overall, this would allow for more code-centric implementations while still maintaining the convenience of previewing your GUI outside play mode. It would also mean less widget management, which would ultimately result in a lighter CPU load.
The text was updated successfully, but these errors were encountered:
I'm not knowledgable enough about the ins and outs of GUI element drawing in either OnGUI or OpenGUI. But it seems to me it would make it easier to script flexible UI's.
This is a bit of a stretch, but it would be very cool: Make OpenGUI just as capable of in-line GUI programming as it is in GameObject-based form.
That is, we'd create methods like
OG:Button ( String, Rect, ... ) : bool
and call them fromOGPage:DrawPage ()
, which would essentially be OpenGUI's version ofOnGUI ()
. This needs a bit of restructuring, and there are some issues with material passes that need to be addressed, but overall, this would allow for more code-centric implementations while still maintaining the convenience of previewing your GUI outside play mode. It would also mean less widget management, which would ultimately result in a lighter CPU load.The text was updated successfully, but these errors were encountered: