Hourglass while processing data

[osuire]

It would be nice to have some kind of visual indication that GH is processing data ; something like the proverbial hourglass .
Using Human UI, we often have the case of users pressing multiple time boolean toggles that control time-consuming processes, and they go crazy because they never see any outcome.
They don’t realize that they are interrupting and resetting time-consuming processes, but they can’t really be blamed because they don’t know if something is actually happening.
Did they mis-fire by pressing the toggle too swiftly ? Is the whole thing crashed ? Are we living in a simulation devised by super-intelligent guinea pigs ?

As mentionned in another request, it would be nice to have a real “kill-switch” that would effectively stop a process without having to resort to the old “Ctrl-alt-esc” method.

[DavidRutten]

This is planned. The idea is to run solutions both on multiple threads and on non-UI threads. This should result both in faster solutions and a UI which remains live.

Async, UI & Computation

Just asking! I know this is a redacted kind of request/wish/etc., but: would it not be wonderful if SolveInstance would be on the lines of an async (really don’t care wether the multithreaded way or reactor pattern à la node) function that essentially communicates back in an evented way, to the ui and to the rest of the graph? There’s a zillion ways of doing this in .net nowadays, and I know this implies a rather big architectural change - but if not here, where else could i ask? PS: I know th…

[idid (Dimitrie)]

I’m just going to keep liking everything about this. David, this is quite the statement! Would love to get dirty with this, but I’m sure you guys have everything in control. Please excuse this post that doesn’t really contribute anything besides emojis to the conversation.

[DavidRutten]

@idid

but I’m sure you guys have everything in control.

I wish I had your level of confidence

[idid (Dimitrie)]

well async control, at least wrapped in a try { } catch { }