If you refresh you shouldn't lose everything you've done

Bugs
1

Because the builder has quite a few bugs that require a refresh, I press refresh often and lose work.

You should save when the button is pressed and then refresh, and not require us to use the revisions to continue.

It’s poor UX that needs addressing.

Thanks

1 Like
2

Hi Dean,

when - except for the strange ghost element thing, that rarely occurs in my tests so far (yes, it’s still annoying, I know) - are you required to reload the whole tab?

Best regards,
timmse

3

I’m actually having consistent issues (I’ve had a lot of bugs in the last 24 hours) that require me to refresh. Quite a lot of changes I make atm require a refresh (things like inputs not working, things saying REMS when they’re pxs), structure panel not being accurate/just not displaying elements that are actually on the canvas.

I’ve recorded a bunch of looms that I’ll report here soon. Although they’re not all consistently reproducible, they’re hopefully helpful and will help create a more stable product for 1.3.8 so I don’t need to refresh every couple of minutes :slight_smile:

2 Likes
4

I’m with @Deanphillips here. I often have to refresh because things in the canvas are out of whack, and if I happen to forget to save, I lose everything since last save. Autosave also doesn’t work.

I would really like to see a hotfix prior to 1.3.8 that fixes bugs—there are a lot of them.

5

When will this issue be addressed?

1 Like