Skip to content
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

(feature) Allow to use chili-widgets when engine's menu is disabled, too. #34

Open
knorker opened this issue Mar 6, 2015 · 0 comments

Comments

@knorker
Copy link

knorker commented Mar 6, 2015

It could be useful if chili-widget still worked even when the engine's GUI is hidden.
(player pressed F5 or textcommand "hideinterface 1")
Chili has Hide/Show functions so that a widget can decide on its own if/what to hide or show in that situation.
At the moment that decision seems to be taken away by the chili framework. *

A usecase might be widgets that are supposed to be visible even with "all" GUI disabled:
For example a "return to normal mode" button that only shows when the GUI is hidden.
(allows players to get their GUI when pressing F5 was maybe on accident.)

Or maybe widgets that go a bit into "debug territory" like widget selector might wish to ignore Spring.IsGUIHidden() too.

Even more radically:
In some situations none of the engine'S GUI is needed but chili-widgets should show:
Example 1: menus with animated gameplay in background.
Example 2: Mod that does all its GUI in Lua and has no more need for any of the engineGUI, even during normal play.

Being able to use "hideinterface 1" would be more elegant than fumbling to disable all the elements seperately. (and maybe restore them too..)


*Not 100% sure on that, but I do not see where such option could be hidden for example here:

function widget:MousePress(x,y,button)
if Spring.IsGUIHidden() then return false end
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant