As far as I know, the Warp Datatypes are receiving updates every now and then. So it does make sense to support the author. At least until update 3 or any updates for os4 are being rolled auf again.
Edit: 6 Datatypes have received updates since AmigaOS 4.1 Final Edution Update 2.
FWIW, I've been using Warp datatypes for a long time without any issues, including with WEBP files and an old beta of Multiviewer. Those datatypes are REALLY mature software.
@jabirulo
I agree with Tuvok, the Warp datatypes continue to get regular updates and may even support more functionality than the ones bundled with AmigaOS.
Thanks for your help. After several inconclusive attempts, including trying Multiviewer 2.2 and moving some datatypes, I've concluded that the warpdts aren't working very well for me (yes, I did install the OS4 versions).
Jabirulo, I installed the link you gave me, and it works perfectly with Multiviewer 3.18.
I personally didn't delete any datatypes... I just installed the Warp ones with their installers (which could have?).
On the other hand, aside from the radeon driver (bought) and the old Multiviewer I was testing and working on (scripts), I have *sero* of MattyOS installed.
If you wanted to get to the cause, you could try booting your system off a clean AmigaOS (the install CD?) and seeing if Multiviewer works with the operating system then?
Multiviewer works, but as soon as I introduce a single datatype in Warpdt's classes/datatype, multiviewer no longer works.
Then I have a choice: either to use Warpdt and no longer use multiviewer, or not to use Warpdt and have a functional multiviewer. That's the choice I made: not to use Warpdt.
That's very odd. I use both MultiViewer and the WarpDT datatypes just fine. But I do not use the datatypes.library included with Enhancer, only the one included with AmigaOS. In fact I am extremely selective about what I install from Enhancer to the absolute minimal when it comes to components that replace anything included in AmigaOS.
-- eliyahu
"Physical reality is consistent with universal laws. When the laws do not operate, there is no reality. All of this is unreal."
I've been using WarpDT since a long time now (from my former A1200 more than 20 years ago) and they are still working flawelssly on my X1000, Sam460 and FPGA Replay/060.
I reinstalled Warpdt and replaced datatypes.library with the one from Update 2, and everything works!
I'm still having a problem with Webp: the image icon is displayed, but when I click to display the image in multiview or multiviewer, it tells me "invalid data."
I'm using all Warpdt.
I just reinstalled Webp_dt, which you told me, Jabirulo. Now I can open the image.
Good to hear. The bottom line I follow with Enhancer components is this: unless there is a very good reason to replace an AmigaOS component with one from Enhancer -- like a specific feature that is new that you absolutely must have -- don't do it. Only install things that do *not* replace AmigaOS components unless you absolutely have to.
-- eliyahu
"Physical reality is consistent with universal laws. When the laws do not operate, there is no reality. All of this is unreal."
Do you know which version of the Enhancer datatypes.lib and WarpWebP.datatype you were using together? I have the Enhancer datatypes library and WarpWebP installed and can load WebP images in Multiviewer without issue.
I'm using WarpWebP version 45.5 (11.1.2024) and for Datatypes.library, it's version 54.6 (8.1.2016) of Update 2 and not the one from Enhancer Software 2.2. (54.15, 9.1.2022 of Amigakit).
I solved my problem with WarpWebP. I remembered last night in bed that I had changed something in the WarpDT prefs.
I just put it back to the way it was before and now I can open a WebP image with Multiview and Multiviewer.
Actually, it's version 54.15 (9.1.2022) of Amigakit that's causing problems with Multiviewer.
There are issues with the Enhancer software. Also, never mix Enhancer and AmigaOS versions of C:AddDataTypes and LIBS:datatypes.library together, as Enhancer is not necessarily AmigaOS compatible.
What was the setting in WarpDTPrefs that was causing an issue with WebP?