We'll try and release them but there are some non-technical issues to resolve first.zzd10h wrote:Yes, I wanted to be able to convert Datatype pictures from one format to another for a personal project, a little picture viewer, FastView.
DTM_WRITE feature requests
Re: DTM_WRITE feature requests
ExecSG Team Lead
Re: DTM_WRITE feature requests
Many thanks (by advance) !
http://apps.amistore.net/zTools
X1000 - AmigaOS 4.1.6 / 4.1 FE
X1000 - AmigaOS 4.1.6 / 4.1 FE
Re: DTM_WRITE feature requests
@salass0
Thank you for the release of DTConvert on OS4Depot.
Thank you for the release of DTConvert on OS4Depot.
http://apps.amistore.net/zTools
X1000 - AmigaOS 4.1.6 / 4.1 FE
X1000 - AmigaOS 4.1.6 / 4.1 FE
- salass00
- AmigaOS Core Developer

- Posts: 534
- Joined: Sat Jun 18, 2011 4:12 pm
- Location: Finland
- Contact:
Re: DTM_WRITE feature requests
You're welcomezzd10h wrote:@salass0
Thank you for the release of DTConvert on OS4Depot.
Re: DTM_WRITE feature requests
Hi,
since Update 1, it seems that DTConvert/main.c
dst_dt = IDataTypes->NewDTObject(NULL,
DTA_SourceType, DTST_RAM,
DTA_BaseName, base_name,
PDTA_DestMode, PMODE_V43,
TAG_END);
failed, at least for picture type.
Could it be related to this change ?
datatypes.library 54.7
FIXED
o Using DTST_MEMORY objects could lead to a crash;
o SaveDTObject() in conjunction with DTST_RAM did not create
correct icons;
But after update 1 installation, my SYS:Libs/datatypes.library is 54.6 (08/01/2016) and NOT 54.7.
Typo error or not the correct one shipped ?
edit : Reverted to datatypes.library 53.4 (FE update 0) makes it work again.
Thanks
since Update 1, it seems that DTConvert/main.c
dst_dt = IDataTypes->NewDTObject(NULL,
DTA_SourceType, DTST_RAM,
DTA_BaseName, base_name,
PDTA_DestMode, PMODE_V43,
TAG_END);
failed, at least for picture type.
Could it be related to this change ?
datatypes.library 54.7
FIXED
o Using DTST_MEMORY objects could lead to a crash;
o SaveDTObject() in conjunction with DTST_RAM did not create
correct icons;
But after update 1 installation, my SYS:Libs/datatypes.library is 54.6 (08/01/2016) and NOT 54.7.
Typo error or not the correct one shipped ?
edit : Reverted to datatypes.library 53.4 (FE update 0) makes it work again.
Thanks
http://apps.amistore.net/zTools
X1000 - AmigaOS 4.1.6 / 4.1 FE
X1000 - AmigaOS 4.1.6 / 4.1 FE
- salass00
- AmigaOS Core Developer

- Posts: 534
- Joined: Sat Jun 18, 2011 4:12 pm
- Location: Finland
- Contact:
Re: DTM_WRITE feature requests
Yes, it does look like the wrong version was included in the update.
Versions 54.4 to 54.6 had a bug in the DTST_RAM handling but this was fixed in version 54.7 which was supposed to be the version shipped with 4.1 FE update 1.
Versions 54.4 to 54.6 had a bug in the DTST_RAM handling but this was fixed in version 54.7 which was supposed to be the version shipped with 4.1 FE update 1.
Last edited by salass00 on Wed Jan 04, 2017 7:51 am, edited 1 time in total.
Re: DTM_WRITE feature requests
Thank you for your reply.
Therefore, If I understand well, the v54.7 still works with DST_RAM ?
As I use DST_RAM in my FastView program, I just have to wait for an AmiUpdate delivery ?
Right ?
thx
Therefore, If I understand well, the v54.7 still works with DST_RAM ?
As I use DST_RAM in my FastView program, I just have to wait for an AmiUpdate delivery ?
Right ?
thx
http://apps.amistore.net/zTools
X1000 - AmigaOS 4.1.6 / 4.1 FE
X1000 - AmigaOS 4.1.6 / 4.1 FE
Re: DTM_WRITE feature requests
Hope so too. The bug fix turaround was so much faster with AmiUpdate releases than the 2 year wait for update1.zzd10h wrote:Thank you for your reply.
Therefore, If I understand well, the v54.7 still works with DST_RAM ?
As I use DST_RAM in my FastView program, I just have to wait for an AmiUpdate delivery ?
Right ?
AmigaOne X1000 with 2GB memory - OS4.1 FE
Re: DTM_WRITE feature requests
@Salass00
Thanks for the clarifications
Thanks for the clarifications
http://apps.amistore.net/zTools
X1000 - AmigaOS 4.1.6 / 4.1 FE
X1000 - AmigaOS 4.1.6 / 4.1 FE
Re: DTM_WRITE feature requests
@zz10dh,xenic
Sadly , but that will not be amiupated, you probably have to wait another update
Sadly , but that will not be amiupated, you probably have to wait another update
