Fix for mouse movement problems using /mouseto and /click

Mckorr · Post by **Mckorr** » Tue May 20, 2003 10:35 pm

Top left, starting at 0,0. Very strange, your mouspos should either be 100, 100, or 50,50 if the doubling above is necessary.

It has to be a compiler setting, some difference between the VC6 and VC7 project settings.

loadingpleasewait · Post by **loadingpleasewait** » Tue May 20, 2003 10:44 pm

Ok.. well, gonna try the taking out of the /2 again, then do the /mouseto 100 100 abs test.. it shouldnt matter if mouse isnt in the top left corner, should it, if abs is used? anyways.. I will hafta test this after raid is over.. I'm thinking, if some people work at /2 and some people work without that.. maybe some other people still have a different modifier??

EDIT: Ok.. changed the code to remove the /2 s again.. had some interesting results.. it is no longer acting like its always set to relative.. absolute works now.. and on the /mouseto 100 100 abs, it puts my cursor at 300 300... so, next compile, gonna change the /2 to /3 and see if that works.. = )

EDIT: Ok, Hopefully last edit as replacing the /2 with /3 worked... Thanks for your help Mckorr

EqMule · Post by **EqMule** » Wed May 21, 2003 12:45 am

http://macroquest2.com/phpBB2/viewtopic.php?t=2308

I posted an alternative MouseTo function, which moves the mouse nicely... thanks DKAA for showing me howto port it from asm to c++ :)

Mckorr · Post by **Mckorr** » Wed May 21, 2003 8:04 am

Okay, that divider (/2 for me, /3 for loading) seems to be the problem... no idea why it appears to be different for different machines. For all I know it is related to how many lines you have your mouse wheel set to scroll :)

Glad you fixed the problem. If I get a chance I'll work in Mule's code, see how that reacts.

I've posted a change in the EQLib Development forum that should remove the necessity for having EQPath defined in macroquest.ini. That will make things a bit easier. Still have to test that.

Shark · Post by **Shark** » Wed May 21, 2003 1:40 pm

When compiled with code in CVS the mouse was going nuts, different places everytime, sometimes at edge of screen, position i wound up was not consistent, every time typed /mouseto 500 500 abs it went somewhere else. I replaced CVS mousemove code with code provided by EqMule00 and get a toggling behaviour between 2 positions when typing /mouseto 500 500 abs. The 2 positions toggled between changed when I changed number of bits in display from 32 to 16. I am running at 1024 x 768 resolution.

Positions toggle between with resolution at 1024x768x16 are 321,353 and 179,147. I am compiling with VC6 and running directx9. OS is windows XP.

Ok, after looking closer at code, reason for toggling effect is that abs and rel are backwards. When I type /mouseto 500 500 abs, it does a relative position change and vice versa. If you just type the opposite of what you want or change the code to reverse abs and rel in MouseTo it works fine without needing /2.

Mckorr · Post by **Mckorr** » Wed May 21, 2003 3:41 pm

If you replace MoveMouse with EQMule's code, replace MouseTo as well. The problem is that you are using MouseTo code that does calculations inside it, which are not done by EQMule's much shorter version and aren't required by his MoveMouse.

That's why you are seeing correct movements when you reverse abs and rel. My rel does NO calculations, just passes the arguments from /mouseto to MoveMouse.

On the other hand, my abs has to calculate based on current position, translating it into a relative movement for passing to MoveMouse.

Since EQMule's MoveMouse only deals in absolute positions, a "rel" request in my MouseTo will give you correct movements with his MoveMouse, but abs will jump around... position based on your screen resolution actually. This is similar to a problem I had when modifying NealThorpayt's code in the first place.

Try using EQMule's code for both MoveMouse and MouseTo, and the movements should be correct, assuming his code is correct (can't test it till I get home from work.)

EqMule · Post by **EqMule** » Wed May 21, 2003 3:51 pm

I just did a few hard tests on the code, and I can tell you that its totally stable, I can pick any resolution, colordepth windowed and non windowed mode, custom UI or default, eqw or not eqw, and IT WILL move the mouse to the loc specified...

Now im moving on with the parser, to see if we can get some /mouseto "bag 1" and /mouseto "right ear" and stuff like that.

Mckorr · Post by **Mckorr** » Wed May 21, 2003 3:58 pm

All those can be added in to locations.txt. I just didn't bother fleshing out that file. Good project for someone who wants to help, can scan through text files, but sucks at coding.... sorta like me, but I want to switch over to Mule's mouse code for testing, and integrate the code that finds your EQ path without having to specify it in macroquest.ini.

If Mule's MouseTo and MoveMouse work out, I'll fix MouseTo so you can /mouseto auto and stuff like that.

Digitalxero · Post by **Digitalxero** » Sat Aug 16, 2003 6:34 am

FYI the reason you have diffrent divisable variables is due to the mouse speed setting. The EQ client I think has 1 = 1to1 ratio 2 = 2to1 3 = 3to1 ect. Dont remember how many speed settings EQ has though, so you just need to set it to what ever your EQ mouse speed is set to. Which is

MousePointerSpeedMod=3

in the eqclient.ini

So figure out how to pull that info from memory and then you should be able to make it use the correct setting with out people changing the code ;p

Fix for mouse movement problems using /mouseto and /click

well...