Good morning,
I started the development of a preferences manager for Aros with Hollywood.
It is almost complete and working quite well excluding a bug that it is almost a month that I 'm playg around without success.
I'm looking for sone support from the Hollywood community here in aros to catch this bug (l' m quite sure it is due to Hollywood itself) or find a work around. Contact me at sb5@libero.it and I will supply the code.
Regards

Solved all problems, now the program is functionally completed. I need only to complete the catalog support (that's why I developed GoCatalog actually in queue on Aminet that should make this activity quite easier).
If someone wants to cooperate with translations let me know at sb5@libero.it

Version 1.0 in queue on Aros Archives

@Ilbarbax

It works well on AROS 64-bit via Emuv0

I can confirm that Preferences works well even in 64-bit mode, but the visibility of the icons needs improving; there is a strange glare and the second side of the DualPNG icon is not visible.

Furthermore, some backgrounds should be added which might help to cover up the flaws in the icons.

I would also add that the preferences in (Script) mode listed as ‘StatusBar’ and ‘AROS One Prefs’ on AROS One cannot be executed from the Preferences GUI.

The quality of the icons does not depend on my program, I use the program icon2png from Mike Riddle to convert the icons. It was supplied years ago, may be actually he can improve it. Moreover it extract only the front icon and not the second one, therefore I realized the yellow aura to highlight the active one.

During my test AROS One Prefs was working fine. I will have a check.

PS checked AROS One Prefs on my quemu arosone and I confirm that it does not work, but it does not work on Prefs directory too giving an iconx error.

AROS One Prefs and Status Bar are scripts and work fine on QEmu; it’s odd that they aren’t working for you – please check your Tooltypes settings.

Scripts run via IconX must be executed one at a time, not simultaneously. If you’ve run Status Bar, you must close the Status Bar request GUI and then run AROS One Prefs.

Thanks for the information. I will update the program for you later today to extract both icon images. I use the same code to split PNG icons in one of my other apps. It will be a quick update then I'll post the icon2png executable here.

This is iconsplit cli version. It has replaced icon2png because it does the same thing. It splits a PNG glow icon into images saved to Ram Disk.

If you need to specify the output path for both images I can modify iconsplit to allow that functionality.

Thanks, miker. I’ve compiled Iconsplit for 64-bit and it works fine, but I’ve encountered a small issue with the 64-bit version: if you use an icon file without an extension (.info), a Guru error appears.

I’ve also noticed that the version of Iconsplit you attached is 1.1.0, whereas the version you attached a year ago for AROS 68k also called Iconsplitter was 1.3.0, which I then compiled for 32-bit and 64-bit using your source code.

A real icon always has a .info file extension. The program searches for the png file signature as well as the .info extension. If you have a single PNG file with .png extension it's a picture file. If you have a PNG file with a single image with .info extension then it's an icon file. Both have to be true for it to be an icon. An icon can have one or two images.

I will update it to catch the error when an improper file is used and I will update the version to 1.3.1 to be consistent with the 68k version.

This version of iconsplit can extract images for PNG glow icons, IFF glow icons & IFF glow icons where icon data is stored in tooltypes (new icon). Currently all images are extracted to Ram Disk for simplicity.

@Ilbarbax

Do you need to be able to set the paths for image1 & image2 or can they just be extracted to Ram Disk to be used in Preferences Manager?

Thanks, miker. By the way, for the 32-bit version, there’s no Guru with icons without extensions.

If there are no differences between the new version 1.1.0 and the old 1.3.0, I can delete the old one.

Mike,

definitely the path is better, so I can directly store the brushes in the desired directory (to be also reused in case already present avoiding the time to reconvert them).
however I use a command like this one

fullpath(prefs_data_path$,"icon2png".." "..fullpath$.." "..p_path(brush_temp_path$,filename$).." >NIL:"

practically I run icon2png with the source file and destination file.

May I suggest that there could be a sort of switch if only the first image is desired or both.

thanks

@Ilbarbax

Here is the syntax for the new Icon2PNG which uses the IconSplit base code. I modified it to allow the use of separate output paths for both images or you can specify with a switch which image to extract. Note that the switch uses two dashes such as - - n or - - s.

Looking at the screenshot image the first item - icon2png icon.info will extract both images to Ram Disk as before. Starting with second item you can add --n for the normal image or --s for the select image to extract either image independently. As you see in the third item you can specify the output path for the normal image. But in this case the select image (second image) will be extracted to Ram Disk because there is no path2 specified, so be careful.

In the fourth syntax item by adding the --n switch it will only extract the normal image to the specified path. The fifth item allows extracting both images to the specified output paths. However, item six is interesting because in order to extract the second image to a specific path you must also include the output path for the first image. That is so the program knows which is path2 which follows path1 such as argv[3] & argv[4] in sequence. But as long as you specify both output paths as in the last item you can extract either image using a switch.

I'll finalize the new version and post it here either later today or tomorrow. I hope this helps! :-)

Great. You are covering all the possibilities. More than that I can't desire

@Ilbarbax

Here is the new release version of icon2png with the features I explained earlier. As long as you use the correct syntax as I explained for a png glow icon with 2:images it should work as expected. But if for example you try to extract the 2nd image of an icon with a single image it may cause a problem. I didn't test that so I'm not sure what will happen. :-p