Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • B bjgf
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 127
    • Issues 127
    • List
    • Boards
    • Service Desk
    • Milestones
  • Jira
    • Jira
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • BlueJ
  • bjgf
  • Issues
  • #2186
Closed
Open
Issue created Jul 03, 2021 by Neil Brown@nccbMaintainer

[GREENFOOT-859] Terminating ask-method in World-constructor leads to unexpected behavior

(Related to the solved [Greenfoot-849|http://bugs.bluej.org/browse/GREENFOOT-849] )

Try this:

  • Use the ask-method in the constructor of a class (e.g. in the World write var String x = Greenfoot.ask("answer me"))
  • Reset. The ask-dialog appears.
  • Click reset. You will be asked "The scenario is currently waiting for input. … you need to terminate the current execution." You click "terminate"
  • Now the world shrinks to small size and is fully occupied by the dialog-box.

Everything works correctly, but students are worried if the World suddenly "disappears" and think they have made something wrong.

So perhaps one could think about assimilating the both behaviors - like "When Greenfoot.ask is called in a World-constructor we let the World disappear and only show the dialog-box." or, alternatively: "When the ask-method is terminated by the user via the reset-button we create the World-size and then put the ask-method on it."


Issue metadata

  • Issue type: Bug
  • Priority: Lowest
Assignee
Assign to
Time tracking