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
  • #1975
Closed
Open
Issue created Dec 06, 2017 by Neil Brown@nccbMaintainer

[GREENFOOT-640] Tidy up the Simulation thread code

The Simulation thread on the debug VM is a bit muddled at the moment. Previously, it had code for doing Swing painting at the appropriate intervals along with various world locks. I wonder if the world locks may be removed now (since all code on the debug VM that touches anything world-related should run on the Simulation thread, I think we can treat being on the simulation thread as an implicit mutex?).

I think we can get rid of the SimulationListener mechanism eventually (the only use which will remain is one use in GreenfootScenarioViewer, I think, which probably doesn't need a whole listener/event mechanism).

I think it probably makes sense for Davin to either do this or review this, since I think he probably understands that code better than the rest of us. But this is probably best done a bit later on in the rewrite after chunks of the IDE code have been removed and it's clearer what is still needed, so not assigning it yet.


Issue metadata

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