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

Groups view: position of unfold-symbols & heigth of entry-lines & group icons #3252

Closed
buhtz opened this issue Oct 4, 2017 · 10 comments
Closed

Comments

@buhtz
Copy link

buhtz commented Oct 4, 2017

Using stable 4.0 for your download site with Windows 10. There are three aspects about the groups view.

The symbols for fold and unfold the groups are on the right side/end of each entry. This is unusual compared to tree-views in other software on many operating systems. Maybe their are but currently I am not aware of other software using it this way. It should be possible (per settings dialog) to switch the position to the left.

The height of the lines for each entry are quite heigh. I think this is because of the circle-box around count symbol. It is not only unusual compared to other software. :) It is wasting space on the screen. Can we modify this? It is nice that you currently have users with big screens in mind while developing JabRef. But please don't forget the other ones with small screens or not using JabRef in full-screen mode.

On the left of the group names are icons. They are two wide/big and have no functionality. And they look a bit like a fold-unfold-symbol. So you clicking on it and nothing happens before you are aware of the missplaced fold-symbols on the right end of the group name.

@buhtz buhtz changed the title 4.0 groups view: position of unfold-symbols & heigth of entry-lines 4.0 groups view: position of unfold-symbols & heigth of entry-lines & group icons Oct 4, 2017
@tobiasdiez
Copy link
Member

The new icons on the left are customizable and were actually a feature requested by users quite a few times. Because of these icons the (un-)fold icons moved to the right (admittedly, a bit unorthodox but not too unusual). I think we will not revert these ui-changes. Note also that you can simply double-click a group to collapse/expand it.

@buhtz
Copy link
Author

buhtz commented Oct 4, 2017

Would it be an option to make the postion customizable by a setting?

@Druidefix
Copy link

What about the height of the entries? Having many groups I'm now always scrolling...

@geyslein
Copy link

geyslein commented Oct 6, 2017

I'm in for every recommendation made by buhtz. The height of the entries is a bit annoying, I'm scrolling way too much now. I am not so much against putting the symbols to (un)fold on the right but it takes longer to grasp whether a group is folded or not. The two symbols do not differ that much on the first glimpse and the indention of a subgroup is not so big either which both makes it a bit more complicated to distinguish between group and subgroup.

@AEgit
Copy link

AEgit commented Oct 6, 2017

Maybe as a workaround until the issue is fixed: Instead of scrolling in the groups panel, you can just search for a group with the newly implemented groups filter:
#2588

@buhtz
Copy link
Author

buhtz commented Jul 20, 2018

4.3.1 problem is there

@buhtz
Copy link
Author

buhtz commented Jul 20, 2018

Could be related #4220

@buhtz
Copy link
Author

buhtz commented Feb 20, 2019

Still exists in 5.* dev

@buhtz
Copy link
Author

buhtz commented Feb 20, 2019

The problem still exists in current 5.* dev

@stefan-kolb stefan-kolb changed the title 4.0 groups view: position of unfold-symbols & heigth of entry-lines & group icons Groups view: position of unfold-symbols & heigth of entry-lines & group icons Aug 25, 2019
@github-actions
Copy link
Contributor

This issue has been inactive for half a year. Since JabRef is constantly evolving this issue may not be relevant any longer and it will be closed in two weeks if no further activity occurs.

As part of an effort to ensure that the JabRef team is focusing on important and valid issues, we would like to ask if you could update the issue if it still persists. This could be in the following form:

  • If there has been a longer discussion, add a short summary of the most important points as a new comment (if not yet existing).
  • Provide further steps or information on how to reproduce this issue.
  • Upvote the initial post if you like to see it implemented soon. Votes are not the only metric that we use to determine the requests that are implemented, however, they do factor into our decision-making process.
  • If all information is provided and still up-to-date, then just add a short comment that the issue is still relevant.

Thank you for your contribution!

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

No branches or pull requests

6 participants