Oh no! Where's the JavaScript?
Your Web browser does not have JavaScript enabled or does not support JavaScript. Please enable JavaScript on your Web browser to properly view this Web site, or upgrade to a Web browser that does support JavaScript.

Picture Tools

Last updated on 4 days ago
M
miker1264Software Dev
Posted 1 month ago
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.
Edited by miker1264 on 05-12-2024 12:41, 1 month ago
AMIGASYSTEMAMIGASYSTEMDistro Maintainer
Posted 1 month ago

miker1264 wrote:

@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.

miker1264 wrote:

@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.

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 !
AMIGASYSTEMAMIGASYSTEMDistro Maintainer
Posted 1 month ago
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.
AMIGASYSTEM attached the following file:
test-pixieview.zip [8.47MB / 37 Downloads]
AMIGASYSTEMAMIGASYSTEMDistro Maintainer
Posted 1 month ago
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.
M
miker1264Software Dev
Posted 1 month ago

AMIGASYSTEM wrote:

@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.


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.
M
miker1264Software Dev
Posted 1 month ago
AMIGASYSTEM

After doing some testing with PixieView I found the unfreed resource that prevented deleting an image after viewing.

The source code is several years old and it's very messy. In the Load_Image_DT function there is a subfunction to read the BMHD by using a Datatype. But the DTObject wasn't being freed.

I will revise it and I will compile a new version later today and post it for testing.
M
miker1264Software Dev
Posted 1 month ago
I will compile & post the updated PixieView program later today. It will solve the problem of not being able to delete a picture file after viewing.
M
miker1264Software Dev
Posted 1 month ago
AMIGASYSTEM

Try this new version of the PixieView program. You should now be able to delete a picture file after viewing it. If you find any issues please let me know so I can fix them. Thanks for testing.
miker1264 attached the following file:
pixieview_x86_12-09-24.zip [41.18kB / 35 Downloads]
AMIGASYSTEMAMIGASYSTEMDistro Maintainer
Posted 1 month ago
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
M
miker1264Software Dev
Posted 1 month ago
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.
Edited by miker1264 on 09-12-2024 17:01, 1 month ago
AMIGASYSTEMAMIGASYSTEMDistro Maintainer
Posted 1 month ago
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.
AMIGASYSTEMAMIGASYSTEMDistro Maintainer
Posted 1 month ago
miker, Pixieview does not recognise the XBM format, see screenshot, with Multiview the XBM format works fine
AMIGASYSTEM attached the following image:
xbm.jpg
M
miker1264Software Dev
Posted 1 month ago

AMIGASYSTEM wrote:

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


Could you post some XBM images to test with?
M
miker1264Software Dev
Posted 1 month ago

AMIGASYSTEM wrote:

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


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.
Edited by miker1264 on 10-12-2024 14:19, 1 month ago
AMIGASYSTEMAMIGASYSTEMDistro Maintainer
Posted 1 month ago
Attach image XBM
Edited by AMIGASYSTEM on 10-12-2024 14:58, 1 month ago
AMIGASYSTEM attached the following file:
test_1.zip [74.48kB / 29 Downloads]
M
miker1264Software Dev
Posted 1 month ago
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.
AMIGASYSTEMAMIGASYSTEMDistro Maintainer
Posted 1 month ago
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 !
M
miker1264Software Dev
Posted 1 month ago
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. :-)
miker1264 attached the following file:
pixieview_x86_12-11-24.zip [41.13kB / 28 Downloads]
AMIGASYSTEMAMIGASYSTEMDistro Maintainer
Posted 1 month ago
Thanks miker, now PixieView displays image XBM !
M
miker1264Software Dev
Posted 1 month ago

AMIGASYSTEM wrote:

@AMIGASYSTEM - Thanks miker, now PixieView displays image XBM !


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.
You can view all discussion threads in this forum.
You cannot start a new discussion thread in this forum.
You cannot reply in this discussion thread.
You cannot start on a poll in this forum.
You cannot upload attachments in this forum.
You can download attachments in this forum.
Moderator: Administrator
Users who participated in discussion: AMIGASYSTEM, Amiwell79, miker1264, mattson62, Templario
Sign In
Not a member yet? Click here to register.
Forgot Password?
Users Online Now
Guests Online 9
Members Online 0

Total Members: 271
Newest Member: enzorug
Member Polls
Should AROSWorld continue with AROS-Exec files (SMF based)?
Yes44 %
44% [12 Votes]
No26 %
26% [7 Votes]
Not sure30 %
30% [8 Votes]