-
-
Notifications
You must be signed in to change notification settings - Fork 248
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Breeding Planner GUI Bug #620
Comments
Hi, that's great news. I try to find a workaround for that issue for over a year. Thank you for sharing how to fix this! |
Alas, it's different in win7 and disabling display scaling doesn't fix the issue. |
If you find the fix for windows 7, post it here. |
The layout-method was changed, does it show correctly now? |
Win7 ASB user reporting in. Names are readable now. Thank you. Column names are slightly shifted. Is it possible to use same method for pedigree tab? Atm it is very hard to understand. |
Thanks for the feedback! The pedigree has a more complicated layout which isn't as easily put in a table, also the arrows are probably hard to set. I'll look into the column-headers in the breeding plan. |
Why the fuck was I included in this email? Who are you people?
…On Sun, Mar 18, 2018 at 8:34 AM, cadon ***@***.***> wrote:
Thanks for the feedback! The pedigree has a more complicated layout which
isn't as easily put in a table, also the arrows are probably hard to set.
I'll look into the column-headers in the breeding plan.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#620 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AitGe7IBn46BlPjwcw7WOS-aCHnZH4x8ks5tflRdgaJpZM4SBnGr>
.
|
|
@Mymsea or maybe because you started this github issue on 2/11/2018. maybe try and read what you get and you may figure out why you are getting emails |
I've never heard of github before this. Plz stop emailing me.
…On Thu, Mar 22, 2018 at 10:46 PM, kohonac ***@***.***> wrote:
@Mymsea <https://github.com/mymsea> or maybe because you started this
github issue on 2/11/2018. maybe try and read what you get and you may
figure out why you are getting emails
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#620 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AitGew6ST-BhdQJZS8Aj0NH1PmyUUVy4ks5thGIAgaJpZM4SBnGr>
.
|
@Mymsea if you didn't set up this account which uses your email, I suggest you write to the support of github here https://github.com/contact. Like kohonac wrote, someone took your email-adress to create the account https://github.com/Mymsea. Changing your password of this email-account is advised as well. |
I'm still having an issue similar to this one: The female side aligns just fine but the male side gets a little compacted and the columns are slightly misaligned. It just makes things a little difficult to check at a glance. I tried the DPI fix above but the box was already unchecked for me. I tried checking it just to see what happens and it didn't fix it. |
@harry323 the layout of that was partly fixed some time ago, but the breeding scores apparently still are affected by different DPI settings. I'll see what I can do in this case, it's a bit more complicated. |
@cadon Thanks for that. If there's a setting change that I can make on my end then I'll be happy to set it properly so that you don't have to do any tinkering. |
@cadon I figured out the issue. In my Windows 10 Settings I had the Scale and layout setting changed to 225% from the recommended settings of 100%. Incidentally I realized this while doing something entirely different. Once I changed the scaling percentage to 100% ARK Smart Breeding displays everything correctly including the Taming and Breeding Plan tabs. |
closing as being duplicate of #151. |
The GUI for my breeding planner is messed up. Everything is way too close together.
https://image.prntscr.com/image/UUBea-89Sv6xpXtE4yzHLA.png
The text was updated successfully, but these errors were encountered: