was: current work - code integrity - up to v1.6
was: current work - code integrity - up to v1.6
I'll be working on the code integrity. It may result in several releases and I may also change the search server protocol. The purpose is to finish the work in the shortest possible time.
next i think there will be a technical upgrade, i adopted a later version of GUI library, basically all the same just some glitches are fixed there (but some bugs which i fixed myself weren't fixed so i had to fix them again, i keep record for such a case). i'll release it probably tomorrow as a small release so if i forgot something users will remind me.
after two glitches (no button here or unexpected icon there) the gui library after upgrading seems to work ok, no sign of resource leaks or crashes. there is more potential, the tabs in the workspace and task manager are independent code, but because all is running so stable i may change it later using uniform approach. i just need to check one more topic first.
i released the version with the new browse dialog (the other two are also an option) as v1.3.7
it took half a day since i had to compare two sources (one derivative) and also had to fix several bugs (like both showed "zip" files since such files have folder flag in winxp).
the same source is used in winrar since remaining drawbacks are the same (like when deleting folders it is not reflected in the view), i could fix is since there is source, just given the purpose - to create a single directory - it is not critical, exactly like in winrar case.
it took half a day since i had to compare two sources (one derivative) and also had to fix several bugs (like both showed "zip" files since such files have folder flag in winxp).
the same source is used in winrar since remaining drawbacks are the same (like when deleting folders it is not reflected in the view), i could fix is since there is source, just given the purpose - to create a single directory - it is not critical, exactly like in winrar case.
i've fixed a bug, there was a single indicative spam message reposted in a single newsgroup for over 30 days (spam bot) which caused a variable overflow only today.
also i found a bug in the new browse for folder dialog (third party code), they didn't check return result of a shell function properly.
it is released as v1.3.8
also i found a bug in the new browse for folder dialog (third party code), they didn't check return result of a shell function properly.
it is released as v1.3.8
v1.3.9 runs ok.
the only reservation is the new "explorer" browse for folder dialog, i need to revise all the code and compare it to windows sources. in part in addition to not parsing the network paths (which we just ignore) i have a report it doesn't fill the folder tree in win2k, so it is system version dependent which is bad.
if it will be too messy i may omit the dialog from the next release and leave only the standard and custom dialogs. from other side i would like to keep it too, but in short i'll check the issue first and decide towards the end of the week.
the only reservation is the new "explorer" browse for folder dialog, i need to revise all the code and compare it to windows sources. in part in addition to not parsing the network paths (which we just ignore) i have a report it doesn't fill the folder tree in win2k, so it is system version dependent which is bad.
if it will be too messy i may omit the dialog from the next release and leave only the standard and custom dialogs. from other side i would like to keep it too, but in short i'll check the issue first and decide towards the end of the week.
in the end i've further developed my own simple hack of the standard dialog and it works much better than the cumbersome third party code which was reported to have even more problems (but it is not them to blame but the microsoft poor documentation and negligence).
also i see all is running clean, so this chapter is closed.
releases will be now back to normal schedule.
also i see all is running clean, so this chapter is closed.
releases will be now back to normal schedule.
one more bug related to collections fixed after i got more data (thanks to the user who helped me).
we are talking now about very small probabilities around 0.2% (like 2 crashes per 1000 sessions), clearly in practical terms it is not significant.
just if i can make code cleaner i go for it right away.
with newspro such reliability has never been achieved (and newspro is very reliable program) since it was based on microsoft foundation classes.
i've used the opportunity to set better default options (see release notes) and refer new users to getting started in the initial browse for folder dialog - v1.4.1
we are talking now about very small probabilities around 0.2% (like 2 crashes per 1000 sessions), clearly in practical terms it is not significant.
just if i can make code cleaner i go for it right away.
with newspro such reliability has never been achieved (and newspro is very reliable program) since it was based on microsoft foundation classes.
i've used the opportunity to set better default options (see release notes) and refer new users to getting started in the initial browse for folder dialog - v1.4.1
in v1.4 with fix of keeping maximized state i removed a little more code than it was needed and it stopped remembering the offset of quickfilter and search service bars from the left. it is the same case with the latest version. i've fixed it here.
also in time left (forum post) when some entries are paused it also wrongly took into account paused articles so the time was exaggerated it is also fixed here. i've also added the time to the system tray tooltip.
otherwise no problems.
also in time left (forum post) when some entries are paused it also wrongly took into account paused articles so the time was exaggerated it is also fixed here. i've also added the time to the system tray tooltip.
otherwise no problems.