weequ
2010-09-26 07:16:36
In ScrollMouse you can't choose wether you wan't to scroll up or down. It always scrolls up.
SRL Archive - Bugs
Scroll Mouse
Wizzup?
2010-09-26 08:18:01
Can't you give negative lines?
weequ
2010-09-26 08:31:17
From: Wizzup?I'll try.
Can't you give negative lines?
Edit: Yes! Horay =) Anyway once again the x and y parameters does not do anything.
Wizzup?
2010-09-27 18:05:21
From: antti mies
Anyway once again the x and y parameters does not do anything.
Yeah, it's silly… I'm not sure what to do just yet. :(
BenLand100
2010-09-29 22:36:04
From: Wizzup?
Yeah, it's silly… I'm not sure what to do just yet. :(
Like any other mouse event, they happen at a position. It *should* be the current position of the cursor.
weequ
2010-09-30 06:05:14
From: BenLand100Then the parameters should be removed.
Like any other mouse event, they happen at a position. It *should* be the current position of the cursor.
BenLand100
2010-09-30 13:25:54
From: antti mies
Then the parameters should be removed.
I disagree, I believe the scripter should provide the current position, just like for hold/release mouse.
weequ
2010-09-30 17:05:37
From: BenLand100Now I get your point. In that case the parameters should be made to actually move the mouse.
I disagree, I believe the scripter should provide the current position, just like for hold/release mouse.
Actually there is exactly same problem with hold/release/clickmouse. They have x and y parameters that does not do anything.
BenLand100
2010-09-30 18:45:39
From: antti mies
Now I get your point. In that case the parameters should be made to actually move the mouse.
Actually there is exactly same problem with hold/release/clickmouse. They have x and y parameters that does not do anything.
It functions exactly how it should function. I'm just thinking you don't understand the underlying functionality of the event system. The event may occur at a location that is not the location of the cursor, that will just appear as if something is "wrong" with the native system's event control. SMART enforces that events must occur at the position of the cursor by moving the cursor if it is not already there, however since the native event queue does not (and it doesn't) neither should Simba. At least, this has always been the case with this sort of thing. I believe it should at least be consistent with itself.
Wizzup?
2010-10-21 15:00:05
I'm still not sure if we should change them either. Benland is right in the sense that it is exactly how the operating system does it as well.
weequ
2010-10-30 08:54:41
From: Wizzup?Now I get it =)
I'm still not sure if we should change them either. Benland is right in the sense that it is exactly how the operating system does it as well.
It just feels like it doesn't do anything because in programs like runescape the click appears always at the mouse position. Is it different in other programs?