🚀 go-pugleaf

johnv@tower.actrix.gen.nz (John Veldthuis) writes:
>Quoted from <3735@orbit.cts.com> by koleman@pnet51.orb.mn.org (Kurt Koller):
>
>[stuff deleted]
>
>>  
>> And for the second question...
>>  
>> I have this:
>>                 movea.l (KWPtr),a0              ;Pointer to window's user
>>                 movea.l (wd_UserPort,a0),a0     ;  port goes in a0
>
>Make sure that d1 has been zeroed as only the lower 8 bits are effected by
>this instruction and old data may be still in there
>add a moveq #0,d1 to zero out d1
>
 
Yes, this WAS the problem.  After I dragged my handy debugger out and took a
look at what was happening, d2 and d3 had trash in them.  After I zero'd them,
everything was fine.  I then changed the whole thing to 1 call, LoadRGB4().
>>                 move.b  (MP_SIGBIT,a0),d1       ;window's signal bits
>>                 moveq.l #1,d0                   ;Convert bit number in mask
>>                 lsl.l   d1,d0                   ;  and place result in d0
>>                 SYSCALL Wait                    ;Wait for closegadget
>>  
>>  
>> And I'm waiting for a MENUPICK.  This is the only thing I am waiting for, not
>> a closegadget.  It used to be a closegadget.  Anyhow, what do I do next?  All
>> of the RKM examples on this are in C, and I am having a difficult time with
>> this one.  CAn someone maybe mail me an example of how to figure out what
>> menuitem was chosen, etc?  MAybe mail me an example (in assembly, please)...
>
>Once the Wait call returns you have to call GetMsg() untill it returns a
>NULL and process each of these messages.
>--
>*** John Veldthuis, NZAmigaUG.         johnv@tower.actrix.gen.nz       ***

Thanks
Kurt "Koleman" Koller
UUCP: {crash tcnet}!orbit!pnet51!koleman
INET: koleman@pnet51.orb.mn.org