Stars Bet Pot AHK ?

[_dave_]

Hi Right5,

[ QUOTE ]

New Stars update completely screws up bet pot, doesn't work at all


[/ QUOTE ]

I updated to fix this Stars update issue - Update (0.01a) not fix it for you? I just tested, incase they updated again today - seems fine. Please check you have no Edit6 in the code - this was changes to Edit7 by the last update.

[ QUOTE ]

For some reason if I use the script for a while certain buttons stop fuction (eg Scroll up works but right click and scroll down don't) I have to reload the script to get it functioning properly again


[/ QUOTE ]

This indicates something is casuing the execution of a hotkey to get stuck - I can't think what may be causing this (it must be failing to exit a loop somewhere, obviously under extremely rare conditions). I'll take some time to study how this could happpen. Can you think of anything that seems to occur at a similar time to a hotkey becoming stuck?

dave.

[Right5]

[ QUOTE ]
Hi Right5,

[ QUOTE ]

New Stars update completely screws up bet pot, doesn't work at all


[/ QUOTE ]

I updated to fix this Stars update issue - Update (0.01a) not fix it for you? I just tested, incase they updated again today - seems fine. Please check you have no Edit6 in the code - this was changes to Edit7 by the last update.

[ QUOTE ]

For some reason if I use the script for a while certain buttons stop fuction (eg Scroll up works but right click and scroll down don't) I have to reload the script to get it functioning properly again


[/ QUOTE ]

This indicates something is casuing the execution of a hotkey to get stuck - I can't think what may be causing this (it must be failing to exit a loop somewhere, obviously under extremely rare conditions). I'll take some time to study how this could happpen. Can you think of anything that seems to occur at a similar time to a hotkey becoming stuck?

dave.

[/ QUOTE ]

Thanks, haven't played in a few days and didn't see the a version of the update

[patchdiaz]

[ QUOTE ]
[ QUOTE ]
Hey Dave, I have a problem with Stars preflop. I play NL25 and when I open, it gives me a raise of .95 instead of 1. 4xBB+1 limper gives me the correct raise of 1.25, but +2 limpers gives me 1.35. Then +3 works giving me the correct value of 1.75. There are also problems in both the blinds.

[/ QUOTE ]

Same problem here at 25NL. Thank you for the software and the time dave.

Best wishes.

[/ QUOTE ]

dave this update should fix the problem quoted? b/c I'm still having the same problem on Stars 25NL, ty.

Best wishes.

[_dave_]

[ QUOTE ]
[ QUOTE ]
[ QUOTE ]
Hey Dave, I have a problem with Stars preflop. I play NL25 and when I open, it gives me a raise of .95 instead of 1. 4xBB+1 limper gives me the correct raise of 1.25, but +2 limpers gives me 1.35. Then +3 works giving me the correct value of 1.75. There are also problems in both the blinds.

[/ QUOTE ]

Same problem here at 25NL. Thank you for the software and the time dave.

Best wishes.

[/ QUOTE ]

dave this update should fix the problem quoted? b/c I'm still having the same problem on Stars 25NL, ty.

Best wishes.

[/ QUOTE ]

Bah, no it doesn't [img]/images/graemlins/frown.gif[/img]

Pseudo edit: new 0.01b does fix it...

The reason being, the code I have on my own system is quite different to the 0.01 release. It is broken in parts, due to in-progress development, and is full of pop-ups, traytips & tooltips so I can follow the execution of various code sections.

In short, my current code is in no way suitable for general use.

So when Stars broke it yesterday, immediate update was needed - I just re-downloaded the 0.01 code, fixed the required lines, and put it up (therefore the 0.01a, rather than a new version number).


I just edited in the fix on overcards.com, so now there is a version 0.01b [img]/images/graemlins/smile.gif[/img]

I have not yet updated the download package with this fix, so you'll have to copy/paste the script code for now..

dave.

[patchdiaz]

ty dave is working great.

Best wishes.

[sputnik365]

Thank you, Dave.
It is working now for the first time for me, but only on hyper simple.
Default, and no images it still wants to bet 0.
Also, there is about a 5 second delay before filling in the bet amount in the box.
This is on Stars SNGs.
All the best

[PietM]

Dave,

LOOOVE your script! Works like a charm for me! I've been doing some editting of my own (to include hotkeys for folding, check/calling and such). I think you still need to put a line on top of the script to set the act_only_on_active_table variable. This one bugged me for a few days [img]/images/graemlins/smile.gif[/img]

[stoxtrader]

starting to work pretty well for me, but have two quick issues if anyone can help

1. my middle mouse button (scroll button) doesnt seem to recognize, but the wheel funtion does work. not a big problem as i changed to x and x2 as i have the mx1000 and those seem to work.

2. only my default monitor works, my second monitor causes an error - is there a spot in the script to change for this? I actually use three monitors.

[_dave_]

Hi Stoxtrader,

I was just about to reply to your PM (to ask waht mouse you have), and I refreshed here and you posted the relevant info [img]/images/graemlins/smile.gif[/img]

[ QUOTE ]

1. my middle mouse button (scroll button) doesnt seem to recognize, but the wheel funtion does work. not a big problem as i changed to x and x2 as i have the mx1000 and those seem to work.


[/ QUOTE ]

IIRC the logitech SetPoint software does something to intercept middle-button click - probably some other stuff too. I only have Microsoft mouse, so have no personal knowlegde how to sort it out, but from the memory of other posts, I think the commonly used fix is to make SetPoint map middle clicks to a function key, then edit the AHK to use the newly mapped key. Some info in this 2+2 thread, and in this AHK forum thread

There have got to be plenty MX1000 users here - any ideas?

[ QUOTE ]

2. only my default monitor works, my second monitor causes an error - is there a spot in the script to change for this? I actually use three monitors.

[/ QUOTE ]

This is known issue with Stars - It uses xy co-ords extensively, and negative co-ords cause an error [img]/images/graemlins/frown.gif[/img]

The quick fix is to make sure tour (top)left monitor is known to Windows as the "Primary Display". This makes the top left pixel 0,0 - and prevent errors caused by negative values in certain calculations used in the script.

I have an idea how this could be overcome, but I'm not sure if it woll work, so no promises - for now, set left monitor as primary and all monitors will work fine [img]/images/graemlins/smile.gif[/img]

dave.

[kidpokeher]

I have a MX1000 but don't have your script installed (yet). [img]/images/graemlins/grin.gif[/img]

Stox, take a look over here...

http://forumserver.twoplustwo.com/showfl...e=0#Post7987907