Forgive the poor formatting below with the quotes...

[ QUOTE ]
[ QUOTE ]
I wasn’t able to use V2 for more than a few minutes b/c of a few problems:

[/ QUOTE ]

Let me start by saying that i'm quite pleased that nothing blew up [img]/images/graemlins/smile.gif[/img]

[/ QUOTE ]

Me too!


[ QUOTE ]
2.My laptop screen size appeared to be misidentified, as the right most 1” was never used. The screen resolution listed under one tab was incorrect (and couldn’t be changed so far as I could tell).

[/ QUOTE ]

Are you using your laptop and an external monitor at the same time?

[/ QUOTE ]

Yes.

Are they running different resolutions?

[/ QUOTE ]

Yes. the 2nd monitor has a lower max than my laptop.

The identified resolution info is naive as it presumes that all monitors are of the same size, alas your resolution might very easily be misidentified. Even though this, your tables ought to line up with the actual corners of the monitors, no matter what resolution they're running. But they didn't?

[/ QUOTE ]

They didn't go to the 2nd monitor ever, so I don't know if they would have lined up. But they never lined up on my lap top on the right side (other edges were fine).

[ QUOTE ]
Recommedation for a new feature for those who want to multi-table beyond their monitor capabilities: allow tables in which you are active after the flop (or through some manual identifier) to remain on top of other tables until the start of the next hand. The idea is to be able to follow the action in a subset of tables in which you are especially interested. I am currently 12-tabling on two monitors and the only way I can follow a specific table is to place all 12 tables on my 2nd monitor, have the focus on the primary monitor, and then drag a table of interest to the main monitor for the duration of a hand.

[/ QUOTE ]

I've experimented with this form of tracking previously, and i've come to the conclusion that it's too dangerous to implement before i know MTH v2 is 100% stable. The reason being that the way things work results in the windows remaining their "topmost" state, even though MTH quits/crashes. That means if two of your tables were set to be topmost and MTH crashed, they would remain topmost, and you couldn't do anything about it other than closing/reopening the tables.

And trust me, it's mayhem when you're running 12-16 tables on a small monitor and two of the tables suddenly cover more than half your screen... I had it happen to me quite some times when i was still running my single 17" [img]/images/graemlins/smile.gif[/img]

[/ QUOTE ]

gottcha.

Thank you for trying v2, and even more thanks for helping me solve the bugs!

You can get the newest version at the same URL.

[/ QUOTE ]