Results 1 to 5 of 5

Thread: TBox not being clicked.

  1. #1
    Join Date
    Jun 2012
    Posts
    122
    Mentioned
    0 Post(s)
    Quoted
    40 Post(s)

    Question TBox not being clicked.

    I wrote this procedure that find a gem and tries to cut it. It finds the gem using a DTM then fails to click on cut.

    Code:
    cutBox : TBox;
    Code:
      if(findDTM(dtm, x, y, tabBackPack.getBounds()))
      then begin
        mouse(x, y, 5, 5, MOUSE_LEFT);
    
        wait(2000);
    
        cutBox := intToBox(436, 597, 565, 615);
    
        mouseBox(cutBox, MOUSE_LEFT);
      end;



    I tried changing the coords for the TBox, but that didn't work. How do I solve this?

  2. #2
    Join Date
    Jun 2007
    Location
    The land of the long white cloud.
    Posts
    3,702
    Mentioned
    261 Post(s)
    Quoted
    2006 Post(s)

    Default

    Simba Code:
    if productionScreen.isOpen(3000) then
    begin
      productionScreen.selectBox(3); //whatever box
      productionScreen.clickStart(); //click start

      if progressScreen.isOpen(2000) then
      repeat
        wait(100);
        //antiBan        //wait until cancel button is no longer up
      until progressScreen.getButton() <> PROGRESS_BUTTON_CANCEL;

    end;

  3. #3
    Join Date
    Jun 2012
    Posts
    122
    Mentioned
    0 Post(s)
    Quoted
    40 Post(s)

    Default

    Quote Originally Posted by The Mayor View Post
    Simba Code:
     
    Thank you.

    Let me ask you a related question. I saw you have an uncut gem DTM

    Code:
    'm1gAAAHic42JgYNjExMCwDYhXAvESJgh/JxTvAuLVUDkuIGYGYkYg5gZiMSDmBWJRIBaB0iBcISEINJUJB2aEs/8zEAcYicQIAABXaglk'
    You used that in your Miner script to represent at least 3 types of gems, emerald, ruby, and saphire. How did you create that? I find it very useful to not have to have one DTM per gem color when dealing with the already cut gem.

  4. #4
    Join Date
    Jun 2007
    Location
    The land of the long white cloud.
    Posts
    3,702
    Mentioned
    261 Post(s)
    Quoted
    2006 Post(s)

    Default

    Quote Originally Posted by KLight View Post
    Thank you.

    Let me ask you a related question. I saw you have an uncut gem DTM

    Code:
    'm1gAAAHic42JgYNjExMCwDYhXAvESJgh/JxTvAuLVUDkuIGYGYkYg5gZiMSDmBWJRIBaB0iBcISEINJUJB2aEs/8zEAcYicQIAABXaglk'
    You used that in your Miner script to represent at least 3 types of gems, emerald, ruby, and saphire. How did you create that? I find it very useful to not have to have one DTM per gem color when dealing with the already cut gem.
    Pick the midpoint with a tolerance of 255 (max tolerance so it can be any colour) + the normal black outline.

  5. #5
    Join Date
    Jun 2012
    Posts
    122
    Mentioned
    0 Post(s)
    Quoted
    40 Post(s)

    Default

    Quote Originally Posted by The Mayor View Post
    Pick the midpoint with a tolerance of 255 (max tolerance so it can be any colour) + the normal black outline.
    That's really smart. It worked perfectly. Thank you. I wish I could give you more reputation.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •