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

Scrolling in the Context Editor while Headers Stay Visible #43

Open
eugenkiss opened this issue Jun 4, 2013 · 3 comments
Open

Scrolling in the Context Editor while Headers Stay Visible #43

eugenkiss opened this issue Jun 4, 2013 · 3 comments

Comments

@eugenkiss
Copy link
Contributor

I believe it would be great, especially for bigger contexts, if both the attribute header row and the object header column would stay visible at all times. When scrolling horizontally, the attribute header row would scroll horizontally, too, and when scrolling vertically, the object header columns would scroll vertically, too.

@blu2lz
Copy link
Contributor

blu2lz commented Nov 25, 2013

In fact, this is quite easy. You design two tables. One with only the first column and the second one with the rest of the table. Needs adjustment of the table model and the table itself and you got a fixed row header.
The column header is even simpler. It works out of the box…if you use it. The column header in the context editor is not used. I don't really understand why, but the table is done in a weird way anyway.
I suppose this does not have the highest priority, so I get to some more important issues first. Maybe later I redesign the whole table because I'm afraid this would be easier than adjusting this one.

@blu2lz
Copy link
Contributor

blu2lz commented Nov 28, 2013

see also #116.

@blu2lz
Copy link
Contributor

blu2lz commented Nov 29, 2013

This table has the most awful design I have ever seen. In the javadocs you read that the code is ugly because JTable is not meant to be too flexible. WTF? JTable is very flexible. Every swing element is flexible because it follows the MVC and you can extend/override/adjust every bit of functionality in it. Whoever wrote this was just not capable of doing so. BTW his code is ugly because he did not meant to comment it too much…before adjusting this spaghetti code I'd rather do it again from scratch. After all the time I burned with trying to fix the related bugs this got to be said…

So anybody waiting for #33, #42, #116 and this issue to be fixed: I'm working on it but it can take a while to be finished completely.

blu2lz added a commit that referenced this issue Jan 24, 2014
now but the table is one bunch of crap…so it does not react to context
changes. Because there are that much issues open regarding the context
editor and my decision of a redesign I will tackle it all together in
time. See #33, #42, #43, #116
@blu2lz blu2lz modified the milestones: 0.7, 0.6 Mar 18, 2014
@rjoberon rjoberon modified the milestones: 0.8, 0.7 Apr 30, 2014
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

3 participants