We still sometimes use FSlowTask for a few things in the editor SDK. While a bit nice that we can use it to guarantee 0 state changes will happen --- it's a bit error prone and seems overkill for a few of our current uses.
So, we should just replace it with "disabling the beamable window along with a notification regarding the work that's being done".
We still sometimes use FSlowTask for a few things in the editor SDK. While a bit nice that we can use it to guarantee 0 state changes will happen --- it's a bit error prone and seems overkill for a few of our current uses.
So, we should just replace it with "disabling the beamable window along with a notification regarding the work that's being done".