Can someone please post examples for Pressed-Key & RDo?

Shifrin · 4 Jun 2005

infuzion wrote: Also, RDo doesn't seem to act the way I'm used to LDo working. Might help if there was a RUp... Plus RDo doesn't seem to caputure when LDo is working, or maybe just for me? :/

I'd like a RUp too, basically any functionality with LMB I'd like to have for RMB. On the issue of RDo not being captured when LDo is working, I think this is by design - at the moment. I had a similar problem with XDrag not working while YDrag had focus and it was also not possible to change the focus from YDrag to XDrag while YDrag was working.

I'm sure malc will get this stuff sorted 😉

Shif.

Tom7777 · 4 Jun 2005

I think that the R Mouse modules being able to work at the same time and L is a good idea.

i might be wrong but shouldn't this post be in the Ideas and Requests area as this area should be for sharing .osm examples or can we ask for examples too?

As for Shift to replace Ctrl it works fine for me so im not sure whats happening, you might want to type SHIFT in caps if its lowers then it wont work. Hope this helps

Hopefully these new modules and fixes will be added soon 🙂

infuzion · 4 Jun 2005

Shifrin wrote: ...On the issue of RDo not being captured when LDo is working, I think this is by design - at the moment.

yea, I'm trying to see if I'm doing something wrong in trying to capture RDo, & trying to decide if it's a bug, or a Windows's thing.

Tom7777 wrote: As for Shift to replace Ctrl it works fine for me so im not sure whats happening, you might want to type SHIFT in caps if its lowers then it wont work.

For me, I can use the (I think malc's) example in using the CTRL Capture to modify say the scale rate of a Drag just fine. But when I connect a Out to the Out of my CTRL-Capture module, I don't see any value change when I press CTRL. I can see the results of pressing CTRL clearly; I'll have slower change in values of said slider. But I can't make Capture do any thing else :/

Just seeing if I found a bug or don't know how to use it. cheers

malc · 4 Jun 2005

Hi infuzion,

First, the Mouse R-Button Down should work together with the Left one. However as Shif says, the Accumulate components currently capture the mouse messages so if you have one of these involved as well then it may be having an effect.

I have the issue of the Accumulate capture on my todo list. In the meantime if you make sure that an Accumulate is always on the first link from a Mouse Area and any other mouse components are on later links then the other components will handle the mouse messages first before passing them on to the Accumulate (components higher in the link order are always considered 'on-top' from a drawing perspective).

We will have a R-Button Up too at some point also.

The Is Key Pressed does not send a trigger ie. when you press a key nothing get's informed. The purpose of the component is to allow you to investigate the state of a key. So if you link it to another component that component will ask the Is key Pressed when it needs to know it's state but the Is key Pressed will never tell the other component when it changes. This is the way it's supposed to behave.

We'll have other components for handling key up and down events in the not so distance future. For now you can use Tom's workaround of linking a Ticker 25 to the input of the Is key Pressed and this will force a trigger when the state of the key changes.

Let me know if you need any more info.