New app still doesn't remember window size

[QuarkZ 14]

Hello,

I was hoping this would be fixed with the new app since many people complained about this very thing and the answer was "wait for our new app"

When I open the app, everytime I have to maximize it, it never remembers it, which, while not being a big issue, is properly annoying, especially as a known ongoing issue with the previous version.

Any ideas as to why this keeps happening?

[pgriffith 88]

I have the new 2.x app installed on 4 different machines. They all initially started in a window, after going Fullscreen they all now start in Fullscreen every time I start them.

[QuarkZ 14]

I don't want them to start fullscreen though, I want them to maximize, which they don't. Fullscreen already worked before, but maximize never did. Anyway, I found a workaround, which is to use autohotkey. It's just bizarre that after all this time, this app can't do something as simple as this.

[softworkz 5066]

2 hours ago, QuarkZ said:

I don't want them to start fullscreen though, I want them to maximize, which they don't. Fullscreen already worked before, but maximize never did. Anyway, I found a workaround, which is to use autohotkey. It's just bizarre that after all this time, this app can't do something as simple as this.

In case of the new app it was simply an oversight. It's fixed now, but it will cycle through the beta first.

Thanks for reporting!

[QuarkZ 14]

Good to know it was just an oversight, the new app sure fixed most grievances I had with the old one, so it's great to know the last bit will be taken care of too, thanks!

[softworkz 5066]

Can you please try 2.207?

Thanks

[QuarkZ 14]

4 hours ago, softworkz said:

Can you please try 2.207?

Thanks

Works perfectly now, thanks!

[softworkz 5066]

Thanks for confirming!

Edited December 24, 2024 by softworkz

[QuarkZ 14]

So there's actually still a bit of an issue with this, which is that after exiting full screen, the window once again loses the maximize status.

[softworkz 5066]

This is intended to avoid confusion between maximized and full-screen.

[QuarkZ 14]

This doesn't make much sense, you can literally see the title bar and task bar when not in full screen, if one is confused about the two they can avoid using maximize, you shouldn't override the user's choice.

[softworkz 5066]

20 hours ago, QuarkZ said:

This doesn't make much sense, you can literally see the title bar and task bar when not in full screen, if one is confused about the two they can avoid using maximize, you shouldn't override the user's choice.

The app internally stores window states as a single value (full-screen, maximized, minimized, windowed). When it goes full-screen, it doesn't "remember" the state it had before, that's why exiting full-screen always leads to "windowed" state.

I'm afraid but this cannot be easily changed right now.

[QuarkZ 14]

Frankly, this is just bizarre... Jellyfin player does it, MPC does it, VLC does it, but Emby somehow can't remember its previous state after going fullscreen?

Anyway, since apparently it's not easy to store a "last state" variable, I guess this won't happen anytime soon, especially if it's "Intended behavior", I created an Autohotkey script to override this behavior, if other users want it, they can feel free to contact me.

 

 

[softworkz 5066]

7 minutes ago, QuarkZ said:

Frankly, this is just bizarre... Jellyfin player does it, MPC does it, VLC does it, but Emby somehow can't remember its previous state after going fullscreen?

Anyway, since apparently it's not easy to store a "last state" variable, I guess this won't happen anytime soon, especially if it's "Intended behavior", I created an Autohotkey script to override this behavior, if other users want it, they can feel free to contact me.

Please take my apologies for the confusion. I was under the wrong assumption that you would have some basic understanding of how professional software development works. What I meant by "it cannot be changed right now" is the simple fact that after a feature has been developed, undergone several months of beta testing and finally been relased just days ago, you do not make fundamental changes to program logic based on the disliking of a single user and which would involve a more than minor risk of regression.

Of course it would have been totally easy to do if we would be in an early beta phase, that goes without saying. The original intention though, had been to completely eliminate the "maximized" state and have a full-screen state only instead of maximized - in the same way like Windows Media Center behaves. 
This idea had been dropped and we kept separate states for maximized and full-screeen. From 80 people in the beta, nobody has brought up this subject within 3 months and that's how it came to be like it is.

A change would be easy if there weren't thousands (add zeroes to your liking) of users who are relying on us providing a solid and stable client software which doesn't introduce new bugs and regressions with every new release. There is a difference between personal/hobbyist and professional application development and for those who are not familiar with the peculiar nuances, it's easy to deem professionalism as incompetence.