@pascal @wim
this is a very annoying bug.
I was teaching Rhino the hole day and I use the commandline to check success / failure of commands.
… and I also teach to do so…
2 curves joined into one open curve.
2 curves joined into one closed curve.
In the preparation of the course I did some tutorial videos that I can do again as soon as this bug is fixed…
please give it a decent priority - thanks.
kind regards -tom
Yep, thanks - it is on the devleoper’s pile. I don’t see any reason it would not be fixed for the V8 release.
-Pascal
I came to post about this after being bothered by it for a very long time. I’m on V7 / Ventura / Intel currently, but I’m fairly sure this was happening at least under Monterey. I know it’s persisted through multiple Rhino updates, because it’s the first thing I check to see if it’s been fixed yet.
I’m sure you have a system for prioritising bugs but, reinforcing other posts above, if an hour’s work could fix this, that would be worth more to me than some other issues that you’re likely spending weeks on. In particular, it is very hard to use measurement commands when every action clears their results from the screen.
Hi -
I understand this is not what you want to hear, but the top priority for all developers at this point is to get Rhino 8 released. This particular issue is currently on the 8.1 list.
-wim
that is not acceptable, i am not going to buy Rhino 8 just to be able to use the command history again!! common guys really not.
and no dont suggest us to spend a day to role back the mac os version. please fix that for 7 either.
Yes - I agree.
I know I am beating a dead horse, but here we go:
I asked John if this can be prioritized
Its better, but still easy to break:
for(int i = 0; i < 100; i++) {
RhinoApp.WriteLine("Test: " + i.ToString());
}
After running this a few times it scrolls only halfway or more, but never to the end. And does not recover. Dragging a box etc. results in erratic jumping around. Once the Buffer is is full (around 4k lines) it stablizies a bit, but still:
What i see:
what it is:
Edit:
I don’t think my script has anything specifically to do with it, so i assume it would fail after an hour of work… Also for the screenshots i removed the panel from the dock, this makes no difference.
Same for the bottom panel:
@atair I could not reproduce the behavior your are seeing. I only get a slight issue in the panel, when printing to the commandline with a script, see YT report.
FYI I tested this in 14.0 Sonoma on an intel Mac
I am still on 13, and just tested again without any scipts - just repeat command about 30 times (pressing enter over and over):
what i get
what is should be:
fresh file, didnt touch anything else
@dan could not reproduce either on a mac M1 on Sonoma. Do you plan upgrading to Sonoma as well @atair and see if this resolves things for you?
eventually - but because of Rhino / unity - xcode etc I wait a few more weeks… lets see if someone else can reproduce it in the meantime
Version 8 BETA (8.0.23271.13234, 2023-09-28)
Expires November 12, 2023
mac os x 13.5.1 (22G90)
I can confirm that the scroll behaviour of the command line still is buggy.
(sorry - and thanks for the effort)
i m doing some scrolling in the video with the trackpad - which is not really visible on the screen capture…(the magic movements are trackpad-scrolling)
scrolling to the top will make the panel stuck to this position.
Hi @atair,
We have this already logged, fixed and tested::RH-73417 - CommandHistory-doesnt-scroll-to-the-bottom
Looks like it has been tested and will be available in the next BETA.
You will be notified here when it is in the next Rhino 8 Beta build and it is ready for you to test out…
Thanks, ,
Mary Ann Fugier
sorry but this is still fundamentally broken - after 30-40 commands it does not scroll anymore. Even before it catches up sometimes only after 1-2 commands.
Just updated MacOS to Sonoma, now I have this bug too. 
