DeMonster (New AHK Script) - Page 8

jukofyork · #71 08-25-2006, 06:18 PM

I just took a look at the AR code to see what I was using instead of WinClose and/or SendInput and have translated the calls into AHK code:

; Press ESC.
PostMessage, 0x0100, 0x1b ; 0x0100=WM_KEYDOWN, 0x1b=VK_ESC
PostMessage, 0x0101, 0x1b ; 0x0101=WM_KEYUP, 0x1b=VK_ESC

; Press ENTER.
PostMessage, 0x0100, 0x0d ; 0x0100=WM_KEYDOWN, 0x1b=VK_RETURN
PostMessage, 0x0101, 0x0d ; 0x0100=WM_KEYUP, 0x1b=VK_RETURN

Using these I've never yet seen it not close/auto-confirm a window, but using WinClose it seems to regularly mess up for me and failed to close the windows.

These calls should also work to help SafeMine and my Pacific anti-spam scripts too.

If you need to send any other keys via post message, then this page should be helpful.

Juk [img]/images/graemlins/smile.gif[/img]

Tk79 · #72 08-25-2006, 06:25 PM

When the first version came out it worked perfectly for me. Now when I use it it will leave the monster total on one table if I open 12. The other 11 close like before.

okayplayer · #73 08-25-2006, 09:04 PM

This works well to replace Auto Resizer, except that when I click "Sit Out" (like when I am finishing a session) when the blinds get to me again, it re-auto-posts it. Is there a way to fix this? It didn't do it on Auto-Resizer...

Thanks
OKP

APerfect10 · #74 08-25-2006, 11:46 PM

[ QUOTE ]
Using these I've never yet seen it not close/auto-confirm a window, but using WinClose it seems to regularly mess up for me and failed to close the windows.

[/ QUOTE ]

WinClose is a rather forceful way to close windows but it isnt perfect as you noted. Your method is noted in the WinClose docs. With that said, I've never encountered a problem with WinClose running this script. If it becomes a regular problem, I'll change it. Are you having a problem with WinClose in the DeMonster script?

[ QUOTE ]
When the first version came out it worked perfectly for me. Now when I use it it will leave the monster total on one table if I open 12. The other 11 close like before.

[/ QUOTE ]

I've been messing around with the code a lot these past few days and even made some major changes today. As of last night it worked fine for me but this latest release may have broken this. I'm going to take a look and see whats going on. I'll let you know once I can confirm and fix this bug.

[ QUOTE ]
This works well to replace Auto Resizer, except that when I click "Sit Out" (like when I am finishing a session) when the blinds get to me again, it re-auto-posts it. Is there a way to fix this? It didn't do it on Auto-Resizer...

[/ QUOTE ]

I think I understand what you are saying. You are not really clicking "Sit Out". If you click "Sit Out" Party will deal you out and you dont have the option to post blinds therefore DeMonster can't repost. I think you mean when you uncheck "Auto Post Blinds" in preparation of sitting out, playing your last few hands before the blinds hit. In this case, DeMonster will repost the Big Blind.

Here's the issue...when you first join a table and lets say the very first hand you sit down you are directly in the Big Blind. Auto-resizer would not post this blind for you. You would need to manually click the Post Big Blind button. I wanted to make it so it would auto do this. The problem is that the script can not differentiate between whether you are first sitting down, returning, or playing your last hands before the blinds hit. (I didnt think about this latter scenario and I agree something needs to be done)

Just off the top of my head; I'll think about this further but...I think I could make a Hotkey that would toggle the auto-post feature. When you are ready to call it quits, you hit whatever Hotkey you define and DeMonster will no longer post the blinds. I could then either auto detect when you are sitting out on all tables and toggle the auto post option back to its original state or I could create a second hotkey to return.

Sorry to ramble...I'll try to get a workaround out here shortly for you [img]/images/graemlins/smile.gif[/img]

APerfect10 · #75 08-26-2006, 12:25 AM

[ QUOTE ]

When the first version came out it worked perfectly for me. Now when I use it it will leave the monster total on one table if I open 12. The other 11 close like before.

[/ QUOTE ]

I've just tried replicating this problem and I cant duplicate it. Does it always leave the 12th table monster total running or was this a one time occurance. It may have been just a coincidence that it was the last table. Was it pinned and not hidden? Or was it not pinned and not hidden?

APerfect10 · #76 08-26-2006, 12:27 AM

[ QUOTE ]
Hmmm for some reason now if I run DeMonster before opening the party client it doesn't pin the sliding jackpot. If I open the client first and then run DeMonster it's fine. That wasn't the case before if I am not mistaken.

[/ QUOTE ]

Try startin DeMonster and opening the Party client and let me know if it still isnt working. Was this for one table or multiple tables?

APerfect10 · #77 08-26-2006, 12:44 AM

Anyone having issues with v1.1.0 not pinning & hiding some monster jackpots...download the latest version and please test and let me know if this solves the problem.

Jeff W · #78 08-26-2006, 01:06 AM

[ QUOTE ]
No. Version 1.1.0 still is DeMonster. It'll do all the same things that your current/old DeMonster scripts do but it now eliminate other annoyances.

[/ QUOTE ]

Awesome update. Any chance you could add a feature to automatically obscure the balance in the Party cashier? There is a Java program out there that does it but it's not open source so I can't risk using it.

MilkMan · #79 08-26-2006, 01:43 AM

[ QUOTE ]
[ QUOTE ]
Hmmm for some reason now if I run DeMonster before opening the party client it doesn't pin the sliding jackpot. If I open the client first and then run DeMonster it's fine. That wasn't the case before if I am not mistaken.

[/ QUOTE ]

Try startin DeMonster and opening the Party client and let me know if it still isnt working. Was this for one table or multiple tables?

[/ QUOTE ]

AP10 - seems fine now, sorry maybe it was something on my end. Very nice script.

Tk79 · #80 08-26-2006, 02:15 AM

[ QUOTE ]
[ QUOTE ]

When the first version came out it worked perfectly for me. Now when I use it it will leave the monster total on one table if I open 12. The other 11 close like before.

[/ QUOTE ]

I've just tried replicating this problem and I cant duplicate it. Does it always leave the 12th table monster total running or was this a one time occurance. It may have been just a coincidence that it was the last table. Was it pinned and not hidden? Or was it not pinned and not hidden?

[/ QUOTE ]

I havent played on party since the new update but I did have idlemine running and upon coming home I currently have 2 tables with the monster thing still there and not pinned. It doesnt happen to the 12th table all the time I dont think. I think its randomly missing tables.

Is the script from a previous version still posted anywhere? I like the new features but dont really need them. Id be happy to go back to the way it was if possible for now.

Let me konw if there's anything else I can do to narrow down the problem.

NOTE: hope that was legible. Im not sober.
NOTE2: I think they should start airing reruns of the wonder years.