icon.library 46.4 test versions

[PeterK]

Sorry, it's me again and ....

Link removed.

Thanks to everybody who has tried to help or support me!

[Retrofan]

Hi Peter, is everything ok about money now?. We are a family here, just tell if you like or by PM. Money is the easiest thing to fix having friends

[bloodline]

Sorry if this is the wrong place to ask, but does anyone know why there are the functions addFreeList() and freeFreeList() in the icon.library?

Shouldn’t these functions be in exec?

[voxel]

@bloodline ^^)

if you patch/replace an exec function by some more optimized code or else you find the new code (under the same function name) in the software that patches the old function...

[Thomas Richter]

Originally Posted by bloodline

Sorry if this is the wrong place to ask, but does anyone know why there are the functions addFreeList() and freeFreeList() in the icon.library?

Shouldn’t these functions be in exec?

Oh well. This is - as always im AmigaOs - a historical accident. The icon.library requires some sort of resource tracking to ensure that all memory allocated with an icon is released as soon as the icon is released. That could also be done manually by checking all the pointers when releasing an (possibly even incomplete) DiskObject on release, but apparently the original creator considered it be more convenient to have this adminstrated by the library, and also considered it to be useful to have these functions exposed to the outside.

In reality, nobody else but the icon.library itself uses these functions. Intuition has AllocRemember(), for example, and exec received memory pools later on.

So, this is all legacy cruft, and an early (and not quite succesful) attempt for resource tracking. New code should not use these functions anyhow, and there are better ways how to track memory, e.g. by exec memory pools.

[bloodline]

Originally Posted by Thomas Richter

Oh well. This is - as always im AmigaOs - a historical accident. The icon.library requires some sort of resource tracking to ensure that all memory allocated with an icon is released as soon as the icon is released. That could also be done manually by checking all the pointers when releasing an (possibly even incomplete) DiskObject on release, but apparently the original creator considered it be more convenient to have this adminstrated by the library, and also considered it to be useful to have these functions exposed to the outside.

I sort of suspected/feared as much! I’ve never used the icon.library, so looking over the autodocs a while back these two functions stuck out like a sore thumb. RJ Michal does like to go on about what a mess OS1.x was, and you can see why when there is cruft like this scattered around.

Many thanks for the explanation.

[PeterK]

Many thanks to everybody who has tried to help or support me during the last months. But I hope on your understanding when I don't want to talk here about that time anymore.


Update to icon.library 46.4.515

On filesystems which cut down long file names (like floppies) the icons that are losing their ".info" extension will no longer overwrite or delete their own mother file when you drag&drop files. But there is no protection like this for the contents of copied drawers and this does also not affect the Copy command or filemanagers.

[AMIGASYSTEM]

Welcome back, your absence created a void, thanks for updating this useful library

[Genlock]

Originally Posted by PeterK

Many thanks to everybody who has tried to help or support me during the last months. But I hope on your understanding when I don't want to talk here about that time anymore.


Update to icon.library 46.4.515

On filesystems which cut down long file names (like floppies) the icons that are losing their ".info" extension will no longer overwrite or delete their own mother file when you drag&drop files. But there is no protection like this for the contents of copied drawers and this does also not affect the Copy command or filemanagers.

Hi Peter, Nice touch mate

[Mark sealey]

Can anyone help me with this icon display issue ?

https://m.facebook.com/story.php?sto...13580129224184


https://youtu.be/Hh_BLJXNU7o

[AMIGASYSTEM]

The video is not accessible to those who do not have a Facebook account, uses Google Drive practical, simple and easy to access for everyone; you can also attach a sreenshot that shows the problem encountered

[Tigerskunk]

Thanks for keeping on working on the Icon-Library, Peter!

[Mark sealey]

Originally Posted by AMIGASYSTEM

The video is not accessible to those who do not have a Facebook account, uses Google Drive practical, simple and easy to access for everyone; you can also attach a sreenshot that shows the problem encountered

My apologies....added a YouTube link...currently uploading to Google drive.

[AMIGASYSTEM]

Thank you, what minute can we see the problem? the video lasts about 10 minutes

[Mark sealey]

Originally Posted by amigasystem

thank you, what minute can we see the problem? The video lasts about 10 minutes

2.47 ?

[AMIGASYSTEM]

Originally Posted by Mark sealey

2.47 ?

If it's the system crash it could be that the filesystem is corrupted or HD with some physical problem, have you tried to copy that folder to another volume or device?

[PeterK]

Hello Carlo, nice to see that you want to help me.

Originally Posted by Mark sealey

Can anyone help me with this icon display issue ?

https://m.facebook.com/story.php?sto...13580129224184


[ Show youtube player ]

Sorry, but that's not enough information. Ok, your "About" message says Kickstart and OS 3.1.4, but it doesn't look like a clean OS 3.1.4 installation at all, more like an old 3.1 system, which was updated with 3.1.4.

What were your last hard- or software changes to the system before this issue started to occur? (Furia sometimes has hardware problems.)

Which version of icon.library is installed. Does it happen with other (older)versions too? Did you try the library from OS 3.1.4 v45.22? Which screenmode are you using?

Version Libs:icon.library FILE FULL

Upload your startup-sequence as a text file, please.

Hmm ... that all seems to be an old hardware problem ... http://eab.abime.net/showthread.php?...66#post1275266

[Mark sealey]

Originally Posted by PeterK

Hello Carlo, nice to see that you want to help me.




Sorry, but that's not enough information. Ok, your "About" message says Kickstart and OS 3.1.4, but it doesn't look like a clean OS 3.1.4 installation at all, more like an old 3.1 system, which was updated with 3.1.4.

What were your last hard- or software changes to the system before this issue started to occur? (Furia sometimes has hardware problems.)

Which version of icon.library is installed. Does it happen with other (older)versions too? Did you try the library from OS 3.1.4 v45.22? Which screenmode are you using?

Version Libs:icon.library FILE FULL

Upload your startup-sequence as a text file, please.

Hmm ... that all seems to be an old hardware problem ... http://eab.abime.net/showthread.php?...66#post1275266

Thanks for the reply....I have had your library working.....awhile ago....but I had to rebuild my boot partition.

Currently its a os3.1.4.1 build with

fblit(os314.cfg)

Full pallet patch

Visual prefs

Mcp in WBstartup

High res laced (pal...via indivision ecs v2)

Peter K icon library from aminet
(020 icon library)

I'll post further information when I get home.

EDIT:

Icon.library 46.4.513

screenmode PAL:Hi Res Laced (default width/Height 16 col)

[PeterK]

Please try another icon.library like v45.22 of OS 3.1.4 or 46.4.515 from the first page of this thread.

Copy your Prefs and FullPalette drawers with their contents into a lha archive and upload that together with your startup-sequence.

--------------------------------

The icon.library 46.4.515 can be downloaded from Aminet now:

http://aminet.net/package/util/libs/IconLib_46.4
.

[James]

Originally Posted by PeterK

The icon.library 46.4.515 can be downloaded from Aminet now:

http://aminet.net/package/util/libs/IconLib_46.4
.

Thanks PeterK!