Created attachment 97078 [details]
Screenshot of Data>Form... Window with no scrolling possible
Steps to reproduce:
1. Create about 30 column headers (first row)
2. Open Data>Form...
3. Input some data.
Current behavior: You cannot scroll the list of input fields, the last entries are not visible.
Expected behavior: To scroll down the list.
Operating System: Mac OS X
Version: 126.96.36.199 release
Created attachment 97155 [details]
Hi Hendrik, thanks for reporting.
Version: 188.8.131.52 Build ID: 3be8cda0bddd8e430d8cda1ebfd581265cca5a0f
Version: 184.108.40.206.alpha0+ Build ID: 615f6aa293a6da90da94e6e78828198ffbc0ca5e
TinderBox: Win-x86@39, Branch:master, Time: 2014-04-08_01:30:26
Scroll bar is visible but works for the records not for the fields.
This bug is already there in 4.1.
*** Bug 77799 has been marked as a duplicate of this bug. ***
Due to the way this dialog works, we have no choice but to set an upper limit on the number of columns, and have the dialog fail to launch when that exceeds the limit.
Can't you do columns? Or don't use the scroll bars for moving onto the next record, since there is already buttons for that on the UI?
(In reply to comment #5)
> Can't you do columns? Or don't use the scroll bars for moving onto the next
> record, since there is already buttons for that on the UI?
No. Because that would be a re-design of the UI which is beyond the scope of this bug fixing.
If you want a redesign, join the design team and try to find an interested developer to take on the task.
To clarify, I'm not against redesigning this dialog, but that would require more effort & planning and I have no interest nor time to take on such task at this time.
Or, our alternative would be to turn this bug report into an enhancement request for the re-design of the dialog, and leave it until someone interested will show up. It may take one month or 5 years, depending...
Since the dialog is not producing errors or causing errors, but just don't work for any columns beyond a certain count, I think it would be worth more to ask for a redesign.
I'm working with Oracle SQL Developer, and they also have this features and theirs work well (buttons for next/pre record and scrolling for columns/fields) so there is a very simple way of making this work.
I think the original design of this dialog was not giving enough thought because one doesn't use it that much, but a redesign would be worth it for the quality of the project.
Because it is a stand-alone dialog that a junior/new developer can work on without messing with important code, it may be a nice assignment for new comer contributing developers.
I'm not sure what Hendrik Koch think since he also reported this.
Actually, re-design may be the only way to go. This dialog behaves in a very weird way even without this bug.
Ok.. I'll give you a point there, Bernard. I'm leaning toward what you said in Comment 9.
(In reply to comment #10)
> Actually, re-design may be the only way to go. This dialog behaves in a
> very weird way even without this bug.
Unless you are indicating something else, yes it is weird that you use the scrollbars to move to the next record. Although their is buttons to do the same thing.
(In reply to comment #11)
> Ok.. I'll give you a point there, Bernard. I'm leaning toward what you said
> in Comment 9.
I agree with a re-design, so that scrolling moves the window content up/down. In my opinion this is the expected behaviour of scrollbars.
The oddness preceded its conversion to .ui FWIW. Shouldn't be too hard to modify it. See sc/uiconfig/scalc/ui/dataform.ui and sc/source/ui/miscdlgs/datafdlg.cxx to get started
Created attachment 99579 [details]
Oracle SQL Developer's Single Row window layout.
For some inspiration, here is a sample of Oracle SQL Developer's design of this window.
I don't think I need to explain it's functionality. But it is a very neat layout.
Also, if the dialog won't scroll, there ought to be a warning when you click on "Form" to show that:
Number of columns has been exceeded
What the maximum number of columns are
And a help suggestion/link to possible resolutions (like how to create a relational table).
P.S. I'm not a developer.
*** Bug 104721 has been marked as a duplicate of this bug. ***
*** Bug 124782 has been marked as a duplicate of this bug. ***