Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • B bjgf
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Issues 127
    • Issues 127
    • List
    • Boards
    • Service Desk
    • Milestones
  • Jira
    • Jira
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • BlueJ
  • bjgf
  • Issues
  • #2005

Closed
Open
Created Mar 26, 2018 by Neil Brown@nccbMaintainer

[GREENFOOT-670] Deleting the current world class causes exceptions

If you delete the current world class (i.e. the one that instantiates by default), you will get exceptions when Greenfoot later tries to use the currentWorld field in GreenfootStage. The way to solve this might be to listen for class deletions in GreenfootStage, and null out currentWorld if we see that it is the class that is being deleted.


Issue metadata

  • Issue type: Task
  • Priority: Medium
Assignee
Assign to
Time tracking