https://bugs.kde.org/show_bug.cgi?id=424434
--- Comment #4 from [email protected] --- > I'm relunctant to make a change that would flood all clients with pointless > configure events "Pointless" according to what criterion? I'm not sure we really need "events", though. In the case I'm considering, the application is not listening for an event (at least from the point of view of the JavaScript code), it's actively querying for a given property when it needs it, and you are returning an obsolete value. Now I don't know if the only way for the application to know its configuration is to listen for events and store the values when they change. IF that is the case and it impacts efficiency (that is, IF an application has no way of querying for a given window parameter at a given time without "subscribing" for being notified of events, AND being flooded by those events without doing anything more than storing the values it needs to read later is costly), then it means the overall architecture is poorly designed. > without hearing a better use-case than "browser pong" What criteria does a use case need to meet to be good enough for you? Does it need to be "useful"? Where do you draw the line between useful and not useful? Does it need to save lives? (note that I didn't create "browser pong", I just spent a couple of minutes to look for a random use case because you asked) What even is a use case? What if the use case is something genius that neither you nor I have even thought about yet? You shouldn't ask for a use case for a feature. The mere thought of a feature should be enough to require its existance. To me, when I can describe a feature with words, that automatically translate to a use case: "Someone might want to do that", that's it. And if the feature has existed for the last 20 or 30 years in every major OS, then before you take it away, you need to be able to prove that a use case can't possibly exist (which is usually impossible, that's why you usually just don't remove a feature that has existed for ages). Unless of course you gain something huge by removing it, but that's obviously not the case here. That "flooding" that you are afraid of is already happening in all the other major desktop environments, and I don't see them become slow or unresponsive when I move windows around. If KDE did, then probably that would mean there's an issue elsewhere that needs addressing. > Upcoming replacement for X. > No windows will know their own position Wow. Looks to me like someone had a really, really stupid idea there. -- You are receiving this mail because: You are watching all bug changes.
