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

Refresh and Error status can be cut off #301

Closed
sssoleileraaa opened this issue Apr 11, 2019 · 1 comment
Closed

Refresh and Error status can be cut off #301

sssoleileraaa opened this issue Apr 11, 2019 · 1 comment
Labels
bug Something isn't working

Comments

@sssoleileraaa
Copy link
Contributor

Description

Refresh status is cut off when window is not wide enough (this might be related to the introduction of error_status and the width of my client which was set to 960 pixels wide)

https://user-images.githubusercontent.com/15223328/55972972-9649bf80-5c52-11e9-8278-bf12a453b341.png

Error status can also be cut offf when window is not wide enough. We do have minimum widget sizes for the sourcelist and conversation view which will prevent us from making the window too small. These sizes will be added in PRs for each section.

Other things we can do are:

  • make error status messages actual popup windows that closes when a message goes away. Right now it is a statusbar that has a reserved section of the main status bar.
  • make the error section smaller
  • add some logic that will change the size of the acitivity status bar widget when the error status bar widget hides, so that it can take up more space when errors go away
@eloquence eloquence added this to the 0.2.0alpha milestone Jul 2, 2019
@eloquence eloquence modified the milestones: 0.2.0alpha, 0.2.0beta Dec 12, 2019
@eloquence eloquence added bug Something isn't working needs discussion and removed needs discussion labels Mar 20, 2020
@eloquence eloquence removed this from the 0.2.xbeta milestone Mar 20, 2020
@eloquence
Copy link
Member

This no longer occurs with current "Last Refresh" behavior; we are tracking a recently observed similar example in #932. Closing this historical issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants