It's not that anyone is checking the Depot for new SDK addons daily. For a mere porter this is the easiest to keep up to date.
The main problem with the current SDK update server IMHO is that it wants to install everything. If it could be made to work more like a package manager where you select which components you want to install it would be better.
Ahh ok. There probably wouldn't be much that would need to *only* be on the SdkServer and not on OS4Depot too, but there could be exceptions and a desire for that.
As for AmiUpdate always selecting all by default, some of the packages could be set to only be listed if you already have them installed. Or, you could always Deselect All then tick the ones you want. And of course, no-one has to use it if they don't like it :)
---------
Just tried logging into the AmiUpdate site. Either I've forgotten my user/pass or the SDK stuff has been removed. I'll fire off an e-mail to Simon.
Edit: I was just using the wrong username :)
Edited by MickJT on 2015/9/3 15:46:23 Edited by MickJT on 2015/9/4 6:13:00
The release of current SDK for FE is great news indeed. I just wonder if anyone tried it with Cubic IDE - this is the environment I'm using on classic. I wish Cubic got updated as well to support AmigaOS 4.1 FE with latest SDK. Anyway before I will destroy my working environment by installing latest SDK I am curious of other Cubic IDE users experience.
The main problem with the current SDK update server IMHO is that it wants to install everything. If it could be made to work more like a package manager where you select which components you want to install it would be better.
That's not the fault of the server, but rather a mistake made by those adding/updating the entries in the database. There's a flag that indicates "only update if an older version is already installed." Some people forget to set that (or maybe they think that their work is so important that everyone should install it ).
IIRC, AmiUpdate does allow you to add entries to a personal ignore list, so you can use that to work around the entries you don't want that don't have that flag set.
BMATags_RGBFormat was set to TAG_USER+2, was private tag.. (also noted in the include files)
You should really not be using that.
I just unarchived the latest SDK, and that tag is public now. It's documented in the autodocs, and is in the graphics/gfx.h header. It makes sense as p96AllocBitMap() can't be deprecated unless developers have access to that tag.
@AmigaBlitter Your compiler is probably using old header files from somewhere.
EDIT: Gazelle is right, it's BMATags_PixelFormat, and not BMATags_RGBFormat.
Hi guys, sorry for my silly question but as there is this topic I used it to ask a thing..
In this new SDK release, reading the docs, in the new features there is an AutoDocs Viewer. I browsed the SDK directory but I was able to find only the readme.txt file in this path: SDK/local/Documentation/Tools/AutoDocViewer/
Where is the program?
Thanks,
Edit:
I looked here as reported in the readme file (url) but it seems is no more available..
In this new SDK release, reading the docs, in the new features there is an AutoDocs Viewer. I browsed the SDK directory but I was able to find only the readme.txt file in this path: SDK/local/Documentation/Tools/AutoDocViewer/
Where is the program?
It's in "SDK:local/C".
I was wondering this too and had to use the WB Find feature to find it.