StackAndTile Forums

Full Version: high DPI
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2

baal

is there a high DPI version of the latest update?

Is there a way to integrate this into the release instead of asking every new version?
Yeah sorry about this. I've still slacked on getting a 4k monitor to do proper testing. The v3.0 release will be high DPI supported but I want to make sure to find as many bugs as I can before releasing it. So its been my fault

Here you can downloadd v2.98.03a-highDPI

http://www.stackandtile.com/sat/tmp/Stac...ighDPI.exe

G-G-G-Guest

is there any difference with the regular client? or is just better readable font/visibility?

G-G-G-Guest

any plans to make party and/or microgaming work with 150% scaling?

And to make GG work correctly?

Kind regards,
S&T User since 2011
(03-09-2019, 01:56 PM)G-G-G-Guest Wrote: [ -> ]is there any difference with the regular client? or is just better readable font/visibility?
Only better readability on high resolution monitors. I think I also added the ability for hotkey keys to work on non-poker tables without having to use the "Disable Hotkeys" hotkey. So all of your letters can be used to type an email for example.

(03-09-2019, 02:09 PM)G-G-G-Guest Wrote: [ -> ]any plans to make party and/or microgaming work with 150% scaling?

And to make GG work correctly?

Kind regards,
S&T User since 2011
What exact problems are you facing? What is failing? Have you tried the solutions here:
http://www.stackandtile.com/sat/help/windows-10-fix

G-G-G-Guest

Ok so I've been able to get both the GG browser and the new MPN client (also based on chrome) to work with PW scan mode, which is amazing. You have no idea how long I've been working on this. But this is gonna mean my party tables are going to flicker, which is a problem. Is there anything you can think of that can fix this? Only thing I can think of is running instances of 2 S&T, 1 exclusively for party tables. Is that possible?

gggguest

or actually just have everything on DWM mode, and have a seperate instance open for PW sites like GGnetwork browser, new MPN, bodog/ignition? You see any potential issues with this?

Cheers,
Felix
(03-12-2019, 06:58 AM)G-G-G-Guest Wrote: [ -> ]Ok so I've been able to get both the GG browser and the new MPN client (also based on chrome) to work with PW scan mode, which is amazing. You have no idea how long I've been working on this. But this is gonna mean my party tables are going to flicker, which is a problem. Is there anything you can think of that can fix this? Only thing I can think of is running instances of 2 S&T, 1 exclusively for party tables. Is that possible?

(03-12-2019, 07:30 AM)gggguest Wrote: [ -> ]or actually just have everything on DWM mode, and have a seperate instance open for PW sites like GGnetwork browser, new MPN, bodog/ignition? You see any potential issues with this?

Yeah that is a problem, but I think running multiple instances could solve it. I don't see any issues off the top of my head, other than the normal considerations for running multiple instances. See this page:

http://www.stackandtile.com/sat/help/run...-instances

Let me know how it works out because I am curious. I've never tried this myself

felix

PW mode is making my 2nd display screen flicker/shake. is this normal?

felix

nvm prev. post. i think my phone was too close to my setup and giving off weird signals.

pretty sure i got it working correctly for the most part. Only thing that's still not working 100% as it should is, sometimes my stack and tile doesnt recognize a gg browser table(in chrome). and then when i get moved to a different table it will recognize it.

[settings]

standard_table_width=1233
standard_table_height=1026

buttons=fold,call,bet

action_button=fold

fold_button_x_coord=801
fold_button_y_coord=965
fold_button_region_topleft_x_coord=758
fold_button_region_topleft_y_coord=933
fold_button_region_bottomright_x_coord=851
fold_button_region_bottomright_y_coord=978

call_button_x_coord=2585
call_button_y_coord=1817
call_button_region_topleft_x_coord=912
call_button_region_topleft_y_coord=932
call_button_region_bottomright_x_coord=1005
call_button_region_bottomright_y_coord=978

bet_button_x_coord=1166
bet_button_y_coord=972
bet_button_region_topleft_x_coord=1065
bet_button_region_topleft_y_coord=934
bet_button_region_bottomright_x_coord=1157
bet_button_region_bottomright_y_coord=978

use_basic_click=0

table_class=Chrome_WidgetWin_1

table_include_title_text=Table
table_exclude_title_text=
Pages: 1 2