Closed arthurhjorth closed 5 years ago
When you reshow the model should it remember the last speed you had it at or set the speed to the parent's speed?
That's a really good question. I think when I'm playing through the use cases in my head, that I would prefer for it to run at its parent's speed. But that's just my gut feeling. What do you think?
On Thu, Jul 18, 2019, 09:57 Bryan Head notifications@github.com wrote:
When you reshow the model should it remember the last speed you had it at or set the speed to the parent's speed?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/NetLogo/LevelSpace/issues/136?email_source=notifications&email_token=AAOGJ22BSZ7CDKRTJL5TUVDQACHE7A5CNFSM4HZGPPV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2I6JGA#issuecomment-512877720, or mute the thread https://github.com/notifications/unsubscribe-auth/AAOGJ2YXULDUJKMHD27FUQLQACHE7ANCNFSM4HZGPPVQ .
Um, I think full speed actually makes more sense now that I think about it. Doesn't seem like there's much point in limiting it.
Maybe, yeah. I don't think I have too strong feelings about any of these options. For "event-zoom" models it is nice to be able to open them and play them slowly during the critical event. (Though it does raise a question of whether we want to introduce a programmatic way of dealing with this too...)
Oh, I'll have it remember the speed from when it was hidden. So we'll get that for free.
On Fri, Jul 19, 2019 at 5:27 AM Arthur Hjorth notifications@github.com wrote:
Maybe, yeah. I don't think I have too strong feelings about any of these options. For "event-zoom" models it is nice to be able to open them and play them slowly during the critical event. (Though it does raise a question of whether we want to introduce a programmatic way of dealing with this too...)
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/NetLogo/LevelSpace/issues/136?email_source=notifications&email_token=AAAG4N3XY3QTMVGEZ3ZVKEDQAGXLRA5CNFSM4HZGPPV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2LPOKA#issuecomment-513210152, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAG4N2QIELJRTRCBTNZCWLQAGXLRANCNFSM4HZGPPVQ .
-- Bryan Head PhD Candidate, Computer Science Center for Connected Learning and Computer-Based Modeling Department of Electrical Engineering and Computer Science Northwestern University
while revising the levelspace paper I was reviewing the models to make sure they were up to scratch for 6.1.0. Specifically I looked at the Wolf Chase Sheep LS model, and slowed down the chase model to see what was happening. When I hid it, the parent model still ran extremely slowly.
On the one hand, maybe it's annoying to automatically take over control on a model that the user has specifically slowed down. On the other hand, when would one ever want a model that one is not even looking at to run slowly?
If we decide to do this, we could save the speed state of a model and revert to that once the user shows it again?
Thoughts, @qiemem ? Anyone else?