stubborn mouse?

Hi,

In a program I’m writing this occurs:

DEF PROCmouse(x%,y%,button%,window%,icon%)
IF window%=hadd% THEN
CASE icon% OF
WHEN 0,1,2,3 etc: do this
WHEN 19: addbutton%=FALSE:PROCbutton:PROCadd:PROCwrite:PROCfillarray
WHEN 20,21,22 etc: do that
ENDCASE
ENDIF
ENDPROC

DEF PROCbutton
REM Switch the state of button 19 (inverted/not inverted)
switch%=addbutton%+1:REM make a number from TRUE or FALSE
!block%=hadd%:block%!4=19
SYS “Wimp_GetIconState”,,block%
!block%=hadd%:block%!4=19
block%!8=switch%<<22:block%!12=1<<22
SYS “Wimp_SetIconState”,,block%
ENDPROC

When I run the program and click button 19, PROCmouse is visited twice, corrupting the data, but button 19 is inverted. When I leave the call PROCbutton out, the data stays OK, but button 19 is not inverted.

What am I doing wrong?

Peter

corrupting the data

What do you mean by this?

addbutton%=FALSE then switch%=addbutton%+1

Means that switch% will always be 1.
Not an answer, sorry!

I think you forgot to check what button% is. There’s probably two codes coming in, a click and a release or something like that.

You haven’t said what button type you’ve used for icon 19.
Some types can generate two clicks for the price of one as JJVDG said.

@Martin: I have a list of names and via internet I find another (which isn’t hard, haha). I want to add it to the top of the list. All the other items have to move down and they do. The corruption is that the new item comes on the second place and the last item on top.

At another place in the program addbutton%=TRUE and PROCbutton is called, to switch the button on. I need a 0 or a 1 in PROCbutton and addbutton%+1 makes a 1 from 0 and a 0 from -1. It’s a bit compact.

Reporter is pro!, thank you for that:-)

@Jan-Jaap and Jeff: it’s Click/Drag, but it should be Click only (a result of nonselective selection). I changed it and… you’re right. It gives one click now and PROCmouse is entered once. I suppose the second came from the drag.

Problem solved, Martin, Jan-Jaap and Jeff, thank you very much.

Can’t remember offhand, but shouldn’t you be checking for the button% anyway? I think your button will now also work if you press Menu over it, which is a bit weird. (And it will work for Adjust, but that’s probably OK anyway)

I could be wrong though…

You’re not, Jan-Jaap, it is still on my worklist in the catagory loose ends. But if I knew that it caused this problem, I would have done it in the first place. I understand now why this happened. Thanks!