Am 29.12.2010, 21:04 Uhr, schrieb Peter Persson <pep.fishmoose@gmail.com>:
1. N.AES does not rule (for me)We need some point of reference here. The reason I compare with N.AES and 0.998 is because they're the closest comparison we have for a modern AES - not counting MyAES because I can't get it to work on my machine (probably an error on my behalf, however). Toolbars are working in N.AES, and has been working for quite a while. So in that sense, N.AES rules. Apart from that, I generally prefer XaAES.
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.
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.
and I'm trying to contribute to make that happen. I do that by testing the toolbar functionality, providing code to reproduce problems, and
Good.
providing screenshots. That's the only way I can contribute at the moment, and I'm under the impression that testing the toolbar implementation is a good way of finding problems in the implementation.
Sure!
This means it's not a minor cosmetic flaw, and it causes artifacts on screen. It's not a matter of personal taste, it's a redraw error.
Of course, but it does not handycap any program (existent or not) from working.
I'm using toolbars in an upcoming project, and I think it's a great opportunity to test this stuff properly. And so far I've found several bugs, and we've had a good cooperation when solving them. I believe my latest finding was introduced with the changes in the toolbar visuals,
I'm pretty sure there are still lots of minor and major bugs in the toolbar-implementation, just because there is not much to test.
of nature - no code on the planet is free of bugs. The reason I requested this particular code to be rolled back (note that I say rolled back - not ditched) was because I wanted a fully working toolbar implementation in 1-17. If it's not rolled back, or if this bug is not
It is easier for me to fix step-by-step than to roll back and forth (and you don't know what exactly to revert).
fixed (if it is a bug), then that will not be the case, and I think that would be unfortunate. When working, the code could be re-introduced
The upcoming release will not get burned into ROM, why not release 1.17.1 in Feb? When is your app ready?
again (because it does look better than the old code once it's fully working). I was under the impression that CVS could make this possible in some neat way, but maybe I was wrong.
It would be complicated for me (and useless).
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.
There is a small transparent bar left beneath the toolbar that only shows up sometimes, but this was always there, will be fixed too (hopefully).
-- PePNote: The extra arrow sprites on the screenshots seems to be an Aranym+fVDI problem. Please ignore them (it doesn't happen on my real machines). Another note - the Alert icons looks very weird on my 0.999 build compared to 0.998 (this is also evident on the screenshots).
Yes, they look odd, don't know how you did that. -- Helmut Karlowski
Attachment:
4d1bb015.gif
Description: GIF image
Attachment:
4d1bb9bb.gif
Description: GIF image
