Re: [MiNT] MiNT1.17 Changes

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

29 dec 2010 kl. 22.53 skrev Helmut Karlowski:

> Of course things have to work in XaAES perfectly. I meant we do not have to strictly imitate the behavior of any other OS.
> 
> The new layout of toolbars is correct and modern and has nothing to do with your issue.

That's not what I meant. I meant that it made sense in this case to compare the behavior with an environment where toolbars are known to work properly.


>> All I want is for XaAES to have a fully working toolbar implementation,
> 
> Me too. I did a lot of fixes in toolbars (for no particular reason in the end), the changed slider is only a small part of this. There was once someone called zorro who complained non-correct toolbars. I thought ok when we get a killer-app, I'll try, but never heard again of it. Until today there is not a single app knwon to me that uses AES-toolbars (except the atari-demo), so I don't understand why get nervous.

I'm not nervous :) I'm just frustrated, because I spend weeks trying to find what I'm doing wrong in my code, just to find out that it's a problem with the AES. And I've encountered a lot of them lately.


> The upcoming release will not get burned into ROM, why not release 1.17.1 in Feb? When is your app ready?

Some time before that, hopefully.


>> My 0.999 is from Dec 18 2010.
>> My 0.998 is from May 6 2007.
>> Lonny tested it successfully on the most recent version of N.AES and Odds last unofficial build (0.998 alpha, from Apr 15 2006).
>> 
>> I'm using Aranym right now.
> 
> Please download the latest build and try again. I cannot see the error (see screenshot). I changed some things on 12/19.

This looks much better! It's evident now that we've discussed apples and oranges.

Too bad I didn't know about this build earlier; in such case I could have saved 3 days of my life ironing out how to trigger this particular bug, and we wouldn't have thrown poisoned darts at each other for the past few days!


> Yes, they look odd, don't know how you did that.

It was like that by default with the build from Dec 18 - hence my frustration.

-- PeP