Re: [MiNT] MiNT1.17 Changes

[Peter Persson <pep.fishmoose@gmail.com>]

Could you please add the changes made to the toolbar resource handling to that list?

Helmut: I don't have proper access to our recent correspondance since I'm away for the Christmas holidays, but again I urge you to roll back the cosmetic changes made to the toolbar. Again, in practice, I suspect that I've tested it more than anyone else recently, and my conclusion is that the changes are not yet stable. The changes are good once they work properly, and they make good candidates for future releases, but releasing them at this stage would be bad imo. The work you've put into it is not lost and can be used later on. The toolbar implementation has already suffered from numerous bugs, and bug fixing should have a higher priority than cosmetic changes imo.

Again, the changes look nice, but they have introduced a random 1-pixel displacement of custom objects, and the behavior nolonger matches that of naes nor 0.998. I have tested this empirically, and produced screenshots of the problem. I've helped out by writing test code for other bugs in the toolbar implementation, to make it easy to reproduce them. I've also come up with workarounds for previous versions. I'm not just complaining, so please take this seriously. The toolbar was a killer feature in 1992, and it needs to be working by now. Untested cosmetic changes can't be allowed to break the toolbar in yet another version. Please.

Skickat från min iPhone

28 dec 2010 kl. 00:19 skrev Alan Hourihane <alanh@fairlite.co.uk>:

> Thanks Ole.
> 
> I'll add this to the README.
> 
> Looks like Wednesday it's release time.
> 
> Alan.
> 
> On Thu, 2010-12-23 at 14:10 +0100, m0n0 wrote:
>> Hello there,
>> this is the stuff that I could extract from the changelog. Doesn't sound
>> like that much to the user,
>> but I think every user shouldupdate, because this is the most stable
>> release of XaAES and FreeMiNT ! :)
>> 
>> Additions, anyone ? The Changelog () is a bit old (4 month) is this
>> intentionally? Shouldn't the bugfixes ot the last 4 month be within the
>> log? I remember there where several issues ( like shutdown... ).
>> 
>> XAAES Changes:
>> --------------
>> 
>> - Improved Task manager
>> - Single Tasking mode
>> - File Selector: case sensitive pattern matching,
>>  when | is the first character of the pattern
>> - Improved documentation
>> - Support for "extended textured" (?)
>> - Improved compatibility with EmuTos
>> - Manages a list of processes which shouldn't be killed shutdown
>> (CTLALTA_SURVIVORS)
>> - Implemented WF_FIRSTAREAXYWH ( whatever that is... )
>> 
>> 
>> XAAES Bugfixes:
>> ---------------
>> - Fixed many redraw issues ( like drawing of transparent RSC Elements )
>> - Several bugfixes for Resource File loading
>> - Various other Bugfixes of "small bugs" ( not so interesting for users )
>> 
>> 
>> Kernel Changes:
>> ---------------
>> 
>> - FAT fs: Renaming of files in-use is allowed
>> - Single Tasking mode
>> 
>> 
>> Kernel Bugfixes:
>> ----------------
>> 
>> - fixed load of keyboard tables when memory protection is turned on
>> - Shutdown procedure fixed
>> - TCP connect sequence fixed
>> - Various other Bugfixes of "small bugs" ( not so interesting for users )
>> 
>> Greets,
>> m
>> 
>> 
> 
> 
> 
>