New Tradeskill UI Problems

Need some help with that macro you're working on or aren't quite sure how to get your macro to do something? Ask here!

Moderator: MacroQuest Developers

Chummer
orc pawn
orc pawn
Posts: 24
Joined: Fri Mar 12, 2004 1:58 am

New Tradeskill UI Problems

Post by Chummer » Sat Mar 13, 2004 1:56 am

I have been trying to develop a macro that will allow me to make a Jar of Clockwork Grease. The main issue I am having now is being able to open and use an Environmental container with the new UI. As of now, i can use the /click command to get it open, but would also like a way to get into experimental mode. In normal containers this can be done with Control-R-Rightclick. In the Case of Environmental containers this does not work.

One of my thoughts would be a request that more functionality be given to the /click command in MQ2 itself. (ie: /click left enviro experiment) much like the current functionality to click on particular bag slots and buttons.

Please if you have any other suggestions or code samples that can help with this, i would love to hear them.

Dulapore
a lesser mummy
a lesser mummy
Posts: 67
Joined: Thu Feb 26, 2004 4:39 am

Post by Dulapore » Sat Mar 13, 2004 11:30 am

Try

Code: Select all

/notify tradeskillwnd ExperimentButton leftmouse

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

Post by Mckorr » Sat Mar 13, 2004 12:36 pm

/click is, and has always been, a bit buggy. I'm working on the new mouse code, I'm just very busy right now.

/notify is the way to go. Eventually most of /click will just be a dumbed down version of /notify, basically parsing /click syntax into /notify syntax in most cases.

locations.txt will disappear at the same time as it is translated to a new structure inside the source code itself.

Chummer
orc pawn
orc pawn
Posts: 24
Joined: Fri Mar 12, 2004 1:58 am

Post by Chummer » Sat Mar 13, 2004 11:31 pm

Okay, the /notify suggestion worked, yay!

There are a few new problems i have encountered when trying to get this macro finnished up that I could use some help on.

1) Ive had to add some delay with the /delay command in some places to get some of the commands such as /notify in order for them to work properly. Is this something to be expected? Is this a result of lag that these delays are needed? It works fine as it is, however i was just curious about this.

2) Part of this macro requires that a container, which is fashioned in the prior combines, be used to make a final combine. I have been unable to make it so i can find this container and open the bag to do the final combine. I have tried the following command but all i got was crashed to desktop:

Code: Select all

/itemnotify "@Container" rightmouseup
Container was set to "pack3" in previous code. /click just doesnt seem like the correct function either.

3) Taken from the manual:
/finditem [similar] "itemname"
Finds an item in your inventory by name. /finditem will open a pack, click the item, and then close the pack if it was already closed.
Using similar triggers a search for substrings in <"itemname">
If there was an item on the cursor, $getlasterror is set to FIND_HANDSFULL
If it was unable to open a pack, $getlasterror is set to FIND_PACKNOTOPEN
If the item wasn't found, $getlasterror is set to FIND_NOTFOUND
/finditem does not seem to be working as described in bold. If no bags are open before this command is run in the macro, the macro seems to lock into some kind of infinite loop that i am unable to break out of. Is there a break command for any macro in MQ2 like a Control-Q or something? /finditem only seems to work properly if the bags containing the items are initially open.


I am very close to completing this macro and would appreciate any helpful hints or suggestions. Thank you.

Chummer
orc pawn
orc pawn
Posts: 24
Joined: Fri Mar 12, 2004 1:58 am

Post by Chummer » Mon Mar 15, 2004 1:49 am

Okay, i got it to open the container fine now using a /click command.

One final detail im still working on is what to do with the final product. I dont want to /autoinv because it will put it in the slot where the next container will need to go in the next iteration. Im trying to figure out a way for it to put it in the first free slot that is inside a bag so i can set up the macro to run till out of supplies instead of just one iteration. The most obvious solution is to just make it click on a slot in a bag after it makes the final product, but I was hoping to find a more general solution.

Again, any suggestions are appreciated here.