--- In [email protected], Ilkka Lehtoranta <[EMAIL PROTECTED]> wrote:
> On Wed, 23 Mar 2005, jahc2 wrote:
> 

> It is not perfectly clear. But it seems that you modify string array 
> pointers...
> 
>    orig_str = array[0];
> 
>    /* process string here */
> 
>    array[0] = "copy this to clipboard";
>    array[1] = strlen("copy this to clipboard") + 1;
> 
> Documentation is really confusing... but try? :)
> 
> 
>    Ilkka


I was getting lockups using that attribute and copying anything to array[0] 
.... but I've decided that MUIA_NList_CopyEntryToClipHook is better for my 
needs now.. still same old problems though.


static void Custom_Clipboard_Func(REG(a0, struct Hook *hook),REG(a2, char 
**array),REG(a1, LONG **new_entry)) {


    array[0]="testing";

    if(new_entry) 
printf("new_entry[-1]:%i\nnew_entry[0]:%i\nnew_entry[1]:%i\nnew_entry[2]:%i\nnew_entry[3]:%i\nnew_entry[4]:%i\n",new_entry[-1],new_entry[0],new_entry[1],new_entry[2],new_entry[3],new_entry[4]);

}

It's sucessfully copying "testing" to the clipboard, but I want to get the 
nlist entry number in new_entry[-1].. I dont know what type to use for *a1 .. 
i've tried char, int , ULONG, LONG (while using the right format in printf) and 
it either locks up or displays information that doesnt look very correct at 
all.....

the docs seem incomplete.. I need example code..






------------------------ Yahoo! Groups Sponsor --------------------~--> 
Has someone you know been affected by illness or disease?
Network for Good is THE place to support health awareness efforts!
http://us.click.yahoo.com/Rcy2bD/UOnJAA/cosFAA/16uqlB/TM
--------------------------------------------------------------------~-> 

Visit http://www.amiga.dk/tumult for MUI-related
information, especially about MUI custom classes. 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/MUI/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 



Reply via email to