Leaderboard

Any developer or organisation that cares about quality should be flexible enough to accept bug reports from a variety of channels. Clearly if the reporter can enter a high quality report in the project bug tracker, then that is the ideal. But in reality that is not always possible. Sometimes these reports are unclear and imprecise and the project owner has to edit the report. And sometimes the reporter just won't take the required steps. Sometimes the reporter is stubborn and for inexplicable reasons refuses to give their email address and a password to sourceforge 😉 But what developer would here of a bug in their software and not want to fix it? Any developer that is prepared to let bugs pass if they aren't in the tracker should just give up. Incidentally, it grinds my gears that Emba killed QC without transferring open reports to the replacement. On numerous occasions I have been asked by Emba staff to resubmit to QP the litany of open floating point related bugs that I submitted to QC. It makes no sense to me at all that any developers that care about quality would do that.

@Larry Hengen How many open source projects do you maintain? So speak for yourself - I have received enough issue reports over the years not via bitbucket but on forums, via email or someone told me personally that I then either entered myself or just fixed (yes I need to make a habit of first reporting and then fixing so its documented outside of just a commit that says fixed xyz). It does not matter where but how and what. A poor report with zero info on bitbucket is as time consuming as a bad one elsewhere.

Just uploaded a new version. Now it supports "introduce variable" refactoring, parameter to field binding and other features. Change log with animation: http://siberika.com/whatsnew.htm

I-Pascal v2.0 has been released. What is I-Pascal? It's a Pascal language support plugin for IntelliJ IDEA. Integration with Delphi and Free Pascal Compiler. The main goal of the project is to provide modern code editing and inspection tool for Pascal language. Dependency cycles ready. In the new release: Completion options from not used yet units (with automatic modification of uses clause) Completion itself is improved and not is comparable to one for Java Delphi 10.3 inline declarations syntax support. Highlighting, find usage, renaming etc. No inherited destructor call inspection Project site: http://siberika.com/ Installation instructions: http://siberika.com/install.htm Source code: https://github.com/casteng/i-pascal

If you care about quality it does not really matter where the bug was reported. What matters is that people who need to know are aware of the bug.

String is not an automation compatible data type. The IRecognitionResult.Get_text() method and IRecognition.recognition_text property need to be declared to use WideString instead of String. IRecognitionResult = interface(IDispatch) function Get_text: WideString; safecall; property recognition_text: WideString read Get_text; end;

Why are you not using ApplyUpdates to delete the marked records from the database?

I know there is a way to mark an entire forum as read, but is there a way to mark a single thread in a forum as read too? Marking an entire forum as read is a little drastic, IMO, but marking a thread (i.e. all messages currently in that thread) as read would make a lot of sense, IMO.

I always thought that happens as soon as you are in the thread (not necessarily reading it). But I guess you want to mark it read without entering it, correct?