Home away from home 
Joined: 2007/9/11 11:31 Last Login
: Today 16:00
From Russia
Group:
Registered Users
|
@Elwood
No, it's not just you—most of us have this issue. It was reported several times and rejected. Initially, it started after a commit a few years ago, and I reported it immediately. However, it was incredibly difficult to explain repeatedly what was happening and where the bug was—even when I provided video evidence and explained it in various ways with different approaches. Yet, each time, it was dismissed as if nothing was wrong. Then others reported it, and I brought it up again. Nothing changed. More recently, some people on os4depot reported it, and I highlighted it once more—still no response.
Every report about this issue is treated as if we (or I) are attacking without reason, when it's simply a legitimate bug report that, for some unknown, irrational, and illogical reason, keeps being ignored.
I pointed to LiveForIt exactly which commits introduced the issue (I don’t remember the commit number now, but it’s in the old thread about uae-improvements on amigans). The proper approach would be to understand what was changed, create a test case, test it on different machines, and then implement the fix correctly. But that requires a willingness to acknowledge the issue and trace the root cause in the code that broke things.
In other words, don’t get your hopes up. I’m only writing about it again—and again—holding onto a faint hope that LiveForIt will finally accept that there’s a problem, instead of simply saying, “It works on my X1000,” and actually try to create a small test case or investigate where the issue lies.
Because if this is being done for users, shouldn’t bug reports be accepted? If it’s only for personal enjoyment, then why make it public and avoid reports?
|