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

Mouse cursor missing after using debug console #1775

Closed
IBwWG opened this issue Mar 16, 2016 · 7 comments
Closed

Mouse cursor missing after using debug console #1775

IBwWG opened this issue Mar 16, 2016 · 7 comments

Comments

@IBwWG
Copy link
Contributor

IBwWG commented Mar 16, 2016

  • Flixel version: dev
  • OpenFL version: 3.6.0
  • Lime version: 2.9.0
  • Affected targets: flash debug

Steps to reproduce

  1. press ~ to bring up the debug console
  2. press tab OR click in the console text field so you can type
  3. press ~ to hide the debug console

Observed behavior: mouse cursor is permanently gone
Expected behavior: mouse cursor should be unaffected by this

@Gama11
Copy link
Member

Gama11 commented Mar 16, 2016

Huh... I don't think this has always been the case, must've broken at some point.

@Gama11 Gama11 added the Bug label Mar 16, 2016
@larsiusprime
Copy link
Member

I've noticed this a whole bunch! I thought I was being crazy!

@Gama11
Copy link
Member

Gama11 commented Mar 16, 2016

Looks like this has actually been happening for a while (at least 3.3.12 - unfortunately it's difficult to go back further than that because of breaking changes in both OpenFL and Haxe).

@Gama11
Copy link
Member

Gama11 commented Mar 16, 2016

There are actually multiple different issues here. One of them is the fact that the debugger always sets useSystemCursor to false when it loses focus to revert to the Flixel cursor - regardless of what value useSystemCursor had previously, potentially overriding the user's changes.

The simplest solution would be to get rid of this "switch between Flixel and system cursor" behavior (always seemed somewhat annoying to me anyway) and render the Flixel cursor on top of the debugger. However, that's not really an option, since the mouse cursor still needs to work when the game is paused via the VCR buttons in the debugger - since that pauses the updating of FlxG.inputs as well, the cursor would currently stop moving.

@IBwWG
Copy link
Contributor Author

IBwWG commented Mar 16, 2016

For the record, I don't use any custom cursor...maybe I misunderstood though

@adrianulima
Copy link
Contributor

could store all user's mouse properties when open the console and restore when close?

@Gama11
Copy link
Member

Gama11 commented Mar 17, 2016

That's more or less what I've done in a commit I haven't pushed yet.. Not when closing the debugger though, but when any debugger component loses focus.

Gama11 added a commit that referenced this issue Mar 17, 2016
@Gama11 Gama11 closed this as completed in 83d3276 Mar 17, 2016
Aurel300 pushed a commit to larsiusprime/haxeflixel that referenced this issue Apr 18, 2018
Aurel300 pushed a commit to larsiusprime/haxeflixel that referenced this issue Apr 18, 2018
Aurel300 pushed a commit to larsiusprime/haxeflixel that referenced this issue Apr 18, 2018
Only happened on Flash with the native cursor API.
closes HaxeFlixel#1775
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

4 participants