Quote:
Originally Posted by Ponder
The fact that table in fore ground table under mouse jump mouse to table and bring to foreground are mutually exclusive makes this program lose alot of its steam imo.
Its nice once you finally get 24 tables going but as your table selecting this app is no better than using a few free ahks. If you like to table select while you play or do other things while 24 tabling the fact that you have to move your mouse over the table eliminates alot of the ease of use that this program is supposed to give.
The other option of bring table to the foreground isnt so great either as everytime you click on something that table is put in the background and this happens often while 24 tabling/table selecting.
The app needs to allow bring to foreground and move mouse to table to be enabled at the same time to eliminate this problem either that or figure out a way for the table to be brought to the foreground and kept there even if clicking on something else at the time. The latter would be prefferable as you wouldnt have to move your mouse.
The way I think that most people (including me) get around this problem is to use the "Cycle to first in line table" hotkey with the jump mouse to cycled tables option turned on.
This way when you use "table in foreground" and click on a non-table window you can always jump back to the action (and have your mouse move automatically to the urgent table) by hitting the "Cycle to first in line hotkey".
Similarly when you are using Table Under Mouse you can have the mouse jump when you want it to by using the cycle hotkey.
I think having the mouse jump be an option with Table Under Mouse is actually very dangerous and is a fair amount more complex than you might think. What if I am about to use an advanced action check/fold hotkey at table A, and then the instant before I hit the hotkey it becomes my turn at table B. Under your system the mouse jumps to table B and I accidently fold my hand at Table B.
If we force the Table in foreground to remain targetted, even when you select other windows, then you would not be able to type IMs, navigate the lobby, etc without potentially hitting hotkeys accidently. Particularly if you use mouse hotkeys this would prevent you from using those mouse buttons in other applications (or in the lobby) while playing which might be a real hassle.
Anyways this is a problem we have thought long and hard about and we have yet to come up with a perfect solution. Generally our approach has been to error on the side of caution chose setups that minimize the potential for misclicks/mistakes.
If your not using the "Cycle to first in line table" hotkey right now I highly recommend trying it. I use it constantly and find that it is a great solution for exactly the problem you are describing.
If you have other suggestions for how to improve things (or if you think my arguments for why the system your suggesting might be tough to handle are no good) definitely drop me a PM and we can discuss it more.
I really appreciate the feedback,
Thanks
Tarath
Last edited by tarath; 05-16-2009 at 04:35 AM.