Connect
Are there any 68080 macros for ASM1 available? Or is everyone just porting from C?
While sick in Japan the other day, I created a small library for reading directory contents easily with memory management based on dirent.h. Mostly just for me but thought I'd share. Added autodocs as well.

https://github.com/nyteshade/clib-directorylist
Brielle Harrison: Also open to any comments or bugs found when looking at my code
[Amiga Image Question]

I am used to working with pixels from a 32-bit integer representing RGBA or ARGB colors where each of the alpha, red, green and blue get a byte’s worth of color representation.

Can anybody recommend a reference to learn the differences between this modern approach and how it works for planar pixel data? As well as discerning how to read and set colors for this setup?
nightshft: Yes correct. Look here http://amigademomaking.dk-games.com/step20-bitplanes-are-evil I guess they went for this system because you'd save memory when using less than 8 bits for color. But as already mentioned you'd loose a lot of time for conversion and bit-setting in some graphic engines. This is what's called "chunky to planar" conversion and it's a science in itself. It's also the reason why 3d engines in general (and "doom" as a reference in particular) cost more cpu on the miggy than on early dos pc's.
Brielle Harrison: The demo making page is awesome. All these links really help not only myself but others as well.
[Workbench Icon Question]

I am curious about icon creation and manipulation from an OS API level. Are there methods for any of the following things in Amiga OS? If not, any ideas on how to do so programmatically?

+ Creating icon (.info) from image in memory?
+ Are there differences in OS 1.x, 2.x and 3.x one should be aware of
+ How do icons of different depths work? 1bp (2 colors), 2bp (4 colors), 3bp (16 colors), etc..
+ Are there different APIs (if there are any APIs at all) for disk.info vs. <file|drawer>.info icons
+ Telling WB to refresh its display/cache of a given icon when changes are made?
Stefan Blixth: @nyteshade This is just for adjusting the position on the "disk" as per se or do you mean like in an inconify way ? if you use PutDiscObject() it will according to RKRM : " As of release V2.0, PutDiskObject (if sucessful) notifies workbench has an icon has been created/modified." so that shall update the position I think without any force for redraw is needed. I know that there was some workbench-API added to 3.9 etc. that you could make "leave outs" of icons just like an cx_broker object (iconify).
Brielle Harrison: An example app I plan to write is something to organize and save the position of icons within a drawer on disk in a manner I prefer. This should be an easy way to start working with the API.
Brielle Harrison: @develin so had a chance on the train to check. It does in fact work if I omit the .info. Thanks for that. Do you happen to know how DiskObject.do_Gadget.LeftEdge and TopEdge relate to the icon? They seem to be the do_CurrentX and do_CurrentY values plus some arbitrary value. First glance seems like it’s not icon size added to the DiskObject’s x and y but I didn’t really do the math. Also it’s not clear why I wouldn’t use DrawerData’s X and Y but they seem not to be in use.