Abit AT7 Max
Athlon XP 2000+
Windows XP SP2
ATI Radeon 8500 64MB
CATALYST 3.7
Appears that red and blue channels are swapped on pngs.
(See attached)
Abit AT7 Max
Athlon XP 2000+
Windows XP SP2
ATI Radeon 8500 64MB
CATALYST 3.7
Appears that red and blue channels are swapped on pngs.
(See attached)
It's inverted colors. I hate this <_< . Me too
switch to ObjectDock or YzDock
hi,
did you try the updated version 0.77a available from the mobydock-website ? we had a similar problem with some ati-card and this fixed it for the users that had problems with inverted colors before.
if this is not the case and 0.77a does not help you, feel free to contact me directly and we will find a solution.
well and a new version of mobydock dx is just around the corner !!
Stay tuned,
Moby
Same problem here...
Asus MB
K7 700
WinXP SP1
DirectX 9.0b
Radeon 9200 128MB
Latest Catalyst Drivers (04/09/2003)
Hope to see that new version soon 
(Y) Aaaaah, music to my ears Mobey ![]()
With 77a it has bug fix the problem.
With 77a it has bug fix the problem for me
Besides the original bug that I reported above with 0.77a, MobyDock.exe has a decent size memory leak and was using 340MB of memory when I woke up this morning.
As a side note I don't really appreciate the trolls that replied "oh just use YzDock dock!" Why the would I use a program where development was terminated (allegedly because of Apple...) and the source code never released? I feel sorry for users of YzDock but the truth is that a binary floating around with no source is an evolutionary dead end.
How to keep software in the gene pool:
1) Write code that compiles with a free toolchain like gcc and mingw headers.
2) Release the code under GPL or other free license.
Bonus Points:
1) Write code that is easy ported to other platforms.
Originally posted by Cableless@Sep 24 2003, 02:00 PMAs a side note I don't really appreciate the trolls that replied "oh just use YzDock dock!" Why the would I use a program where development was terminated (allegedly because of Apple...) and the source code never released? I feel sorry for users of YzDock but the truth is that a binary floating around with no source is an evolutionary dead end.
Because Y'zDock is better than other docks? now Y'zDock is the more complete and solid than the other docks. I say when other dock would be better than Y'zDock I will be the first to change to it. Before not.
just invert the icons 
The memory leak is due to icon browsing. That is, when someone goes to change an icon mobydock reserves memory which never releases. More icons you browsing more memory gets reserved.
I personaly quit and re-run mobydock after icon changing. Then i use mobydock for days(uptime) without memory loss.
ps: Any estimation for the new release? (i am not pushing, i am not pushing)
hi,
1. release estimation : some days
2. memory consumption : the problem is not that mobydock does not release memory. the reason is how windows handles/frees memory. anyway, it is fixed with the new release.
Moby
Shouldn't this stuff be better discussed in the STICKY thread devoted to bugs?