bjgf issueshttps://gitlab.bluej.org/bluej/bjgf/-/issues2019-11-21T09:25:25Zhttps://gitlab.bluej.org/bluej/bjgf/-/issues/2162[GREENFOOT-835] Greenfoot.delay() forcing repaint2019-11-21T09:25:25ZNeil Brown[GREENFOOT-835] Greenfoot.delay() forcing repaintIn Greenfoot 3.6.0, calling Greenfoot.delay() forces a repaint, even if the absolute delay time would be very small (e.g. a few microseconds) because the speed is set to high. We shouldn't need to repaint if there was a recent repaint a...In Greenfoot 3.6.0, calling Greenfoot.delay() forces a repaint, even if the absolute delay time would be very small (e.g. a few microseconds) because the speed is set to high. We shouldn't need to repaint if there was a recent repaint and the absolute time of the delay is small enough that we'll be back soon to do a further paint.
This is a regression from earlier Greenfoot versions which didn't force a repaint on every delay() call.
---
**Issue metadata**
- Issue type: Bug
- Priority: Medium
- Fix versions: 3.6.1Neil BrownNeil Brownhttps://gitlab.bluej.org/bluej/bjgf/-/issues/2161[GREENFOOT-834] Painting happens more often than needed when scenario running...2019-11-21T09:24:55ZNeil Brown[GREENFOOT-834] Painting happens more often than needed when scenario running full speedOur code was intended to prevent painting overly often in cases where the act cycle is running very fast -- if you are running the simulation at 20,000 FPS, there's no need to paint every frame, we only need to paint at 60-120 FPS at mos...Our code was intended to prevent painting overly often in cases where the act cycle is running very fast -- if you are running the simulation at 20,000 FPS, there's no need to paint every frame, we only need to paint at 60-120 FPS at most. The logic for this paint-skipping appears to have been damaged during refactoring, and Greenfoot 3.6.0 currently paints most frames even when running much faster than the screen can display.
---
**Issue metadata**
- Issue type: Bug
- Priority: Medium
- Fix versions: 3.6.1Neil BrownNeil Brownhttps://gitlab.bluej.org/bluej/bjgf/-/issues/2159[GREENFOOT-832] Incompatibility when working with more than one display2021-05-12T09:12:04ZNeil Brown[GREENFOOT-832] Incompatibility when working with more than one displayAt home I am working with 2 displays on macOS; in school it's Windows 10 with one display for each working station.
If I close a GF-project while the editor-window or the scenario-window is not on the primary display, then I get probl...At home I am working with 2 displays on macOS; in school it's Windows 10 with one display for each working station.
If I close a GF-project while the editor-window or the scenario-window is not on the primary display, then I get problems in the classroom: Either the scenario-window is "outside" the screen or the scenario-window is visible, but opening a class moves the editor-window "outside" the screen.
I encountered this problem already years ago, and probably it's not GF-specific. But it would be nice to have a solution.
---
**Issue metadata**
- Issue type: Bug
- Priority: Low
- Fix versions: 3.7.0Neil BrownNeil Brownhttps://gitlab.bluej.org/bluej/bjgf/-/issues/2157[GREENFOOT-830] Convert to new Color API dialog does wrong action2019-06-07T16:17:12ZNeil Brown[GREENFOOT-830] Convert to new Color API dialog does wrong actionWhen you open an old scenario, you are offered the option to convert it to the new greenfoot.Color API rather than the old java.awt.Color API. However, in Greenfoot 3.5.x, when the user clicks yes, nothing is done, and when they click n...When you open an old scenario, you are offered the option to convert it to the new greenfoot.Color API rather than the old java.awt.Color API. However, in Greenfoot 3.5.x, when the user clicks yes, nothing is done, and when they click no, the conversion is done.
---
**Issue metadata**
- Issue type: Bug
- Priority: Medium
- Fix versions: 3.6.0Neil BrownNeil Brownhttps://gitlab.bluej.org/bluej/bjgf/-/issues/2156[GREENFOOT-829] Cut/Copy/Paste on editor context menu do nothing2019-05-28T15:33:01ZNeil Brown[GREENFOOT-829] Cut/Copy/Paste on editor context menu do nothingThe fix for http://bugs.bluej.org/browse/GREENFOOT-623 checked if the editor pane was focused before executing these actions, but it seems that triggering the context menu also counts as a defocusing event, so this has broken the context...The fix for http://bugs.bluej.org/browse/GREENFOOT-623 checked if the editor pane was focused before executing these actions, but it seems that triggering the context menu also counts as a defocusing event, so this has broken the context menu events.
Probably the best fix will be to force their execution (skipping focus check) when triggered via context menu.
---
**Issue metadata**
- Issue type: Bug
- Priority: Medium
- Fix versions: 3.6.0Neil BrownNeil Brownhttps://gitlab.bluej.org/bluej/bjgf/-/issues/2154[GREENFOOT-827] Fix issue about JavaFX requirement for export to JAR2019-06-18T13:50:36ZNeil Brown[GREENFOOT-827] Fix issue about JavaFX requirement for export to JARGreenfoot requires JavaFX, including for the case when it has been exported to a standalone JAR. In Oracle Java 8 this was fine because JavaFX was included in the JDK so running the JAR would work fine on Oracle's Java 8. However with ...Greenfoot requires JavaFX, including for the case when it has been exported to a standalone JAR. In Oracle Java 8 this was fine because JavaFX was included in the JDK so running the JAR would work fine on Oracle's Java 8. However with OpenJDK 11, JavaFX is supplied separately and installed separately, so the Greenfoot JAR won't be runnable without also supplying the path for OpenJFX 11. We need to either bundle OpenJFX into the JAR itself (with issues about OS-specific libraries or not) or have an accompanying script/batch file which somehow locates the JAR and adds it to the class path. A more advanced alternative is to export using the Java Packager so that it is an everything-included installer for the scenario.
---
**Issue metadata**
- Issue type: Bug
- Priority: Medium
- Fix versions: 3.6.0Neil BrownNeil Brownhttps://gitlab.bluej.org/bluej/bjgf/-/issues/2153[GREENFOOT-826] Greenfoot can freeze while loading on Windows2019-05-03T12:30:41ZNeil Brown[GREENFOOT-826] Greenfoot can freeze while loading on WindowsGreenfoot can freeze when attempting to bring a window to the front (which happens on load) due to a deadlock between the event thread and the external bring-to-front script.
---
**Issue metadata**
- Issue type: Bug
- Priority: Medium...Greenfoot can freeze when attempting to bring a window to the front (which happens on load) due to a deadlock between the event thread and the external bring-to-front script.
---
**Issue metadata**
- Issue type: Bug
- Priority: Medium
- Fix versions: 3.5.4Neil BrownNeil Brownhttps://gitlab.bluej.org/bluej/bjgf/-/issues/2152[GREENFOOT-825] Window invisible on startup of coordinates out of screen2019-05-03T12:25:55ZMichael Kölling[GREENFOOT-825] Window invisible on startup of coordinates out of screenIt seems that the main scenario window can be out of screen. It should automatically be moved into the visible screen area on scenario open.
This also affects windows that were minimised in MS Windows, since they are assigned a nomina...It seems that the main scenario window can be out of screen. It should automatically be moved into the visible screen area on scenario open.
This also affects windows that were minimised in MS Windows, since they are assigned a nominal window position of -32000 / -32000.
Reported in Greenroom (26 Mar 2019: [Greenfoot Scenario starts invisible|https://greenroom.greenfoot.org/forums/1/topics/630]).
---
**Issue metadata**
- Issue type: Task
- Priority: Medium
- Fix versions: 3.5.4Neil BrownNeil Brownhttps://gitlab.bluej.org/bluej/bjgf/-/issues/2151[GREENFOOT-824] Placing a new actor in the world counts as a click2019-01-17T12:50:06ZNeil Brown[GREENFOOT-824] Placing a new actor in the world counts as a clickSet the scenario running, then use the class diagram context menu to create a new actor, which will appear under the mouse cursor, ready to be placed. If you then click in the world to place the actor, it also registers as a click on th...Set the scenario running, then use the class diagram context menu to create a new actor, which will appear under the mouse cursor, ready to be placed. If you then click in the world to place the actor, it also registers as a click on the actor/world underneath, which it should not do.
---
**Issue metadata**
- Issue type: Bug
- Priority: Medium
- Fix versions: 3.5.3Neil BrownNeil Brownhttps://gitlab.bluej.org/bluej/bjgf/-/issues/2150[GREENFOOT-823] Scenario does not (always) open with double-click on project....2019-05-03T16:03:45ZMichael Kölling[GREENFOOT-823] Scenario does not (always) open with double-click on project.greenfootDouble-click on the project.greenfoot file should open a scenario.
This works if Greenfoot is not running, but if Greenfoot is already open, then the new scenario does not open correctly (process starts, but no window appears). (Obser...Double-click on the project.greenfoot file should open a scenario.
This works if Greenfoot is not running, but if Greenfoot is already open, then the new scenario does not open correctly (process starts, but no window appears). (Observed on MacOS.)
---
**Issue metadata**
- Issue type: Bug
- Priority: Medium
- Fix versions: 3.5.4https://gitlab.bluej.org/bluej/bjgf/-/issues/2149[GREENFOOT-822] We should not save or restore window positions with negative ...2019-02-14T15:26:18ZHamza Hamza[GREENFOOT-822] We should not save or restore window positions with negative coordinates When the project file contains negative window coordinates, opening the scenario will minimize the Greenfoot window and it will not be restored. This is reported by the user Irzan Fajari, the scenario file is attached with a screenshot o...When the project file contains negative window coordinates, opening the scenario will minimize the Greenfoot window and it will not be restored. This is reported by the user Irzan Fajari, the scenario file is attached with a screenshot of the minimized window. The work-around to this issue in this scenario is to open the project in a text editor and remove the offending lines:
xPosition=-32000
yPosition=-32000
A proper solution for this is to detect the negative window positions and tries to correct them.
---
**Issue metadata**
- Issue type: Bug
- Priority: Medium
- Fix versions: 3.6.0Hamza HamzaHamza Hamzahttps://gitlab.bluej.org/bluej/bjgf/-/issues/2148[GREENFOOT-821] Edit/Duplicate/Delete not initially available on image in set...2018-11-22T14:55:46ZNeil Brown[GREENFOOT-821] Edit/Duplicate/Delete not initially available on image in set image dialogGo to Set Image... on an actor. If there is a default selected image in the scenario, then the cog context menu at the bottom has Edit/Duplicate/Delete disabled. They are only enabled once you select a different image then select the o...Go to Set Image... on an actor. If there is a default selected image in the scenario, then the cog context menu at the bottom has Edit/Duplicate/Delete disabled. They are only enabled once you select a different image then select the original one again.
---
**Issue metadata**
- Issue type: Bug
- Priority: Medium
- Fix versions: 3.5.3Neil BrownNeil Brownhttps://gitlab.bluej.org/bluej/bjgf/-/issues/2147[GREENFOOT-820] Click from actor placement is remembered during first act cycle2018-12-10T12:21:19ZDavin McCall[GREENFOOT-820] Click from actor placement is remembered during first act cycleReported by Thomas Karp on Blueroom:
{quote}there seem to be a bug when using Greenfoot.mouseClicked(…). A very short example is:
{code}
public class Fish extends Actor
{
public void act()
{
if(Greenfoot.mouseC...Reported by Thomas Karp on Blueroom:
{quote}there seem to be a bug when using Greenfoot.mouseClicked(…). A very short example is:
{code}
public class Fish extends Actor
{
public void act()
{
if(Greenfoot.mouseClicked(this))
javax.swing.JOptionPane.showMessageDialog(null, "Hallo");
}
}
{code}
When I create a fish by right-clicking its class and then run the scenario, “Hallo” appears (most of the time). The click to create the fish seem to be stored. Then everything works like it should. When I create a fish in the world, then run the scenario, everything is fine. But when I create it in the world, after that I click the fish, and than click “Run”, the click event fires again. So it seems to be stored in this case again.
I think a click-event should only be handled after the Run-button is clicked.
{quote}
---
**Issue metadata**
- Issue type: Bug
- Priority: Medium
- Fix versions: 3.5.3Neil BrownNeil Brownhttps://gitlab.bluej.org/bluej/bjgf/-/issues/2146[GREENFOOT-819] Greenfoot project read-only warning not showing on Windows2018-11-13T14:20:03ZNeil Brown[GREENFOOT-819] Greenfoot project read-only warning not showing on WindowsOn Mac, if you `chmod -R a-w` on a directory then open that as a Greenfoot scenario, you correctly get the dialog telling you the project is read-only and you need to save elsewhere first. On Windows, if you right-click a folder, tick "...On Mac, if you `chmod -R a-w` on a directory then open that as a Greenfoot scenario, you correctly get the dialog telling you the project is read-only and you need to save elsewhere first. On Windows, if you right-click a folder, tick "read only" then apply and say apply recursively, then when you open in Greenfoot, you don't get a warning, but you'll get problems editing code and so on. I'm not 100% confident about different Windows permissions (e.g. the Security tab for the folder still says I have access) but I think this should be enough for Greenfoot to show the read-only dialog on Windows.
---
**Issue metadata**
- Issue type: Bug
- Priority: MediumNeil BrownNeil Brownhttps://gitlab.bluej.org/bluej/bjgf/-/issues/2144[GREENFOOT-817] World instantiation error2018-11-20T16:18:44ZMichael Kölling[GREENFOOT-817] World instantiation errorEdit the world class. Focus the main window. Auto-compile and world instantiation happens as planned - all good.
But:
Edit the world class. COMPILE IN EDITOR. Focus the main window. World instantiation does not happen - error.
...Edit the world class. Focus the main window. Auto-compile and world instantiation happens as planned - all good.
But:
Edit the world class. COMPILE IN EDITOR. Focus the main window. World instantiation does not happen - error.
---
**Issue metadata**
- Issue type: Bug
- Priority: Highhttps://gitlab.bluej.org/bluej/bjgf/-/issues/2143[GREENFOOT-816] Auto-compiling too few classes2019-12-02T13:10:06ZMichael Kölling[GREENFOOT-816] Auto-compiling too few classesOpen an Actor subclass. Make a change. Focus main window.
The scenario should now compile.
Instead, only the edited class is compiled. (E.g. if the world class has a reference to this class, and was also uncompiled, it is not compi...Open an Actor subclass. Make a change. Focus main window.
The scenario should now compile.
Instead, only the edited class is compiled. (E.g. if the world class has a reference to this class, and was also uncompiled, it is not compiled, no world is created.)
---
**Issue metadata**
- Issue type: Bug
- Priority: High
- Fix versions: 3.6.1Neil BrownNeil Brownhttps://gitlab.bluej.org/bluej/bjgf/-/issues/2141[GREENFOOT-814] Double-clicking project file does not work on Mac if Greenfoo...2019-01-22T14:34:55ZNeil Brown[GREENFOOT-814] Double-clicking project file does not work on Mac if Greenfoot is already openOn Mac: Open Greenfoot, then double-click on a Greenfoot project file in Finder. Greenfoot does not open the project.
---
**Issue metadata**
- Issue type: Bug
- Priority: Medium
- Fix versions: 3.5.3On Mac: Open Greenfoot, then double-click on a Greenfoot project file in Finder. Greenfoot does not open the project.
---
**Issue metadata**
- Issue type: Bug
- Priority: Medium
- Fix versions: 3.5.3Neil BrownNeil Brownhttps://gitlab.bluej.org/bluej/bjgf/-/issues/2140[GREENFOOT-813] Quitting Greenfoot briefly displays "create a new scenario" m...2019-09-25T14:56:08ZDavin McCall[GREENFOOT-813] Quitting Greenfoot briefly displays "create a new scenario" message.When quitting Greenfoot, the current scenario is visible closed with the "create a new scenario" message briefly displayed before Greenfoot actually exits.
---
**Issue metadata**
- Issue type: Bug
- Priority: Medium
- Fix version...When quitting Greenfoot, the current scenario is visible closed with the "create a new scenario" message briefly displayed before Greenfoot actually exits.
---
**Issue metadata**
- Issue type: Bug
- Priority: Medium
- Fix versions: 3.6.1Pierre Weill-TessierPierre Weill-Tessierhttps://gitlab.bluej.org/bluej/bjgf/-/issues/2139[GREENFOOT-812] Object names not shown on inspectors2021-04-29T10:41:12ZDavin McCall[GREENFOOT-812] Object names not shown on inspectorsWhen inspecting an actor object, no object name is shown. The name is useful for typing as a parameter to another method (although it is still possible to insert the name by clicking the object when the interactive method call dialog is ...When inspecting an actor object, no object name is shown. The name is useful for typing as a parameter to another method (although it is still possible to insert the name by clicking the object when the interactive method call dialog is open).
This was part of GREENFOOT-811.
---
**Issue metadata**
- Issue type: Task
- Priority: High
- Fix versions: 3.7.0Neil BrownNeil Brownhttps://gitlab.bluej.org/bluej/bjgf/-/issues/2138[GREENFOOT-811] NPE raised when passing actor as a parameter2018-11-02T17:18:57ZHamza Hamza[GREENFOOT-811] NPE raised when passing actor as a parameterThis is reported by the user using Greenfoot 3.5.1. Currently, the names of objects can not appear on the inspector, it shows only the name of the class. When clicking on an object to pass its name as a parameter to a method related to a...This is reported by the user using Greenfoot 3.5.1. Currently, the names of objects can not appear on the inspector, it shows only the name of the class. When clicking on an object to pass its name as a parameter to a method related to another object (it shows name like golf_ ), it gives null pointer exception in the terminal window and it also generates the following in the debug log:
"unknown enum constant threadchecker.Tag.Any
reason: class file for threadchecker.Tag not found
unknown enum constant threadchecker.Tag.Any
Handling 69"
---
**Issue metadata**
- Issue type: Bug
- Priority: Medium
- Fix versions: 3.5.2Davin McCallDavin McCall