bug with multiple views and mouseaction in ruby?

[Nubeat7]

hello, just found out that the mouseLDown doesn't work with multiple view inputs - it did before FS 3.06
which is the current version i use atm and where it doesn't work.

as you can read in the userguide the mouse action methodes should work also with multiple view inputs - to use like this :

def mouseLDown i,x,y
end

where the "i" stands for the input and you could define what happens when some mouseaction happens at a specific view...

i repost the radiobutton i did a while ago which uses this technique from this thread
viewtopic.php?f=3&t=2749

if you change the output value at the mouseaction for view 0 you can see that always only the first view gets recognised, doesn't matter which view the mouseaction happens

[tulamide]

Sorry, no solution. Just a refinement. The issue seems to be somewhere else than with that method. The method does recognize different connectors. See this example. Probably somewhere behind the scenes the id isn't sent to the method anymore and the method then falls back to 0 instead of nil?

[Nubeat7]

ok here is a reduced version, if you place the "watch" methode in the 2nd view nothing gets recognised, if you place it in the first view it shows you the index, but not the name!?

i think this is a bug

[tulamide]

ok here is a reduced version, if you place the "watch" methode in the 2nd view nothing gets recognised, if you place it in the first view it shows you the index, but not the name!?

i think this is a bug

Don't get me wrong, I also think it's a bug! My answer was more for DSPr to get faster to the issue. The method works correctly, but the information DSPr feeds it with when dealing with multiple views is messed up. My guess that the method does fall back to 0 instead of handling nil (when those messed up informations come in) seems to be at least partly true (reporting 0 without a name means it is not the connector (0, "a") but some initial value or the like).

[Nubeat7]

yes something must be messed up here


another test

as you can see here when click in the second view it should show the y value but it shows the x value what should only be shown when clicking in the first view

so the input index isn't recognised correctly it seems like, as you mentioned, it is always index 0

[tulamide]

yes something must be messed up here


another test

as you can see here when click in the second view it should show the y value but it shows the x value what should only be shown when clicking in the first view

so the input index isn't recognised correctly it seems like it is always index 0

Erm...that's what I'm talking about the whole time

[Nubeat7]

luckely i didn't updated all my radio buttons to this technique (luckely i was too lazy)

are you using FS 3.08? just to know if the bug is there at the latest version because i'm using 3.06

if so could anyone who is connected to the devs report this? i never got any respond when reporting something..

[tulamide]

luckely i didn't updated all my radio buttons to this technique (luckely i was too lazy)

are you using FS 3.08? just to know if the bug is there at the latest version because i'm using 3.06

No, I'm also using 3.0.6
It also doesn't seem to be the connectors that's causing it. As you can see in the fsm below, they report their name, so it really is a messed up information when feeding the mouse methods. (Just connect the trigger button with one of the inputs)

[Nubeat7]

thx for investigating tulamide, i just tested it in fs 3.05 - there it works correct

[Nubeat7]

anyone using FS 3.08.1 could test this please, just to know if the bug is actual or not...