19 June 2020, 18:24 | #3461 |
Registered Voter
Join Date: Oct 2019
Location: Neunkirchen aP, DE
Age: 62
Posts: 570
|
|
19 June 2020, 18:34 | #3462 |
Registered Voter
Join Date: Oct 2019
Location: Neunkirchen aP, DE
Age: 62
Posts: 570
|
It's pretty wild how AfA's .exe libs affect libs and datatypes version numbers. My picture.datatype which showed 49.6 is now showing 45.17. Too freaking cool...
|
19 June 2020, 18:38 | #3463 |
Registered User
Join Date: Apr 2005
Location: digital hell, Germany, after 1984, but worse
Posts: 3,366
|
HaHa, you didn't look at the LibID string of icon.library in Scout's library list yet ...
|
19 June 2020, 18:44 | #3464 | |
Registered User
Join Date: Aug 2014
Location: Brindisi (Italy)
Age: 70
Posts: 8,252
|
Quote:
These Kodak Photo CDs on Amiga could be seen only with AimCDFS or other equivalent Device CDs, with WinUAE CD Automount you can't see the photos of these CDs, I attach screeshot (used AimCDFS) Last edited by AMIGASYSTEM; 21 June 2020 at 11:46. |
|
19 June 2020, 18:46 | #3465 |
Registered Voter
Join Date: Oct 2019
Location: Neunkirchen aP, DE
Age: 62
Posts: 570
|
I didn't even think of looking there - rather, I looked in Sys Info. I'm not a coder but just a user. I mean nothing by that, it's just my head usually doesn't think in those terms or at least, not at first. Configuration - certainly, it's how my Amiga setup got to be fast, functional, and good looking but I'd be lying if I said I understood how it all worked. Sometimes in my case, it's by brute force.
|
19 June 2020, 18:53 | #3466 |
Registered User
Join Date: Aug 2014
Location: Brindisi (Italy)
Age: 70
Posts: 8,252
|
Yes I looked, but there's your icon.library, otherwise Dopus4 wouldn't have worked.
Last edited by AMIGASYSTEM; 24 July 2020 at 13:09. |
30 June 2020, 17:22 | #3467 |
Registered User
Join Date: Dec 2014
Location: Gothenburg, Sweden
Posts: 114
|
@Peter I think there's still one issue, not sure if you've noticed or not:
When using IconLib TC020 51.4.535, together with DoNoColorMapping and HoldTCBuffer1, and the patched DOpus 5.83 binary that you provided, desktop icons (only!) seem to have a more "trimmed" mask than the previous version. Icons inside windows/listers look normal. Reverting back to IconLib v51.4.533 and changing nothing else, fixes this. I'm attaching a screenshot to demonstrate... |
30 June 2020, 18:31 | #3468 |
Registered User
Join Date: Apr 2005
Location: digital hell, Germany, after 1984, but worse
Posts: 3,366
|
Thanks for reporting this disfigurement, midwan !
Usually, I don't care much about these beauty issues. I think it's caused by one of DOpus5 woes, because it uses dozens of separate tasks for different purposes, and it can be a pain to filter them out. The icons in a window are loaded by dopus_function and dragged by dopus_lister for example, but the icons on the desktop are loaded by the main process with a name which depends on the program name and can be something like DOpus5, DirOpus, DirectoryOpus or DO whatever you want. But, of course, there are more other task names as dopus_disk(copy) or dopus_info etc, I don't remember all of them. Ok, I will consider the main process name for using the TCbuffer, too. And then you may come and say: "The icons are still not looking perfect inside of my trashcan or on my Ram Disk" ... or wherever DOpus5 uses another task. |
30 June 2020, 18:51 | #3469 |
Registered User
Join Date: Dec 2014
Location: Gothenburg, Sweden
Posts: 114
|
Thanks for considering it.
Just a small, related note: - If you disable DoNoColorMapping and reboot, the problem also goes away. But I guess you know that, since you understand more about how this works internally |
30 June 2020, 21:22 | #3470 |
Registered User
Join Date: Apr 2005
Location: digital hell, Germany, after 1984, but worse
Posts: 3,366
|
Update to icon.library 46.4.536 (Aros, TC020, LD020, FastWB and Dopus 5.83 only):
TCbuffer1 was not enabled for icons directly on the DOpus5 desktop, and thus their soft borders were cut off by the image masking when DOnoColorMapping was activated, which is required for the fast custom dragging routines. - No changes in DOpus 5.83. http://aminet.net/package/util/libs/IconLib_46.4 Last edited by PeterK; 02 July 2020 at 11:24. |
30 June 2020, 23:01 | #3471 |
Registered User
Join Date: Dec 2014
Location: Gothenburg, Sweden
Posts: 114
|
That was fast!
Confirmed to work as expected now, thanks! |
13 July 2020, 19:32 | #3472 |
Registered User
Join Date: Apr 2005
Location: digital hell, Germany, after 1984, but worse
Posts: 3,366
|
Update to icon.library 46.4.537:
This is a fix for a small gentle bug that was hiding in IconControlA(SetWidth/SetHeight) since build 484. It did probably never cause any harm yet by using the non-preserved scratch register D1 with a structure offset of zero for Width, because by coincidence AllocMem() uses D1=0 for clearing the structure too, and thus has always fixed this bug. But some "evil" debugging tools didn't like this trick. These functions were called by Eastern, for example. Unfortunately, Eastern still doesn't work on Aros after fixing this bug, so don't install it there! |
14 July 2020, 15:45 | #3473 |
Registered User
Join Date: Mar 2010
Location: Beckenham/England
Posts: 796
|
With this update Memicon no longer works with the helvetica font at size 13, it complains about invalid icon size. Setting it to 12 works, but it is a bit tiny.
http://aminet.net/package/util/wb/Memicon Just tried size 15 and it works. Last edited by James; 14 July 2020 at 15:47. Reason: more added |
14 July 2020, 18:02 | #3474 |
Registered User
Join Date: Apr 2005
Location: digital hell, Germany, after 1984, but worse
Posts: 3,366
|
Hi James,
my tests with Helvetica 13 and all other sizes didn't cause any errors here. Try FixFonts or send me your other MemIcon tooltype settings. But, if MemIcon creates an icon which is larger than 256x256 or just wider than 256 pixels that's not supported by (any) icon.library. It would be allowed to use a longer icon label, but when I select the MemIcon for dragging it seems that the icon images are also too wide (not sure about that). Is your issue reproducible and does it always vanish with the previous versions? I tried Helvetica 13 with 537_TC020 and some debugging tools running, but it works. |
15 July 2020, 01:36 | #3475 | |
Registered User
Join Date: Mar 2010
Location: Beckenham/England
Posts: 796
|
Quote:
When I updated the icon.library (TC020) and rebooted it failed immediately. I changed the font size and it worked, tried to change it back and it failed again. Tried this several times and it always failed with size 13. Switched to verdananabold 16 and it worked, so I left it at that. Now, testing it again, it has worked with every font and size I have tried so far. |
|
15 July 2020, 17:33 | #3476 |
Registered User
Join Date: Apr 2005
Location: digital hell, Germany, after 1984, but worse
Posts: 3,366
|
After doing some more investigations I can say that nothing is calling the functions which I changed in 537, neither MemIcon, nor Workbench by order. So, the Helvetica 13 font problem can not depend on my latest update, but maybe on some racing conditions with LoadWB and WBstartup tools.
MemIcon just uses GetDiskObject(), DupDiskObject() and FreeDiskObject() from icon.library before it calls the Workbench functions AddAppIcon() and WorkbenchControlA(), which consequently uses GetIconRectangle() and IconControlA(), but nothing like SetWidth or SetHeight. I couldn't find any explicit comments about limitations for width and height of AppIcons handled by workbench.library except for the restriction to word size in the diskobject and gadget structures. In the autodocs these images are called "hit box" and it seems that more than 256 pixels for w an h are allowed in contrast to other icons. |
20 July 2020, 15:29 | #3477 |
Bit Copying Bard
Join Date: Jan 2017
Location: Kelty, Fife, Scotland
Age: 41
Posts: 1,293
|
Hi Peter, just wondering if the latest 537 be 51.4.537 as opposed to 46.4.537.
Doesn't seem to have any adverse affect in use, but wondered why it had changed |
20 July 2020, 16:54 | #3478 |
Registered User
Join Date: Apr 2005
Location: digital hell, Germany, after 1984, but worse
Posts: 3,366
|
Sorry, but after checking all versions in the latest 537 package I can't see any changes.
In general, my icon.library has the version 46.4.xxx, with the build number as index. But since build number 510 or so I have added support for Eastern to send TrueColor images to my icon.library, and Eastern only does this if the icon.library version is at least 51 and can handle that with IconControlA(SetImageData). My 51.4 versions are able to do just that additional task, but they don't support any other features of an OS4 icon.library. Therefore the TC020, FastWB, HAM8 and HAM6 versions are v51.4 now and can display the preview thumbnail images of Eastern in TrueColor or HAM, whereas all other 46.4 versions would only display dithered Eastern images with maximal 256 colors. |
20 July 2020, 17:00 | #3479 | |
Bit Copying Bard
Join Date: Jan 2017
Location: Kelty, Fife, Scotland
Age: 41
Posts: 1,293
|
Quote:
|
|
22 July 2020, 00:31 | #3480 | |
Registered User
Join Date: Mar 2010
Location: Beckenham/England
Posts: 796
|
Quote:
http://amigazeux.net/dragon/ |
|
Currently Active Users Viewing This Thread: 2 (0 members and 2 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
ClassicWB Full and icon.library 46.4 | Retroplay | project.ClassicWB | 8 | 05 August 2018 13:57 |
WB library conflict/versions | Amiga1992 | support.Apps | 3 | 22 July 2010 18:47 |
PNG Icon to Color Icon Converter? | Leandro Jardim | request.Apps | 1 | 24 May 2010 04:39 |
What's the latest version of icon.library for OS3.9? | NovaCoder | support.Apps | 3 | 30 June 2009 15:43 |
Requesting icon.library v44+... | nikvest | request.Other | 2 | 16 September 2007 01:58 |
|
|