Gerhard,
I assume you think I generate junk code and throw it at unsuspecting end users. I can assure you that I do extensive testing before releasing a beta version, however, with complex plugins the way that users interact with it can show up issues, i.e. building boundaries clockwise when I do it anti-clockwise (I now test for both directions). Also, different versions of OCPN can cause issues, i.e. OCPN 4.4.0 works OK, OCPN 4.5.0 does not (but it is a beta). Also, using plugins on newer versions can identify new issues, i.e. using OCPN 4.5.0 when the
plugin was developed against OCPN 4.2.0. Fixes are released as soon as possible after the issue is identified.
I want to hear about problems, I just don't like being told I deliver poor quality, buggy, untested plugins or updates. Building some of these plugins is complex and it takes many different users on different platforms with different outlooks and different languages to identify the problems. I did provide a fix for the log issue within a day back in July, however, it has not made it through to the version available for download. My systems are not really good enough to generate the 'release' versions as you need 'old' versions of wxWidgets, etc. So there are special 'build' areas run by others that do this.
I am not the owner of Watchdog, but I do contribute to it to allow my
plugin to be used for alarms, which was a user request. I do fix issues if I can in the watchdog plugin, but windows 10 is a 'special' version of windows and runs REALLY slowly for me and seems to update itself all the time causing issues for other plugins, such as the s63 plugin, as the 'hardware' appears to change with each update.
Please be constructive in your comments and help by testing, writing
documentation, building plugins on other platforms, i.e OS/X, or contribute code to help improve the quality or capability of OCPN.
Thanks
Jon
Quote:
Originally Posted by CarCode
You really should check your code first and test it yourself before any publication. When things happens to the users like this there is for sure something wrong even if you don't want to hear that. You should see for yourself e.g. when a logfile is flooded with warnings even when they are harmless. Same thing with window coordinates out of a visible screen. It should not be allowed to store such wrong coordinates. Check your code.
Gerhard
|