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

Do not handle events in work space when handled by the Ui #30

Open
bvssvni opened this issue Nov 1, 2015 · 1 comment
Open

Do not handle events in work space when handled by the Ui #30

bvssvni opened this issue Nov 1, 2015 · 1 comment
Labels

Comments

@bvssvni
Copy link
Member

bvssvni commented Nov 1, 2015

Currently the events are handled by both Ui and work space.

When clicking in the 3D scene, an entity is added at the ground. When clicking on the "reset" button, turbine tries to insert an entity. Needs feedback from Conrod of which events that were handled.

@bvssvni bvssvni added the draft label Nov 1, 2015
@bvssvni bvssvni changed the title Do not handle events that are handled by the Ui Do not handle events in work space when handled by the Ui Nov 1, 2015
@mitchmindtree
Copy link

Hey @bvssvni just saw this :)

It sounds like it might be useful to add a method to the Ui that tells the user whether or not the mouse is currently over a widget, returning Some(widget::Index) if it is, or None if it is not.

It might also be useful to provide a method that indicates whether or not user input is currently being captured by conrod, as well as a way to tell conrod that user input has been captured/uncaptured by an external source.

I've added issues for these here, here and here. Let me know your thoughts! 😸

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants