Lagi Pittas wrote:On a sidenote I went to the quality site to suggest it as a bug in as a bug and there are hundreds (nay thousands) of bugs going back to years marked as unconfirmed and pending - if they have been fixed shouldn't they be marked as such?
With so many changes over the years some reports have been obsolete for reasons ranging from deprecated OS features to simply having been fixed while addressing other reports.
To trim the noise in the bug DB, last year the LiveCode product manager sent emails to all bug reporters without outstanding reports which included links to each report not yet closed, along with instructions to please verify that the issue remains in the current version and to please note if it does.
It seems only a handful of us who got the email responded with those confirmations.
I've discussed this with the team, and at some point we'll split up the DB into sections and have a team of people go through it to update current status and close older noise reports. But with priorities right now very much focused on delivering a great v8.0, this side project may have to wait a few more weeks.
In the meantime, if you come across any reports there that are either no longer relevant in the current version, or indeed very relevant in which the recipe exhibits the same behavior in the current build as in the reported build, please feel free to add a note to the report. Feedback like that will be very helpful with the future review effort.
