ABIv11 Build System ( New AROS One ABIv11)

I have already compiled these sources and others

https://www.arosw...#post_7478

You might ask @deadwood to help compiling the Datatype.

Are you using the ABIv11 Build System? Or some other method to compile the Datatype?

I tried "PicDT_CreationPackage", it also seems easy to use, but I get the same error as with the compilation via the shell "cannon find -larosc", plus the error "Genmodule : Function not implemented", see screenshot

The "-larosc" error has been siscussed on "ae.arosworld" see link, but I don't know where to correct the Makefile

https://ae.aroswo...34#msg7934

OK thank you, if it's too difficult I'll give up, however all my compilations were done with AROS One v1.0 "ABIv11 Build System"

AMIGASYSTEM

Thank you for testing. You are good at finding issues! 🙂

I haven't tried to compile Icon Splitter for 64 but.

As for SVG Datatype to compile Datatypes you can't use the shell. You need the Picture Datatype Creation Tool from AROS Archives or you need to use the ABIv11 Build System. There are many dependencies for Datatypes.

miker, I'm trying to compile the svg.datatypes on Aros One v11 x86 64-64Bit on WMware, but I encounter an error in the "makefile", when you have time you can take a look at it

https://archives....6-aros.zip

From WMware I tried compiling your "IconClone" and "Icondrop" on AROS One v11 x86 64 and they work perfectly, while "IconSplitter" crashes, but I guess it depends on the v11 x86 64 system!

I'm still working on revising & testing PixieView as well as ViewTIFF. More updates will be posted when they are available.

PixieView is working with the newer system files.

Nice new icons too!

When I had to re-write Load_ImageDT function to fix not being able to delete the image after viewing I forgot one important part to view ILBM images or any other image less than 8 bitplanes.

In order to display these images I use a Datatype trick. No matter how many bitplanes of data the image has if it's less than 8, the planar bitmap in the Datatype always has 8 bitplanes. So some planes are filled and the rest are empty.

So if ( depth<8 ) depth = 8; Then when we are ready to display the image we use the stored pixel format vs. the requested pixel format. So if depth = 8 or depth = 32 we request 32bit ARGB. Now we use WritePixelArrayAlpha to display it.

Thanks miker, now PixieView displays image XBM !

Here is the revised PixieView program. It once again supports images less that 8 bitplanes.

The About Information has been updated and the rotate functions don't leave fringing. :-)

OK as soon as I download PixieView I will start building and deploying the new AROS One 2.7, so that I can then devote myself to the new Core 20241209-D04 !

AMIGASYSTEM

The PixieView program has been revised. I updated the About Information & I fixed the fringing on the image when rotating left or right. I also added the fix for images less than 8 bitplanes so that they will display correctly.

I will compile it & post it at lunch time today in a couple hours.

Attach image XBM

Could you post some XBM images to test with?

Post the XBM that caused this warning message. I suspect it is a different bit depth.

I will probably need to make a small change for display purposes. If ( depth < 8 ) depth = 8.

It seems that XBM is black and white with 1 bitplane = 2 colors.

Could you post some XBM images to test with?

miker, Pixieview does not recognise the XBM format, see screenshot, with Multiview the XBM format works fine

OK thanks, in the meantime Pixieview is the default tool for viewing images on the new AROS One that will be released in a few days.

The Zoom In/Zoom Out & Maximize/Minimize using Scrollbars will be in the next update as well as being able to open images centered on screen rather than at top left corner of screen.

These features require a large re-write of the program & much of the existing source code needs to be cleaned up. There's much work to do. :-)

P.S. - I'm working on revising S-MultiView (Super MultiView) for testing purposes. If I'm satisfied with the new features I will ask deadwood if we can include many of the new features in standard MultiView that we all know & use daily.

The new features are Edit File on the Edit Menu that looks at the App Icon to open an editor based on the currently loaded Datatype Object. Also new is the ability for About information to recognize HAM6/HAM8 & EHB images. Zoom In & Zoom Out, Maximize & Normal are all working. Only Minimize (Iconify) isn't working yet. I have to fix that.

I'm not sure if Convert to PNG will be included, but for Picture files that's very useful. For Sound we could have Convert to WAV. For IFF Text we could Convert to standard text. That will all be tested in S-MultiView to make sure it is working.

Of course, the other option is to completely omit the Convert to functions & instead just use Edit File to open the current filename in the appropriate editor. Then it can be easily converted. I haven't decided yet. But keeping MultiView as pure as possible is surely as important as adding features to improve upon it.

Thanks miker, now the images can be deleted, PixieView is perfect, there is only a small problem, it is not important maybe you can improve in the future, in practice if you view an Image higher than the resolution of the video used, the image is cut and you can not see it in full.

For example, if you have a 1024x768 screen, you can't see the entire image at a resolution of 2048x1024.

With Multiview, Zoom is not supported, but you can see the entire image via the vertical/horizontal scroll bars