SDK 53.24 ... and followups

[Raziel]

Thanks to the team we now have an updated SDK

Does it follow the same advice as the pre 6 OS updates to install it into a fresh dir/partition and let AmiUpdate do the rest?
Or has it the ability to be upgraded over an old SDK (with all AmiUpdates)?

I'd fancy the second but think it's safer to do a new full install plus updates...

[tonyw]

A few betatesters installed it over existing SDK installations without problems, but it's always safer to make a clean installation.

[salass00]

The installation instructions still recommend doing a fresh installation so that's what I did here.

[zzd10h]

Great to see an updated SDK.

Is there a way to see which functions are new or updated ?
A "What's new" file, maybe ?

Thank you OS4 team !

[Raziel]

I did a fresh install, just copied over third party soft like subversion.

Mick did such a great job in managing the SDK updates that it has been a cake to install and update

Thanks a lot to all

[ssolie]

Is there a way to see which functions are new or updated ?
A "What's new" file, maybe ?

I think it would easier if you just did a diff -r between the old one and the new one.

I didn't want to spend time explaining all the details in a text file nobody will ready anyway.

[blmara]

I didn't want to spend time explaining all the details in a text file nobody will ready anyway.

While recompiling my source, at least one change found: there is no IDOS->GetProgramName() anymore, but probably the new IDOS->GetCliProgramName() is renamed version. And there seems to be a change of application.library interface version needed according to autodoc.

Yes, I understand that doing a ChangeLog takes some time, but it also helps to adapt the sources to a new SDK.

Marko

[chris]

While recompiling my source, at least one change found: there is no IDOS->GetProgramName() anymore, but probably the new IDOS->GetCliProgramName() is renamed version. And there seems to be a change of application.library interface version needed according to autodoc.

Yes, if you're using interface v1 (which you will be), OS4 complains profusely when launching your application. It has to be interface v2 when using the new includes. This almost certainly means nothing newly compiled using application.library will work on OS4.0.

There's a new tag to create an alpha channel out of 8-bit picture DT subclasses, some new tags for SetWindowPointer to get the new pointer shapes, some new commodities.library functions to get a list of running commodities and send them messages, dos.library has some new functions and a new function table interface for filesystems and... that's all I've discovered for now.

Yes, I understand that doing a ChangeLog takes some time, but it also helps to adapt the sources to a new SDK.

Usually I miss some new functionality, so a changelog would be useful.

[ssolie]

While recompiling my source, at least one change found: there is no IDOS->GetProgramName() anymore, but probably the new IDOS->GetCliProgramName() is renamed version. And there seems to be a change of application.library interface version needed according to autodoc.

Both of these changes should be covered by the SDK FAQ now.

[Belxjander]

Well I ran into a weird problem...

The SDK Installer decided to cut off everything past the entry for the SDK in my User-Startup sequence

and as that entry was near the beginning... obliterated ALL of the file following...so I lost the MUI and Application assigns for everything else installed.

Neat fun... not... is the Installer suppossed to have exclusive control or have any trigger for "cutting short" files like that ?

repeat installation did not repeat this fault... so something about my original User-Startup triggered the misbehaviour