It's posible to save and load data to the cluipboard via datatypes library,and I have the simples case working fine. SketchBlock now supports copying and pasteing layers via the clipboard.
Using DTST_CLIPBOARD as source type with NewDatatypeObject allows loading from any clipboard unit. I think I have that working too.
To write to the clipboard you need the DTM_CopY method as faras I can tell. I can't see a way of specifying unit for this.
Hello,
I'm using the datatypes to load some images but something strange happens.
If I don't pass the PDTA_Screen parameter to NewDTObject when the screen is opened using an 8 bit screen nothing is blitted.. If i pass the screen pointer the image is blotted (of course it is cutter but doesn't matter)
If i use the WB screen instead all is drawn correctly even if i didn't pass the PDTA_Screen parameter.
Hello
I'm rewriting a library written for os3 and all seems ok but in the original fd file there are three functions within the #private clausole.
If i use fd2pragma that is needed to create my xml interface file those funcions are not included.
So, my question is. What are these #private functions? Are they always called using its base library?
I'm sure these are not like other static functions that are private and callable only within the library, since the program that use this library call them.
Can i safely add them to the #public part of the FD file?
M68k -> OS4-PPC glue code is easy enough to generate using fdtrans:
fdtrans -c blah_lib.sfd
But if I try to do this for a .sfd that includes definitions of WarpOS PPC functions in the jumptable it complains about the "==abi" command used in the .sfd file.
I'm guessing I will have to do them manually somehow or write a better fdtrans that can do them for me but then I need to know what kind of ABI that WarpOS uses, like is it same as OS4 but with library base in r3 instead of interface pointer or is it something completely different and if so what?
