jMonkeyEngine / jMonkeyEngine/jmonkeyengine
If the flyCam is disabled as part of the initialization in SimpleApplication, the cursor is forcefully set to visible during the appstates initialization
Open
Nobody has claimed this yet.
bug
- Dominant language
- Java
- Stars
- 4.3k
- Forks
- 1.2k
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 14
Description
The following code doesnt work as expected when called from simpleInitApp, since the FlyBy cam appstate will force inputManager.setCursorVisible(true) during the initialization of the appstates
flyCam.setEnabled(false);
inputManager.setCursorVisible(false);
A temporary workaround is to also detach the appstate
flyCam.setEnabled(false);
inputManager.setCursorVisible(false);
stateManager.detach(stateManager.getState(FlyCamAppState.class));
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at SimpleApplication initialization and the FlyCamAppState setup invoked around simpleInitApp, then trace when inputManager.setCursorVisible(true) runs. Reproduce the sequence with flyCam disabled and verify that setting the cursor invisible in simpleInitApp remains effective without detaching the appstate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100