MacroQuest64

Plazmic wrote:It's not so much a problem of getting /click to work, it's getting /click to work how I want it to.
In the old UI, MQ told EQ a click was done at x,y and that was it.
In the new UI, MQ will (read, by Sunday... work is hell right now) completely bypass clicks...
So instead of "I clicked pack 2 open, then click slot 1" it will be "I picked up the item in pack 2 slot 1 to the cursor"
Instead of "I clicked the autoequip area" it will be "I'm autoequiping this item"

Maybe I'm missing something...

Shouldn't having a functional system for clicks be the top priority, then move away from the click at x,y scheme?

I'm not trying to be critical. I love MQ (and regularly use the non-click functions). I just think getting a functional version for the actaual macroing or, barring that, finding some way to go back to OldUI should come first, before the fancier things.

-Gooberball

Actually, Plaz's idea of skipping clicks for most things is probably a better option... but for things like buy/sell/combine buttons, will probably need /click function eventually...

It's going to be backwards compatible..
"/click left pack 1 combine" will just be handled internally in a different manner.

Great work. I'm really glad to hear you're making such good progress.

I was wondering if it would also be possible to have a different click command which would just generate a dinput mouse click (like /dclick or something). It could just send a mouse down/up at the current mouse position. This would be useful when you're not dealing with a known object and just need to click somewhere on the screen. Something like:

/mouseto 300 200
/dclick left
/mouseto 400 100
/dclick right
...


Thanks a lot for working on the update!

.. there is. and it does.

/mouseto loc 300 300 (or is it /mouseto 300 300) works

and the old click DOES click on the viewport where the game is played, just not on the Overlay panel