tradeskill macros without mouse commands?

Help section from before the user variable changes that broke all macros

Moderator: MacroQuest Developers

Clawed
a ghoul
a ghoul
Posts: 105
Joined: Mon Jan 20, 2003 6:17 am

Post by Clawed » Thu May 01, 2003 1:08 am

why not require the default skin, at least for now?
It is trivial to find the currently used skin and parse the file. No reason at all to rely on default UI.
What if it just becomes good script coding practice to close windows that might open over other windows
This will probably be the case.
I think you can lock windows so they can't be moved around (or am I high?) with a key sequence in the game
Not sure on that, but I'd imagine it would also become good scripting practice to just setup your windows, wait for "saved" and run the script, without moving the windows during execution.
Clawed

Mckorr
Developer
Developer
Posts: 2326
Joined: Fri Oct 18, 2002 1:16 pm
Location: Texas

Post by Mckorr » Thu May 01, 2003 9:07 am

There's no need for a default skin, or a macroquest skin, etc. It's just a couple extra lines of code to use a custom skin instead of the default, and we have to parse the file where the custom skin name is found anyway.

Yes, you will have to make sure windows don't overlap before you run your click using macros. That's pretty much always been the case. I certainly don't want to tackle code that will discriminate between overlapping coordinates. Major pain.

As currently proposed you will have to do as Clawed says. Set up your windows so they don't overlap. Wait for the character to be saved (you get a message, just takes a few moments and some patience), then execute the macro. If you are in a hurry... well, this isn't supposed to be an uber plat machine, it's just supposed to alleviate problems caused by repetative clicking. Some of us have arthritis :)

Clawed, I missed one thing. The UI.ini file contains base XY for multiple screen resolutions. Need to include a bit in our parser that finds the current screen resolution so that we use the correct base XY.