bjgf issueshttps://gitlab.bluej.org/bluej/bjgf/-/issues2022-04-21T14:05:02Zhttps://gitlab.bluej.org/bluej/bjgf/-/issues/2187[GREENFOOT-860] Greenfoot, GreenfootSound, Color … don't autocomplete2022-04-21T14:05:02ZNeil Brown[GREENFOOT-860] Greenfoot, GreenfootSound, Color … don't autocompleteHi,
with the Stride-editor you type something like "gr" and hit cmd+space, all necessary autocompletements like Greenfoot.…, GreenfootImage… etc. are shown and can be used.
With the Java-editor this does not work. See screenshot attach...Hi,
with the Stride-editor you type something like "gr" and hit cmd+space, all necessary autocompletements like Greenfoot.…, GreenfootImage… etc. are shown and can be used.
With the Java-editor this does not work. See screenshot attached.
I used the Stride-editor for some years now, and as you use Greenfoot-methods like isKeyDown(…) all the time the autocompletement is crucial in my opinion.
So I am not sure if this is a bug or somehow intentional. If yes I would ask to urgently fix this - having the students type "Greenfoot." to get to the autocompletements is not only a waste of time but also a source of errors. (Addendum: The same, even worse, with not recognizing locally declared variables - see my comments, sorry, could not delete the wrong one).
(As attaching images is not supported with this interface please find it here: [https://efm.informatik-bg.de/210919_greenfoot-autocomplete-problem.jpg] )
---
**Issue metadata**
- Issue type: Bug
- Priority: MediumGreenfoot 3.7.1https://gitlab.bluej.org/bluej/bjgf/-/issues/2186[GREENFOOT-859] Terminating ask-method in World-constructor leads to unexpect...2021-07-06T14:31:58ZNeil Brown[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-...(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: Lowesthttps://gitlab.bluej.org/bluej/bjgf/-/issues/2177[GREENFOOT-850] Focus of insertpoint on wrong place2021-07-03T21:19:15ZNeil Brown[GREENFOOT-850] Focus of insertpoint on wrong placeWhen you are calling methods that don't need a parameter sometimes the insertpoint goes inside the brackets if you autocomplete the methodename with strg+space. This is very annoying as you always have to move the insertpoint manually ou...When you are calling methods that don't need a parameter sometimes the insertpoint goes inside the brackets if you autocomplete the methodename with strg+space. This is very annoying as you always have to move the insertpoint manually outside the brackets.
Right now I only can reconstruct cases where a method is called at the beginning of a line, but I remember that I had the same problem also in some cases in middle of a line.
Reconstruct it: Create a Stride-scenario, then
* go e.g. to an Actor-class and type getWorld() at the beginning of the line. (only type getw and autocomplete with strg-space);
* go e.g. go to a World-class and type getWidth() at the beginning of a line.
---
**Issue metadata**
- Issue type: Bug
- Priority: Mediumhttps://gitlab.bluej.org/bluej/bjgf/-/issues/2173[GREENFOOT-846] Cursor Missing2021-05-12T17:10:57ZBabis Kyfonidis[GREENFOOT-846] Cursor MissingI started GreenFoot, I added a 'try-catch' block and I deleted the outer frame immediately. It generated the empty box described in the 845 bug an the cursor disapeared
---
**Issue metadata**
- Issue type: Bug
- Priority: Medium
- Fix...I started GreenFoot, I added a 'try-catch' block and I deleted the outer frame immediately. It generated the empty box described in the 845 bug an the cursor disapeared
---
**Issue metadata**
- Issue type: Bug
- Priority: Medium
- Fix versions: 3.7.0Pierre Weill-TessierPierre Weill-Tessierhttps://gitlab.bluej.org/bluej/bjgf/-/issues/1803[GREENFOOT-459] Add 'Cmd-m' shortcut on Mac to minimise window2021-05-12T09:13:18ZMichael Kölling[GREENFOOT-459] Add 'Cmd-m' shortcut on Mac to minimise window'Cmd-m' on Mac to minimise a window is a system-wide convention. We should support it (on all top level windows).
This means to change the shortcut for 'Insert method' in the Java editor (which I think is Cmd-m currently).
---
**Issue...'Cmd-m' on Mac to minimise a window is a system-wide convention. We should support it (on all top level windows).
This means to change the shortcut for 'Insert method' in the Java editor (which I think is Cmd-m currently).
---
**Issue metadata**
- Issue type: Task
- Priority: Low
- Fix versions: 3.7.0Neil 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/2185[GREENFOOT-858] The execution twirler does not show when user code takes a lo...2021-05-12T09:09:36ZNeil Brown[GREENFOOT-858] The execution twirler does not show when user code takes a long time to runGreenfoot has a feature where an execution twirler control shows if the user code takes too long, which provides help if the user has coded an infinite loop or similar. This was broken in version 3.6.1, such that it no longer shows. It...Greenfoot has a feature where an execution twirler control shows if the user code takes too long, which provides help if the user has coded an infinite loop or similar. This was broken in version 3.6.1, such that it no longer shows. It should be fixed.
---
**Issue metadata**
- Issue type: Bug
- Priority: Medium
- Fix versions: 3.7.0Neil BrownNeil Brownhttps://gitlab.bluej.org/bluej/bjgf/-/issues/2176[GREENFOOT-849] Greenfoot.ask in World-constructor not shown / blocking World...2021-05-12T09:08:52ZNeil Brown[GREENFOOT-849] Greenfoot.ask in World-constructor not shown / blocking World-constructionOne of my students created a scenario where in the constructor some code like
{{this.username = Greenfoot.ask("What's your name?")}}
is used. In most cases the project does not compile due to "World needs compiling". I can open cla...One of my students created a scenario where in the constructor some code like
{{this.username = Greenfoot.ask("What's your name?")}}
is used. In most cases the project does not compile due to "World needs compiling". I can open classes, change everything etc. It seems that the input-dialogue somehow is hidden and waits for being sent.
I tried to duplicate the project even manually, and it worked without problems. But after a few recompilations it showed the same behavior.
---
**Issue metadata**
- Issue type: Bug
- Priority: Low
- Fix versions: 3.7.0Neil BrownNeil Brownhttps://gitlab.bluej.org/bluej/bjgf/-/issues/2179[GREENFOOT-852] Blue insert-marker sometimes disappears2021-05-11T16:53:18ZNeil Brown[GREENFOOT-852] Blue insert-marker sometimes disappearsIn school my students with Windows 10 and Greenfoot 3.6.1. While at home (macOS) I never encounter this problem, sometimes the blue marker just disappears at the machines of my students. The Stride-editor ist still working as expected ex...In school my students with Windows 10 and Greenfoot 3.6.1. While at home (macOS) I never encounter this problem, sometimes the blue marker just disappears at the machines of my students. The Stride-editor ist still working as expected except for the case that you can no more see the blue insertion-marker (so you e.g. have to press the space-key to see where you are). Restarting Greenfoot fixes it.
It's happening not often (15 students working 60 minutes, perhaps 2, 3 occurrences of the bug).
No idea how this could be replicated.
---
**Issue metadata**
- Issue type: Bug
- Priority: Low
- Fix versions: 3.7.0https://gitlab.bluej.org/bluej/bjgf/-/issues/2172[GREENFOOT-845] Delete outer frame creates an empty bordered box2021-05-11T15:15:31ZBabis Kyfonidis[GREENFOOT-845] Delete outer frame creates an empty bordered boxWhen I tried to delete the outer frame an empty box with a black border appeared in the screen
---
**Issue metadata**
- Issue type: Bug
- Priority: Low
- Fix versions: 3.7.0When I tried to delete the outer frame an empty box with a black border appeared in the screen
---
**Issue metadata**
- Issue type: Bug
- Priority: Low
- Fix versions: 3.7.0Pierre Weill-TessierPierre Weill-Tessierhttps://gitlab.bluej.org/bluej/bjgf/-/issues/2056[GREENFOOT-723] Stride editor : Wrong position of the rectangle border when b...2021-05-10T21:58:32ZHamza Hamza[GREENFOOT-723] Stride editor : Wrong position of the rectangle border when bird's eye view is selected and then font size is increased Stride editor: when choosing the birds eye view and increasing the font size, the focus black border rectangle will move into a wrong place (tested on Windows)
---
**Issue metadata**
- Issue type: Bug
- Priority: Medium
- Fix versions...Stride editor: when choosing the birds eye view and increasing the font size, the focus black border rectangle will move into a wrong place (tested on Windows)
---
**Issue metadata**
- Issue type: Bug
- Priority: Medium
- Fix versions: 3.7.0Pierre Weill-TessierPierre Weill-Tessierhttps://gitlab.bluej.org/bluej/bjgf/-/issues/1879[GREENFOOT-541] Empty slots do not expand when the frame cursor is moved into...2021-05-07T15:17:21ZDavin McCall[GREENFOOT-541] Empty slots do not expand when the frame cursor is moved into themMost frames expand by the size of the cursor when the cursor enters them (and reduce accordingly when the cursor leaves). Empty frames are an exception to this - they remain the same size when the frame cursor enters/leaves.
This has ...Most frames expand by the size of the cursor when the cursor enters them (and reduce accordingly when the cursor leaves). Empty frames are an exception to this - they remain the same size when the frame cursor enters/leaves.
This has the perturbing effect of causing the document size to "wobble" as you use the up/arrow keys to navigate. When entering an empty frame, the entire document becomes slightly shorter, and when leaving the empty frame the document becomes slightly longer.
---
**Issue metadata**
- Issue type: Bug
- Priority: Medium
- Fix versions: 3.7.0Pierre Weill-TessierPierre Weill-Tessierhttps://gitlab.bluej.org/bluej/bjgf/-/issues/2178[GREENFOOT-851] Word misspeling in German2021-05-05T15:57:23ZBabis Kyfonidis[GREENFOOT-851] Word misspeling in Germanin the contextmenu in the Stride editor. The menus entry for deleting a frame is labled "Läschen", whereas "Löschen" would be correct.
---
**Issue metadata**
- Issue type: Bug
- Priority: Medium
- Fix versions: 3.7.0in the contextmenu in the Stride editor. The menus entry for deleting a frame is labled "Läschen", whereas "Löschen" would be correct.
---
**Issue metadata**
- Issue type: Bug
- Priority: Medium
- Fix versions: 3.7.0Pierre Weill-TessierPierre Weill-Tessierhttps://gitlab.bluej.org/bluej/bjgf/-/issues/1885[GREENFOOT-547] "you just deleted a large piece of code." is triggered even ...2021-05-05T11:06:43ZNeil Brown[GREENFOOT-547] "you just deleted a large piece of code." is triggered even with small pieces of code.In a class, creating a comment of, say 15 characters or more and
removing its frame triggers: "you just deleted a large piece of code."
message. Maybe this is too small to trigger such message?
---
**Issue metadata**
- Issue type:...In a class, creating a comment of, say 15 characters or more and
removing its frame triggers: "you just deleted a large piece of code."
message. Maybe this is too small to trigger such message?
---
**Issue metadata**
- Issue type: Bug
- Priority: Mediumhttps://gitlab.bluej.org/bluej/bjgf/-/issues/1726[GREENFOOT-382] Can't perform terminal input from world constructor2021-05-05T09:26:53ZDavin McCall[GREENFOOT-382] Can't perform terminal input from world constructorWhen you construct the world, Greenfoot doesn't recognize that the program is running and terminal input is disabled.
---
**Issue metadata**
- Issue type: Bug
- Priority: Low
- Fix versions: 3.7.0When you construct the world, Greenfoot doesn't recognize that the program is running and terminal input is disabled.
---
**Issue metadata**
- Issue type: Bug
- Priority: Low
- Fix versions: 3.7.0Neil BrownNeil Brownhttps://gitlab.bluej.org/bluej/bjgf/-/issues/1715[GREENFOOT-371] Provide more help after objects have removed themselves2021-05-05T09:25:29ZNeil Brown[GREENFOOT-371] Provide more help after objects have removed themselvesIt's possible for an actor to remove itself from the world mid-act(). If the code tries to do anything more that relates to the world (e.g. moving), an exception is thrown (NotInWorldException or something?). Lots of people on the Gree...It's possible for an actor to remove itself from the world mid-act(). If the code tries to do anything more that relates to the world (e.g. moving), an exception is thrown (NotInWorldException or something?). Lots of people on the Greenfoot forum seem to get confused by this exception despite the fact that the exception message tells them what may have gone wrong.
We should be able to identify specifically the case where an actor has removed itself mid-act() and is moving *after* being removed from the world (as opposed to the other cause of this exception: moving *before* being added to the world) \-\- because we know which Actor we are currently invoking act() on. If the actor being act()ed on is the one who isn't in the world, it must be because they've just removed themselves (there's no other way that Greenfoot would be calling act() on them and yet they aren't in the world). So we could be more specific in the exception to say:
"Actor has already been removed from the world \-\- stop executing code after you remove yourself from the world\! And read these messages\!"
---
**Issue metadata**
- Issue type: Task
- Priority: Medium
- Fix versions: 3.7.0Neil BrownNeil Brownhttps://gitlab.bluej.org/bluej/bjgf/-/issues/1954[GREENFOOT-619] Implement possibility to update to 3.0.0-API automatically (e...2021-05-02T19:15:01ZNeil Brown[GREENFOOT-619] Implement possibility to update to 3.0.0-API automatically (even if clicked away the first time)When you open an 3.0.x-scenario with 3.1 you are prompted with the question if you want to automatically update to the 3.0.0-API. If you click "no, I will updated later manually" you never will get the possibility to update automatically...When you open an 3.0.x-scenario with 3.1 you are prompted with the question if you want to automatically update to the 3.0.0-API. If you click "no, I will updated later manually" you never will get the possibility to update automatically (at least I was not able to find it). This is very annoying if you have a lot of classes which you have to update manually. I think a lot of teachers have a lot of scenarios which they want to update comfortably.
As the 3.x-API shall be pushed by force I would recommend to open the dialog each time the scenario opens. Alternatively add a menu-item.
---
**Issue metadata**
- Issue type: Task
- Priority: Mediumhttps://gitlab.bluej.org/bluej/bjgf/-/issues/1704[GREENFOOT-360] Scaling image doesn't update actor size/bounds2021-04-30T12:09:56ZDavin McCall[GREENFOOT-360] Scaling image doesn't update actor size/boundsWhen an actor's image is scaled, the actor size (for collision checking purposes) is not recalculated.
(This is perhaps an API design flaw rather than a behavioural bug \\- i.e. maybe it shouldn't be possible to scale an image "in plac...When an actor's image is scaled, the actor size (for collision checking purposes) is not recalculated.
(This is perhaps an API design flaw rather than a behavioural bug \\- i.e. maybe it shouldn't be possible to scale an image "in place"; rather, scaling should return a new image).
---
**Issue metadata**
- Issue type: Bug
- Priority: LowDavin McCallDavin McCallhttps://gitlab.bluej.org/bluej/bjgf/-/issues/1727[GREENFOOT-383] CSV string storage broken2021-04-30T11:52:33ZNeil Brown[GREENFOOT-383] CSV string storage brokenThere was a character set issue on Windows (fixed in trunk), there is also a problem with the character 13 (\r) not being stored and retrieved properly. So not every valid String can be stored and loaded again locally (though it does no...There was a character set issue on Windows (fixed in trunk), there is also a problem with the character 13 (\r) not being stored and retrieved properly. So not every valid String can be stored and loaded again locally (though it does now work on the gallery) \-\- this should be fixed.
---
**Issue metadata**
- Issue type: Bug
- Priority: MediumNeil BrownNeil Brownhttps://gitlab.bluej.org/bluej/bjgf/-/issues/1698[GREENFOOT-354] Change the speed slider2021-04-30T10:17:37ZNeil Brown[GREENFOOT-354] Change the speed sliderCurrently, in terms of frames per second (which is how most users seem to think of speed: basically, the frequency with which act() will be called), the Greenfoot speed slider is exponential. I did the maths a while back when someone as...Currently, in terms of frames per second (which is how most users seem to think of speed: basically, the frequency with which act() will be called), the Greenfoot speed slider is exponential. I did the maths a while back when someone asked, and here's the slider value on the left (1--100) and FPS value on the right (assuming that each act/redraw takes 0 time):
{noformat}
1: 0.11 FPS
6: 0.22
11: 0.41
16: 0.78
21: 1.48
26: 2.82
31: 5.36
36: 10.19
41: 19.38
46: 36.83
51: 70.00
56: 133.06
61: 252.92
66: 480.75
71: 913.80
76: 1736.95
81: 3301.56
86: 6275.57
91: 11928.62
96: 22673.68
{noformat}
As you can see, probably only about 35% of the range has sensible values for running the simulation and seeing the differences (which I'd characterise as maybe 1--100 FPS). The upper end of the FPS will never be achieved, it will just run at max speed once it can't keep up with the desired FPS, so I doubt you can do more than a few hundred frames per second. There's a few options to make the slider more usable:
1. We could change the slider to be FPS (perhaps just mapping the 1--100 slider range to 1--100 FPS). This is simple and understandable in terms of understanding it, but in practice it may appear jumpy at the lower end: going from 1--5 FPS runs the simulation five times as fast, but 90--95 will be almost no difference.
2. We could keep the slider as exponential, but limit it to a more useful range. So the bottom could be 1 FPS, the top could be, say, 1024 FPS, but it could be exponential between those two. So you would have a mapping like:
{noformat}
1: 1 FPS
11: 2
21: 4
31: 8
41: 16
51: 32
61: 64
71: 128
81: 256
91: 512
100: ~1000
{noformat}
This has the nice property that the middle of the slider maps to around 30 FPS, which seems like a reasonable default. (I need to look up what the current default speed is...)
---
**Issue metadata**
- Issue type: Task
- Priority: LowNeil BrownNeil Brown