On 12.02.2019 18:29 'Fabien Costantini' via fltk.coredev wrote:
> Hi Albrecht,
> In my view, it depends how we interpret the version, it seems that this
> is an old problem that (according to greg latest feedback on this STR)
> is still present in 1.4.
Greg's tests are very much appreciated. So I discovered a very old bug
report of a bug that still exists. Good to know.
> I interpret the version as 'the bug appears since version 1.1' which is
> more helpful than it happens in latest 1.4 branch.
Yep, that's my opinion as well, and that's the reason why I didn't
change the software version and left it at 1.1.
> So my vote would be to keep it that way with a version of 1.1 if I
> interpret correctly that the bug was first detected on 1.1 and still occurs.
> We should probably display a message somewhere (maybe a status bar
> inside of the file content view shomehow confusing) ?
I don't understand what exactly you mean. Please elaborate. If it's a
suggestion how to fix the bug we may discuss it here, but please add it
to the STR as well.
WRT your other message "about 'clean' consideration": I don't intend to
"clean" anything in the sense that I would delete STR's or something
like that. But I'd like to have a clean roadmap for old versions like
1.1, hence we (who ever does this) should try to fix these old bugs first.
Note that I found many more unclassified bug reports and I'm still
working on it. See fltk.bugs from about 17:30 CET to now (19:20 CET),
currently 13 STR's or something like that. I classified bugs correctly
(AFAICT), closed duplicates, and added comments to some more bug reports.