https://bugs.kde.org/show_bug.cgi?id=401103
--- Comment #31 from Ismael Asensio <isma...@gmail.com> --- Thanks a lot for summarizing up! > Should I open another bug report, that matches the current behavior more > closely? I still think there are some problems remaining here. Yes, I think there's more chances to get the remaining issues solved by filling two focused bug reports, especially if one of them only affects okular. > a) okular always starts in maximized state even if it was closed in > unmaximized state. Thus, it remembered the maximization in the first place, > but not the demaximization ... I cannot reproduce this, so there must be some other differences in our setups (multi-screen?) and/or okular internals. Filling a bug against it can help figuring out the problem. > b) "Ignore requested geometry" does not help. See screenshot of okular > settings (I have already forced it). Does this ignore setting include the > maximized state? I still think, that apply initially rules should always > work with this setting forced. At least the description of the feature > should be a little bit more clear about the affected rules (size, position, > maximized?). Currently the description only mentions position, but I think > it will at least affect size, too. This is a very good point. I would also assume that the geometry also affects maximize state, but it in fact doesn't. It is worth looking for a possible solution, or at least disambiguate it as you propose. -- You are receiving this mail because: You are watching all bug changes.
