Re: mouseDown and within
Alex, Thanks for responding. I spent all day trying things out but now I need a break. I am going out to eat and tonight or tomorrow I will revisit your code. It looks interesting. So far, I have a hover solution. I also have a mouse down and up while the mouse is down that sends messages to the button I am over even though real up and downs won't be sent. Pretty cool. But my real goal is to fix the way I think it should be and I will share what I get when I am done. Thanks for all the help, Tom On Apr 23, 2005, at 4:34 PM, Alex Tweedly wrote: Thomas, I haven't had good email access for the last few days, so I hadn't been following this thread closely - so I may have missed a problem described earlier, but your description of the PDA interactions required seemed straightforward (and I didn't like the sound of debugging time-related or race conditions), so I thought I'd try it from scratch. The following script does what I think you want :-), with no hilites left behind or other issues. ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: mouseDown and within
Thomas McGrath III wrote: Hey Eric and others, HELP, I am so damn close. With the adjusted script below I can pretend to trap a mouseUp even though the actual mouseUp handler in my script doesn't receive it. (This is because of the mouseDown issue "bug", sort of, at least to me it is!). Any way the check if the mouse is up works over the new control at present and I get to hear the "mouse up" which will be replaced later with my necessary code. The problem now comes down to one thing. 1. The highlights don't always un-highlight and seems to be a time related thing. I tried 50 ms, 10 ms, 1 ms, and 5 ms - If I move the mouse around in the down state I end up with a trail of highlighted buttons left behind. Not all of them and some times it seems like the same ones but I can't prove that. Thomas, I haven't had good email access for the last few days, so I hadn't been following this thread closely - so I may have missed a problem described earlier, but your description of the PDA interactions required seemed straightforward (and I didn't like the sound of debugging time-related or race conditions), so I thought I'd try it from scratch. The following script does what I think you want :-), with no hilites left behind or other issues. Notes: 1. I created four buttons (B1,B2,B3,B4), and set the "auto-hilite" of each to false (otherwise the hilite is unhelpfully removed for you when the mouse leaves the initial button) 2. I put all four buttons within a group - and put all the code below in the *group*'s script. 3. It assumes that you start off with "theOne" set to empty; this will be the case in production use (because it always sets it to empty on mouseUp/Release - but beware that in development (e.g. if a script stops with an error), you'll need to tidy that up before restarting the script. I added an extra button (tidy) to the group and the script, and did this tidying up in there. 4. I left in some of the debugging - lines like put "A" && . where the initial letter let's me know which line is doing it ... global theKeys, theOne on mouseDown -- tidy up - for development use only if the short name of the mouseControl = "Tidy" then put "B1,B2,B3,B4" into theKeys-- should be elsewhere !! put empty into theOne exit mouseDown end if put the short name of the mouseControl into theOne set the hilite of button theOne to true end mouseDown on mouseMove x,y if theOne is empty then exit mouseMove repeat for each item B in theKeys if the mouseloc is within the rect of button B then if theOne <> B then if theOne is not empty then set the hilite of button theOne to false -- put "A" && theOne && "false" & cr after msg end if put B into theOne put B & Cr after msg-- or into a field to display set the hilight of button B to true --put "B" && theOne && "true" & cr after msg end if else if B <> theOne then if the hilite of button B then put B & Cr after msg set the hilight of button B to false -- put "C" && theOne && "false" & cr after msg end if end if end if end repeat end mouseMove on mouseUp if theOne is not empty then set the hilite of button theOne to false if the mouseloc is within the rect of group id 1076then put "mouseUp select " && theOne & cr after msg put empty into theOne end if end mouseUp on mouseRelease if theOne is not empty then set the hilite of button theOne to false if the mouseloc is within the rect of group id 1076 then put "mouseRelease select " && theOne & cr after msg put empty into theOne end if end mouseRelease -- Alex Tweedly http://www.tweedly.net No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.10.2 - Release Date: 21/04/2005 ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: mouseDown and within
sez [EMAIL PROTECTED] >Thanks, this is one of the ways I have been trying. Two things are >wrong: >1. If the mouse is down then messages are still sent to the original >control that took the mouseDown and it tries to highlight >2. This only highlights the button or sets the color to blue when moved >within it but after leaving it leaves behind the blue. >I might have to stick with the Hover approach using the within message. >But our Director guy was able to do it in Director and since I am >duplicating that work in Rev it is a shame I won't be able to. I will >have to explain that Rev just can't do it. What about rolling your own messages? You could do a send-in-time loop which checks where the mouseLoc is, and triggers appropriate behavior for whichever locations? ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: mouseDown and within
Eric, I just posted another response before I saw this one. In the other the mouse up is faked a little bit. Tom On Apr 23, 2005, at 12:21 PM, Eric Chatonet wrote: Hi Tom, Could not you send the mouseUp message by yourself? ;-) Simplified here: on CheckOtherButtons repeat with i = 1 to the number of btns if the mouse is down then set the hilite of btn i to the mouseLoc is within the rect of btn i else if the mouseLoc is within the rect of btn i then set the hilite of btn i to false send mouseUp to btn i exit CheckOtherButtons end if end if end repeat send "CheckOtherButtons" to me in 50 milliseconds end CheckOtherButtons Best regards from Paris, Le 23 avr. 05, à 18:02, Thomas McGrath III a écrit : So here is what I have so far (adapted to my needs of course). AND it works. Sort of. The problem is still two fold: 1. If I release the mouse over another acceptable control there is no mouseUp sent to it since the mouseDown doesn't want to. This is the same in a mouseMove. Amicalement, Eric Chatonet. So Smart Software For institutions, companies and associations Built-to-order applications: management, multimedia, internet, etc. Windows, Mac OS and Linux... With the French touch Web sitehttp://www.sosmartsoftware.com/ Email [EMAIL PROTECTED]/ Phone 33 (0)1 43 31 77 62 Mobile 33 (0)6 20 74 50 86 ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution Thomas J. McGrath III SCS 1000 Killarney Dr. Pittsburgh, PA 15234 412-885-8541 ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: mouseDown and within
Hey Eric and others, HELP, I am so damn close. With the adjusted script below I can pretend to trap a mouseUp even though the actual mouseUp handler in my script doesn't receive it. (This is because of the mouseDown issue "bug", sort of, at least to me it is!). Any way the check if the mouse is up works over the new control at present and I get to hear the "mouse up" which will be replaced later with my necessary code. The problem now comes down to one thing. 1. The highlights don't always un-highlight and seems to be a time related thing. I tried 50 ms, 10 ms, 1 ms, and 5 ms - If I move the mouse around in the down state I end up with a trail of highlighted buttons left behind. Not all of them and some times it seems like the same ones but I can't prove that. on mouseDown global theKeys, thecheck if the short name of the target is among the lines of theKeys then -- if "button" is in the target then CheckOtherButtons -- ∆ end if end mouseDown --- on CheckOtherButtons global theKeys, thecheck if the mouse is up then set the hilite of btn thecheck to false revspeak "mouse up" && thecheck put "" into thecheck exit CheckOtherButtons end if if thecheck is not empty then set the hilite of btn thecheck to false end if repeat for each line i in theKeys --with i = 1 to the number of btns if the mouseLoc is within the rect of btn i then set the hilite of btn i to true put i into thecheck cPreviewKey i end if end repeat send "CheckOtherButtons" to me in 5 milliseconds -- 50 end CheckOtherButtons ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: mouseDown and within
Hi Tom, Could not you send the mouseUp message by yourself? ;-) Simplified here: on CheckOtherButtons repeat with i = 1 to the number of btns if the mouse is down then set the hilite of btn i to the mouseLoc is within the rect of btn i else if the mouseLoc is within the rect of btn i then set the hilite of btn i to false send mouseUp to btn i exit CheckOtherButtons end if end if end repeat send "CheckOtherButtons" to me in 50 milliseconds end CheckOtherButtons Best regards from Paris, Le 23 avr. 05, à 18:02, Thomas McGrath III a écrit : So here is what I have so far (adapted to my needs of course). AND it works. Sort of. The problem is still two fold: 1. If I release the mouse over another acceptable control there is no mouseUp sent to it since the mouseDown doesn't want to. This is the same in a mouseMove. Amicalement, Eric Chatonet. So Smart Software For institutions, companies and associations Built-to-order applications: management, multimedia, internet, etc. Windows, Mac OS and Linux... With the French touch Web sitehttp://www.sosmartsoftware.com/ Email [EMAIL PROTECTED]/ Phone 33 (0)1 43 31 77 62 Mobile 33 (0)6 20 74 50 86 ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: mouseDown and within
Eric, Thanks, Yeah I didn't specify the PDA simulation aspect before. No apology is needed of course. I appreciate the advice always. So here is what I have so far (adapted to my needs of course). AND it works. Sort of. The problem is still two fold: 1. If I release the mouse over another acceptable control there is no mouseUp sent to it since the mouseDown doesn't want to. This is the same in a mouseMove. and 2. The script below WORKS but leaves behind highlighted keys every couple of seconds. (oh so close) (it still will not send a mouseUp to the control we are over) -- -- theKeys - holds my list of 18 acceptable buttons and the script is in the card -- thecheck - I hope holds the last button that was highlighted on mouseDown global theKeys if the short name of the target is among the lines of theKeys then -- if "button" is in the target then CheckOtherButtons -- ∆ end if end mouseDown --- on CheckOtherButtons global theKeys, thecheck if the mouse is up then exit CheckOtherButtons if thecheck is not empty then -- hopefully each 50 milliseconds this un-highlights the last key if there is one set the hilite of btn thecheck to false end if repeat for each line i in theKeys -- with i = 1 to the number of btns if the mouseLoc is within the rect of btn i then set the hilite of btn i to true put i into thecheck end if end repeat send "CheckOtherButtons" to me in 50 milliseconds end CheckOtherButtons Thanks I really need to get this right. Tom On Apr 23, 2005, at 11:35 AM, Eric Chatonet wrote: Hi Tom, I did not know you were working on a PDA interface: So, I apologize :-) The problem is very different indeed. ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: mouseDown and within
Hi Tom, I did not know you were working on a PDA interface: So, I apologize :-) The problem is very different indeed. I take the opportunity to say that Pat's solution seems a better approach since mousemove is an IDE "pending" message. If you want the button hilited when the mouse is down and the mouseLoc within the button rectangle, but only in this case, you could try: on mouseMove -- in the script of the card if the mouse is "down" then repeat with i = 1 to 4 set the hilite of btn i to the mouseLoc is within the rect of btn i end repeat end if end mouseMove But I don't konw if I understood correctly your problem... Best regards from Paris, Le 23 avr. 05, à 17:19, Thomas McGrath III a écrit : Eric, I tried your script for a while and it will need a bit more work to work for me. Thank you though. As far as the 'good ergonomics' , what I am trying to do in Rev works in our Director project and also works in our pda prototype. You see, on a PDA you don't have a mouseHover type of operation but instead you must place a pen on the screen in a mouseDown situation and then move the pen around in that state. If you stay for a time in one spot then a popup will show. That is normal behavior for PDAs. I think it would also be normal for touch screens. What I am doing is an offset of that concept and actually works quite well in user interface parameters. We are using a palette of 18 buttons that when you move the pen around in a penDown (simulated on the Mac as a mouseDown) that the buttons will highlight so you know you are actually over that button and if it is what you want then you release the pen - executing a penUp (simulated as a mouseUp). If it is not what you want then you move on to either another button or out of our palette and release the penUp(mouseUp) in another area. We also have a field in our palette that will display the name of the button when in the penDown (mouseDown) state within the bonds of our palette and will clear that text when leaving that button. In the end due to the operation of PDAs this behavior is intuitive and expected and we just take it a step further by giving feedback while the user is in our palette. Currently the problem I have with my scripts and the one you offer is that I can't find a way to not allow the mouseDown to send messages to the original control when I have moved on to another control. Your solution does send a message to the control we have moved over BUT it also sends a message back to the original control as well. It seems Rev wants to stick to this in at least five different messages including the mouseMove message IF the mouseDown was pressed and is still down. Thanks again Tom On Apr 23, 2005, at 7:48 AM, Eric Chatonet wrote: on mouseDown if "button" is in the target then CheckOtherButtons -- ∆ end if end mouseDown --- CheckOtherButtons But I would to turn your attention to another thing: I'm not sure such a behaviour is good ergonomics... Best regards from Paris. Amicalement, Eric Chatonet. --- Pour les institutionnels, les entreprises et les associations Des logiciels sur mesure : gestion, multimédia, internet, etc. Windows, Mac OS et Linux... Avec la "french touch" For institutions, companies and associations Built-to-order applications: management, multimedia, internet, etc. Windows, Mac OS and Linux... With the French touch --- Web site http://www.sosmartsoftware.com/ Email [EMAIL PROTECTED]/ Post 24, Bd de Port-Royal 75005 Paris Phone (33) 143 317 762 Mobile (33) 620 745 086 --- ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: mouseDown and within
Pat, Thanks, this is one of the ways I have been trying. Two things are wrong: 1. If the mouse is down then messages are still sent to the original control that took the mouseDown and it tries to highlight 2. This only highlights the button or sets the color to blue when moved within it but after leaving it leaves behind the blue. I might have to stick with the Hover approach using the within message. But our Director guy was able to do it in Director and since I am duplicating that work in Rev it is a shame I won't be able to. I will have to explain that Rev just can't do it. Thanks again to all, Tom On Apr 23, 2005, at 8:50 AM, Pat Trendler wrote: Just another thought, you can use - if the mouse is "down" for example as in the following (a bit sloppy scripting but it does work OK) on mouseMove if the mouse is "down" then repeat with i = 1 to 4 if the mouseLoc is within the rect of btn i then set the backgroundcolor of btn i to "blue" end if end repeat end if end mouseMove Correction to my previous mail I should have said you can get mouseStillDown if the handler is in the script of the target btn. Pat - Original Message - From: "Pat Trendler" <[EMAIL PROTECTED]> To: "How to use Revolution" Sent: Saturday, April 23, 2005 1:26 PM Subject: Re: mouseDown and within Tom, You can get mouseStillDown if it's in the target btn and also you can always get the mouseloc. A bit of fiddling with these two should get you what you want. HTH Pat - Original Message - From: "Thomas McGrath III" <[EMAIL PROTECTED]> To: "How to use Revolution" Sent: Saturday, April 23, 2005 11:56 AM Subject: mouseDown and within Hello all, I have a few buttons and when the mouse is down over a button the background turns blue. This is good. Now I want to have the other buttons turn blue by still holding the mouseDown but moving it over the other buttons and when it is over them that they will act like a mouseDown has been sent to them. I have tried mouseDown, mouseStillDown, mouseWithin, mouseEnter etc. No luck, I might be able to do a mouseOver (SC) but prefer the mouseDown if possible. Does anyone know a way to do this Thanks in advance Tom Thomas J. McGrath III SCS 1000 Killarney Dr. Pittsburgh, PA 15234 412-885-8541 ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution Thomas J. McGrath III SCS 1000 Killarney Dr. Pittsburgh, PA 15234 412-885-8541 ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: mouseDown and within
Eric, I tried your script for a while and it will need a bit more work to work for me. Thank you though. As far as the 'good ergonomics' , what I am trying to do in Rev works in our Director project and also works in our pda prototype. You see, on a PDA you don't have a mouseHover type of operation but instead you must place a pen on the screen in a mouseDown situation and then move the pen around in that state. If you stay for a time in one spot then a popup will show. That is normal behavior for PDAs. I think it would also be normal for touch screens. What I am doing is an offset of that concept and actually works quite well in user interface parameters. We are using a palette of 18 buttons that when you move the pen around in a penDown (simulated on the Mac as a mouseDown) that the buttons will highlight so you know you are actually over that button and if it is what you want then you release the pen - executing a penUp (simulated as a mouseUp). If it is not what you want then you move on to either another button or out of our palette and release the penUp(mouseUp) in another area. We also have a field in our palette that will display the name of the button when in the penDown (mouseDown) state within the bonds of our palette and will clear that text when leaving that button. In the end due to the operation of PDAs this behavior is intuitive and expected and we just take it a step further by giving feedback while the user is in our palette. Currently the problem I have with my scripts and the one you offer is that I can't find a way to not allow the mouseDown to send messages to the original control when I have moved on to another control. Your solution does send a message to the control we have moved over BUT it also sends a message back to the original control as well. It seems Rev wants to stick to this in at least five different messages including the mouseMove message IF the mouseDown was pressed and is still down. Thanks again Tom On Apr 23, 2005, at 7:48 AM, Eric Chatonet wrote: on mouseDown if "button" is in the target then CheckOtherButtons -- ∆ end if end mouseDown --- CheckOtherButtons But I would to turn your attention to another thing: I'm not sure such a behaviour is good ergonomics... Best regards from Paris. ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: mouseDown and within
Just another thought, you can use - if the mouse is "down" for example as in the following (a bit sloppy scripting but it does work OK) on mouseMove if the mouse is "down" then repeat with i = 1 to 4 if the mouseLoc is within the rect of btn i then set the backgroundcolor of btn i to "blue" end if end repeat end if end mouseMove Correction to my previous mail I should have said you can get mouseStillDown if the handler is in the script of the target btn. Pat - Original Message - From: "Pat Trendler" <[EMAIL PROTECTED]> To: "How to use Revolution" Sent: Saturday, April 23, 2005 1:26 PM Subject: Re: mouseDown and within Tom, You can get mouseStillDown if it's in the target btn and also you can always get the mouseloc. A bit of fiddling with these two should get you what you want. HTH Pat - Original Message - From: "Thomas McGrath III" <[EMAIL PROTECTED]> To: "How to use Revolution" Sent: Saturday, April 23, 2005 11:56 AM Subject: mouseDown and within Hello all, I have a few buttons and when the mouse is down over a button the background turns blue. This is good. Now I want to have the other buttons turn blue by still holding the mouseDown but moving it over the other buttons and when it is over them that they will act like a mouseDown has been sent to them. I have tried mouseDown, mouseStillDown, mouseWithin, mouseEnter etc. No luck, I might be able to do a mouseOver (SC) but prefer the mouseDown if possible. Does anyone know a way to do this Thanks in advance Tom Thomas J. McGrath III SCS 1000 Killarney Dr. Pittsburgh, PA 15234 412-885-8541 ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: mouseDown and within
Hi Tom, Menus are handled by the engine and unfortunately are not transcript statements :-( or :-) Something like that (non tested) in the card script: on mouseDown if "button" is in the target then CheckOtherButtons -- ∆ end if end mouseDown --- on CheckOtherButtons if the mouse is up then exit CheckOtherButtons repeat with i = 1 to the number of btns if the mouseLoc is within the rect of btn i then set the hilite of btn i to true end repeat send "CheckOtherButtons" to me in 50 milliseconds end CheckOtherButtons But I would to turn your attention to another thing: I'm not sure such a behaviour is good ergonomics... Best regards from Paris. Le 23 avr. 05, à 12:41, Thomas McGrath III a écrit : Thanks Eric, So my trapping the mouseDown message will break what I want to do while the mouse is down?!! BUT when you mouseDown on a menu and then with it still down you nav down to a sub menu it seems to still highlight text items. And the same works in paint tools where you mouseDown a tool and sub to another tool in a popup. Seems kinda the same... What kind of pending message is good for this and also is there a way to get the button to 'highlight' without a mouseDown??? Thanks again tom On Apr 23, 2005, at 4:11 AM, Eric Chatonet wrote: Hi Tom, Once the mouse is down, the engine stops sending any message until the mouse is up. Then some retroactive messages are sent (as mouseleave). You can check this in the message watcher (where mouseStillDown is not shown). So, the only way I see to do that would be using a pending message with a loop which would check other buttons status :-( Le 23 avr. 05, à 03:56, Thomas McGrath III a écrit : I have a few buttons and when the mouse is down over a button the background turns blue. This is good. Now I want to have the other buttons turn blue by still holding the mouseDown but moving it over the other buttons and when it is over them that they will act like a mouseDown has been sent to them. I have tried mouseDown, mouseStillDown, mouseWithin, mouseEnter etc. No luck, I might be able to do a mouseOver (SC) but prefer the mouseDown if possible. Amicalement, Eric Chatonet. So Smart Software For institutions, companies and associations Built-to-order applications: management, multimedia, internet, etc. Windows, Mac OS and Linux... With the French touch Web sitehttp://www.sosmartsoftware.com/ Email [EMAIL PROTECTED]/ Phone 33 (0)1 43 31 77 62 Mobile 33 (0)6 20 74 50 86 ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: mouseDown and within
Thanks Eric, So my trapping the mouseDown message will break what I want to do while the mouse is down?!! BUT when you mouseDown on a menu and then with it still down you nav down to a sub menu it seems to still highlight text items. And the same works in paint tools where you mouseDown a tool and sub to another tool in a popup. Seems kinda the same... What kind of pending message is good for this and also is there a way to get the button to 'highlight' without a mouseDown??? Thanks again tom On Apr 23, 2005, at 4:11 AM, Eric Chatonet wrote: Hi Tom, Once the mouse is down, the engine stops sending any message until the mouse is up. Then some retroactive messages are sent (as mouseleave). You can check this in the message watcher (where mouseStillDown is not shown). So, the only way I see to do that would be using a pending message with a loop which would check other buttons status :-( Le 23 avr. 05, à 03:56, Thomas McGrath III a écrit : I have a few buttons and when the mouse is down over a button the background turns blue. This is good. Now I want to have the other buttons turn blue by still holding the mouseDown but moving it over the other buttons and when it is over them that they will act like a mouseDown has been sent to them. I have tried mouseDown, mouseStillDown, mouseWithin, mouseEnter etc. No luck, I might be able to do a mouseOver (SC) but prefer the mouseDown if possible. Amicalement, Eric Chatonet. So Smart Software For institutions, companies and associations Built-to-order applications: management, multimedia, internet, etc. Windows, Mac OS and Linux... With the French touch Web sitehttp://www.sosmartsoftware.com/ Email [EMAIL PROTECTED]/ Phone 33 (0)1 43 31 77 62 Mobile 33 (0)6 20 74 50 86 ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution Thomas J. McGrath III SCS 1000 Killarney Dr. Pittsburgh, PA 15234 412-885-8541 ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: mouseDown and within
Hi Tom, Once the mouse is down, the engine stops sending any message until the mouse is up. Then some retroactive messages are sent (as mouseleave). You can check this in the message watcher (where mouseStillDown is not shown). So, the only way I see to do that would be using a pending message with a loop which would check other buttons status :-( Le 23 avr. 05, à 03:56, Thomas McGrath III a écrit : I have a few buttons and when the mouse is down over a button the background turns blue. This is good. Now I want to have the other buttons turn blue by still holding the mouseDown but moving it over the other buttons and when it is over them that they will act like a mouseDown has been sent to them. I have tried mouseDown, mouseStillDown, mouseWithin, mouseEnter etc. No luck, I might be able to do a mouseOver (SC) but prefer the mouseDown if possible. Amicalement, Eric Chatonet. So Smart Software For institutions, companies and associations Built-to-order applications: management, multimedia, internet, etc. Windows, Mac OS and Linux... With the French touch Web sitehttp://www.sosmartsoftware.com/ Email [EMAIL PROTECTED]/ Phone 33 (0)1 43 31 77 62 Mobile 33 (0)6 20 74 50 86 ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: mouseDown and within
Tom, You can get mouseStillDown if it's in the target btn and also you can always get the mouseloc. A bit of fiddling with these two should get you what you want. HTH Pat - Original Message - From: "Thomas McGrath III" <[EMAIL PROTECTED]> To: "How to use Revolution" Sent: Saturday, April 23, 2005 11:56 AM Subject: mouseDown and within Hello all, I have a few buttons and when the mouse is down over a button the background turns blue. This is good. Now I want to have the other buttons turn blue by still holding the mouseDown but moving it over the other buttons and when it is over them that they will act like a mouseDown has been sent to them. I have tried mouseDown, mouseStillDown, mouseWithin, mouseEnter etc. No luck, I might be able to do a mouseOver (SC) but prefer the mouseDown if possible. Does anyone know a way to do this Thanks in advance Tom Thomas J. McGrath III SCS 1000 Killarney Dr. Pittsburgh, PA 15234 412-885-8541 ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: mouseDown and within
It seems that ever possible message PREVENTS the possibility of a mouseDown moving from one control to another and initiating the mouseDown on that without first releasing the mouse. Most programs at least will let you float a mouse cursor over items and hover to display a tooltip. What I want to do is the same thing but with a mouseDown state. It seems I can't do a Hover or a mouseDown in Rev. HELP From the docs mouseEnter If the mouse button is down when the mouse pointer enters the control, no mouseEnter message is sent unless the mouse button is released while the pointer is still in the control. mouseWithin If the mouse button is down when the mouse pointer enters the control, no mouseWithin messages are sent until the mouse button is released. If the mouse pointer leaves the control while the mouse button is still down, no mouseWithin messages are sent. If the mouse button is pressed while the pointer is in the control, however, mouseWithin messages continue to be sent, even while the mouse button is down. Usually, it is easier and more efficient to use the mouseMove message to track the movement of the mouse while the button is being held down. mouseStillDown The mouseStillDown message is sent to the control that was originally clicked, or to the card if no control was under the mouse pointer. mouseMove If the mouse button is down, the mouseMove message continues to be sent to the object that was clicked, even if the mouse pointer moves outside that object. mouseLeave If the mouse button is down when the mouse pointer leaves the control, the mouseLeave message is not sent until the mouse button is released. Tom On Apr 22, 2005, at 9:56 PM, Thomas McGrath III wrote: Hello all, I have a few buttons and when the mouse is down over a button the background turns blue. This is good. Now I want to have the other buttons turn blue by still holding the mouseDown but moving it over the other buttons and when it is over them that they will act like a mouseDown has been sent to them. I have tried mouseDown, mouseStillDown, mouseWithin, mouseEnter etc. No luck, I might be able to do a mouseOver (SC) but prefer the mouseDown if possible. Does anyone know a way to do this Thanks in advance Tom Thomas J. McGrath III SCS 1000 Killarney Dr. Pittsburgh, PA 15234 412-885-8541 ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution Thomas J. McGrath III SCS 1000 Killarney Dr. Pittsburgh, PA 15234 412-885-8541 ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
mouseDown and within
Hello all, I have a few buttons and when the mouse is down over a button the background turns blue. This is good. Now I want to have the other buttons turn blue by still holding the mouseDown but moving it over the other buttons and when it is over them that they will act like a mouseDown has been sent to them. I have tried mouseDown, mouseStillDown, mouseWithin, mouseEnter etc. No luck, I might be able to do a mouseOver (SC) but prefer the mouseDown if possible. Does anyone know a way to do this Thanks in advance Tom Thomas J. McGrath III SCS 1000 Killarney Dr. Pittsburgh, PA 15234 412-885-8541 ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
