[quote name=AMIGASYSTEM post=6961]@AMIGASYSTEM - miker with PixieView I have encountered on Wanderer but also on Dopus4 a strange thing, after you view a graphic file, afterwards it cannot be deleted, reason file in use ! with multiview this does not happen.[/quote] I've noticed the same issue. I will look into it. There is also some unfreed resources at times. Maybe the two issues are related. If you notice anything else please let me know.

miker with PixieView I have encountered on Wanderer but also on Dopus4 a strange thing, after you view a graphic file, afterwards it cannot be deleted, reason file in use ! with multiview this does not happen.

Modified and reconfigured Dopus4 and Def_Icons, created a small video where PixieView on Wanderer displays 12 different graphic formats "without extension". The last TIF image instead displayed with 'PicShow', where via PicShow I make a SlideShow, attach video.

[quote name=miker1264 post=6957]@miker1264 - Thank you for downloading & testing the program. It has come a long way since I started the project many years ago. The next step is to use a new display method with Datatype Objects so that I can adapt PixieView for Amiga 68k. I already have a small program working on Amiga. If you are talking about how icon images are displayed in a larger window than normal that's because I set a minimum window size of 100x120 for icon images. I was frustrated with MultiView opening the icon images with small Windows. They were so small I couldn't move the window or resize the window easily. One of my to do items is to open the images centered on screen rather than the default location at (0,0) top left of the workbench screen. If you are using PixieView on AROS x86 then the TIFF Datatype should work. But if you try to open a Tiff file using MultiView with TIFF Datatype then MultiView will crash. I suspect it can't load Tiff Lib which is an external library not internal.[/quote][quote name=miker1264 post=6957]@miker1264 - If you are talking about how icon images are displayed in a larger window than normal that's because I set a minimum window size of 100x120 for icon images. I was frustrated with MultiView opening the icon images with small Windows. They were so small I couldn't move the window or resize the window easily.[/quote] Yes I was referring to these problems, which is why I preferred PixieView. PixieView does not display TIF images on AROS One, because there is no tif.datatypes, to display TIF images I use "PicShow" For Animations and Music remains Multiview as a tool on Dopus4 and Wanderer !

Thank you for downloading & testing the program. It has come a long way since I started the project many years ago. The next step is to use a new display method with Datatype Objects so that I can adapt PixieView for Amiga 68k. I already have a small program working on Amiga. If you are talking about how icon images are displayed in a larger window than normal that's because I set a minimum window size of 100x120 for icon images. I was frustrated with MultiView opening the icon images with small Windows. They were so small I couldn't move the window or resize the window easily. One of my to do items is to open the images centered on screen rather than the default location at (0,0) top left of the workbench screen. If you are using PixieView on AROS x86 then the TIFF Datatype should work. But if you try to open a Tiff file using MultiView with TIFF Datatype then MultiView will crash. I suspect it can't load Tiff Lib which is an external library not internal.

miker PixieView is now perfect, on Dopus4 it performs much better than Multiview. Multifiew showed the small images so small that the window could not be closed. PixieView on the other hand shows the small Images in real size so well manageable! On the forthcoming AROS One PixieView will be the viewer of all the image formats described above even without extension, both on Dopus4 and Wanderer All Def_Icon "Images" will now have PixieView as a tool, except TIF Images which will have an Application that supports this format.

Here is the current version of PixieView that works with Default Tool set in picture icons.

I have tried all image formats supported by AROS One thanks to the Datatypes Descriptors! The formats successfully supported (with or without extension) on AROS One by PixieView are 12, only the TIF format is not supported because AROS lacks datatypes: - XPM - XBM - PPM - WEBP - TGA - SVG - PNG - PCX - JPG - ILBM - GIF - BMP PixieView is a light and fast viewer, for the future to improve it even further we could add a Zoom to enlarge or reduce images that are too big or too small, and a Slide Show to view or browse images in a drawer. Thanks miker, sorry if I demanded a lot!

That was the problem. It's working now. Later today I will compile the new binary for the program & post it. Hopefully, it's the final version for now. :-)

AMIGASYSTEM Sometimes when you leave a problem unresolved for a day or two the solution becomes more obvious. I believe I know what's wrong. There are two ways to start a program - CLI method & WB method - from shell or from workbench. The shell method is easier. For PixieView you send two arguments, the program name & filename to open. So argc = 2, argv[ 0 ] = program name & argv[ 1 ] = full path. But when you start from workbench the shell argc = 0. But workbench (Wanderer or Magellan) sends a WB message. In the message argc = 2. Again argv[ 0 ] = program name & argv[ 1 ] = full path. But the way workbench deals with the path is different. Just like using a file requester there is a PathPart & FilePart. I seem to have grabbed the FilePart without the PathPart. So when the picture file & program are in the same directory no problem. It doesn't need a full path. So to resolve the issue I need to revise the code in main for the WB message to get the PathPart & then use AddPart to combine PathPart + FilePart to get a full path not just a filename.

miker also on AROS One (Wanderer) works fine if the executable "PixieView" even without Icon is in the same path as the images, in practice it works perfectly as Multiview, whether the images are on Hardisk, on RAM, or on a shared folder on Windows So no parameter is needed in Tooltypes, but "PixieView" is required in the same path as the image, probably the "PixieView" added in the icon as a tool is ignored.

The PixieView program is just a lightweight picture viewer/converter with a few effects added to show what is possible. I intentionally didn't include more effects or features to keep it simple. I'm just pleased that it works, mostly. :-) If you need something more then there are several options of great graphics programs for use with AROS. I like Zune view/Zune Paint and of course Luna Paint. But there are many more.

[quote name=AMIGASYSTEM post=6937]@AMIGASYSTEM - Thanks, tested on AROS One and it works fine, but to run the image from Icon, you have to add the parameter "CLI" in the ToolTypes, this way PixieView will run via Shell If there is nothing in the Tooltypes or there is the parameter "WB" (used by Multiview and all applications that run from Workbench), the image will not be opened. The CLI parameter does not allow the information message to be hidden! If you have to display a lot of images, it might be annoying![/quote] I didn't have to use CLI or WB in the icon DefaultTool. I just used Magellan with Icon Information to add a DefaultTool. I navigated to the PixieView icon then chose 'save'. On double-click it just opened the image in PixieView. Admittedly, though it didn't work the first time, or the second time. I copied the PixieView program and icon to Ram Disk. I copied a test image there also and I changed the DefaultTool. In Ram Disk it worked fine. I did a drag-n-drop from Ram Disk to MyWorkspace then I edited the DefaultTool of the image in Ram Disk. It no longer worked. It wouldn't open PixieView! That wasn't expected. So I assumed there was something wrong with Magellan drag-n-drop. Maybe DOS or Intuition isn't immediately aware the program was copied? Anyhow, I used Magellan in Name View to copy the program and icon separately to MyWorkspace. Then the image in Ram Disk opened just fine with PixieView in MyWorkspace. How strange? I suppose copying the program in a shell should also work. I haven't tested it on AROS One yet. I will do that tomorrow morning. But there is definitely some strange behavior. If you copy a picture file and PixieView to Ram Disk and change the DefaultTool then it works. Copy the program anywhere else and change the DefaultTool and it won't open the picture file! How strange.

Juan your Pintor Web is a very good, with PixieView I wanted to replace Multiview to view images on the fly.

Well, also you can use Pintor Web to make some nice effects.

Thanks, tested on AROS One and it works fine, but to run the image from Icon, you have to add the parameter "CLI" in the ToolTypes, this way PixieView will run via Shell If there is nothing in the Tooltypes or there is the parameter "WB" (used by Multiview and all applications that run from Workbench), the image will not be opened. The CLI parameter does not allow the information message to be hidden! If you have to display a lot of images, it might be annoying!

Here is the revised PixieView program. I work full time at my work from home job so I didn't have time to do it yesterday. It works if you use a shell or in Magellan if you use Open With... or if you use DefaultTool in a icon or if you open the program with it's icon. I copied the program and icon to SYS:MyWorkspace/Programs and I copied a picture file to Ram Disk. I changed the DefaultTool in the icon. PixieView opened with a double-click just like using MultiView.

Thanks, now the user after viewing the image will also be able to make changes or convert the images to the available formats.

AMIGASYSTEM I haved solved the Open With Default Tool issue for PixieView. Now you can set the Default Tool in the icon to match the path to PixieView then double-click the icon to open the image. It works the same as Default Tool to open in MultiView. It uses WBStartup method. Later today I will compile a new binary file to post for you to use.

[quote name=miker1264 post=6913]@miker1264 - [quote name=AMIGASYSTEM post=6910]@AMIGASYSTEM - Perfect as always miker, light fast and useful,created AROS One x86/68k style Icons ![/quote] Thanks! I really like the new icons. You are an artist. :-)[/quote] At best, I am a good 'cut and sew' tailor :)