2 ms·

> The multitasking model of UWP seems to be phone-first, which is just out of place for me. When I have a desktop PC that's plugged in and has 16gb of RAM, my w

by coldpie 10y ago

> The multitasking model of UWP seems to be phone-first, which is just out of place for me. When I have a desktop PC that's plugged in and has 16gb of RAM, my web browser should never just spontaneously CLOSE because I tab out to another window. I haven't used Windows in a decade. This really happens? UWP programs just spontaneously close on desktop computers? I really can't believe that.

DiNovi 10y ago
I think he means it auto minimizes to the tray
cwyers 10y ago
So, open/close is a bit of a weird distinction here? The program doesn't close in the way a Win32 program does, if I open Edge back up everything is as I left it -- all the tabs are still there, everything is where I left it, if I'm halfway through filling out a form everything I've filled out is still there. But yeah, at least when I first started using it, Edge would just vanish sometimes. I should note that I don't know if this is still an issue, I've basically given up on sustained Edge usage for now.
Already__Taken 10y ago
I've not seen that but I thought UWP apps don't really close either. They sort of hibernate because they should restore in whatever state you left them.
deleted 10y ago
[deleted]
contextfree 10y ago
I guess there are a couple things this could refer to - * On desktop Windows in desktop mode, modern apps are suspended when they're minimized or the user switches away from the virtual desktop they're on. Background operations that need to meant to continue are supposed to use various officially supported background task APIs. This is intended to be transparent to the user. * AIUI in situations where the OS detects an app is hung and would put up a ghost window with a "not responding" message if it were a classic app, the OS will just straight up kill a modern app. The theory is that this will force developers to make more responsive apps. So AFAIK there are no situations where a "well-behaved" app is supposed to spontaneously close from the user's POV, but for modern apps the OS is stricter about trying to enforce "good behavior". TBH though I think what the GP was seeing was probably just Edge crashing on its own.

by coldpie 10y ago

DiNovi 10y ago

I think he means it auto minimizes to the tray

cwyers 10y ago

So, open/close is a bit of a weird distinction here? The program doesn't close in the way a Win32 program does, if I open Edge back up everything is as I left it -- all the tabs are still there, everything is where I left it, if I'm halfway through filling out a form everything I've filled out is still there. But yeah, at least when I first started using it, Edge would just vanish sometimes. I should note that I don't know if this is still an issue, I've basically given up on sustained Edge usage for now.

Already__Taken 10y ago

I've not seen that but I thought UWP apps don't really close either. They sort of hibernate because they should restore in whatever state you left them.

deleted 10y ago

[deleted]

contextfree 10y ago

I guess there are a couple things this could refer to - * On desktop Windows in desktop mode, modern apps are suspended when they're minimized or the user switches away from the virtual desktop they're on. Background operations that need to meant to continue are supposed to use various officially supported background task APIs. This is intended to be transparent to the user. * AIUI in situations where the OS detects an app is hung and would put up a ghost window with a "not responding" message if it were a classic app, the OS will just straight up kill a modern app. The theory is that this will force developers to make more responsive apps. So AFAIK there are no situations where a "well-behaved" app is supposed to spontaneously close from the user's POV, but for modern apps the OS is stricter about trying to enforce "good behavior". TBH though I think what the GP was seeing was probably just Edge crashing on its own.