Skip to content
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

Button and Text Scaling Issue on Ubuntu 18.04 #24

Open
digikar99 opened this issue Dec 10, 2021 · 3 comments
Open

Button and Text Scaling Issue on Ubuntu 18.04 #24

digikar99 opened this issue Dec 10, 2021 · 3 comments

Comments

@digikar99
Copy link

digikar99 commented Dec 10, 2021

Hi! Thank you for the textbook as well as the accompanying simulations! This work - Leabra - seems really exciting.

I'm currently using the simulations from ccn_sims_v1.3.1_linux.tar.gz in v1.3.1 03 Sep 2021 release along with the textbook, and have run into a few issues related to button and text scaling.

  • [Resolved] Essentially, the buttons and text are too large. This is still okay, since using an additional monitor does the trick.
  • [Partially resolved] However, in some cases, such as illustrated here, the text flows out of the buttons, thus rendering the text unreadable.

I'd be glad if someone knows about any recommended ways to resolve or work-around these issues.

@digikar99
Copy link
Author

Okay, this is a fair bit more configurable than my first guess.

  • I was unable to locate the GoGI preferences menu earlier; there, the zoom and LogicalDPIScale options take care of the first point.
  • About the second point, hovering does show a tooltip corresponding to the text, so this kinda works as well. Although, it would be great if the text could fit inside the button. The etable.Table window also has a Config button, but as of this moment, I have failed to notice any change produced by changing the options and 'UpdtView' using 'Config'.

@rcoreilly
Copy link
Collaborator

For the tables, the idea is to size columns according to the data, not the headers, which can be rather long sometimes and would thus result in less efficient (and inconsistent-width) display of info.. So yeah the tooltip is the solution there. You could file an issue in the etable repository about an overall option to "show full headers" -- it wouldn't be very hard to support that option and it would be useful in some cases.

@digikar99
Copy link
Author

Alright, done, thank you!

In this particular case, since 'UniqPats' is a common prefix, another way to resolve this could be to make it a common header, and the part following ':' would be the subheaders, something like this:

| Index | Params |                        UniqPats                            |
|       |        | Count    | Mean | Std | Sem | Min | Q1 | Median | Q3 | Max |
|-------|--------|----------|------|-----|-----|-----|----|--------|----|-----|
|       |        |          |      |     |     |     |    |        |    |     |

But I'm not sure if this needs changes here, or someplace else since it seems a 2/multi level header could be useful at other places too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants