Quote:
Originally Posted by zutnop
CLIFF NOTES:
1) If some performance testing and improvements could be made in the "activate current table under mouse" or "activate next table" areas at the code side, it would enhance the user experience A LOT for me!
2) It seemed to me that the option "Also (if above is checked) auto-activate the table under mouse" (which is the last child option under the third strategy to activate next table from stack and move mouse to home - which I have both selected) is broken or doesn't do anything on my comp.
3) A new option to "auto-click ok in get chips window only if you manually clicked the get chips PSC shortkey" would be perfect for me, but if it's not helpful for others I can live without it and click the OK manually.
4) A new option to "do not move the get chips window upward ~150px" would take away the wasted 1-3 seconds (because the moving is not instantaneous) and the missclicks that happen when I try to hit the buttons in their original location .
LONG post below....
[removed for brievity in quoted area]
Thank you for your detailed discssion of new feature suggestions. I appreciate new ideas as most new feature enhancements come from users!
1. I believe one other user said they were seeing a slow response in this area. I'm not able to duplicate this, as my response times are very quick here... Would it be possible to set up a team viewer session with you so I could see this. Please email me at our support email address on the contact web page. There must me some set of unique settings or some interaction with another piece of software.
2. Try this test... open 2 full tilt tables (you don't have to sit down). If this option is checked (and so are all the blue items on the Table 2 tab), then as you move your mouse between the 2 tables, the software will activate each table as you move your mouse to it. If you uncheck the bottom blue box, then moving your mouse over the table will not activate the table.
3. I can understand your need, and I will add this to the wish list.
4. The software moves this dialog box up, because it needs to see if the hero is seated already. Sometimes the dialog box is large (and the table is small) and it covers up the area of the table that the software looks to see if the hero is already seated. I believe the software waits until there isn't any pending action at the tables before clearing this dialog box, so as not to interfere with your clicking on the table... do you play with stacked tables? that is more interfering, of course, when a dialog box pops on top.
nano