Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
ID | ||||||||
0018019 | ||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
defect | [Openbravo ERP] B. User interface | minor | always | 2011-07-18 14:02 | 2011-07-19 13:04 | |||
Reporter | jecharri | View Status | public | |||||
Assigned To | mtaal | |||||||
Priority | high | Resolution | no change required | Fixed in Version | ||||
Status | closed | Fix in branch | Fixed in SCM revision | |||||
Projection | none | ETA | none | Target Version | 3.0MP3 | |||
OS | Any | Database | Any | Java version | ||||
OS Version | Database version | Ant version | ||||||
Product Version | pi | SCM revision | ||||||
Review Assigned To | ||||||||
Web browser | Google Chrome | |||||||
Modules | Core | |||||||
Regression level | ||||||||
Regression date | ||||||||
Regression introduced in release | ||||||||
Regression introduced by commit | ||||||||
Triggers an Emergency Pack | No | |||||||
Summary | 0018019: The scroll is not working properly | |||||||
Description | If you are in one window with a lot of lines and you need to use the scroller. You will see that it is not working properly. For example try to go to the last record, you will see that you can't go inmediatly because the GUI it is refreshing to try to arrive to the last record. Apart from that, if you want to see the last record, you have to put the mouse out of the scroller. | |||||||
Steps To Reproduce | Try to use the scroll when you have a lot of records. | |||||||
Tags | No tags attached. | |||||||
Attached Files | ||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | |
Notes | |
(0039173) mtaal (manager) 2011-07-18 16:43 |
this behavior is on purpose and by design. The system does not do a full count of the number of records in a table. So it detects that there are more records when you scroll down. The only issue could be with your last remark 'if you want to see the last record, you have to put the mouse out of the scroller'. Can you explain what you mean? Note, that with the current implementation it is not really practical to scroll to the last record as you have to click down many many times. So an alternative is to change the sorting, then the last record will be the first. The current logic is based on the assumption that scrolling through very large lists does not make sense, if you have a large list you should first filter to bring down the rowcount. gr. Martin |
(0039223) jecharri (developer) 2011-07-19 13:03 |
Don't worry, the second problem is related with your explanation about the scroll: "So it detects that there are more records when you scroll down" I will reject the issue |
Issue History | |||
Date Modified | Username | Field | Change |
2011-07-18 14:02 | jecharri | New Issue | |
2011-07-18 14:02 | jecharri | Assigned To | => dbaz |
2011-07-18 14:02 | jecharri | Web browser | => Google Chrome |
2011-07-18 14:02 | jecharri | Modules | => Core |
2011-07-18 14:02 | jecharri | Resolution time | => 1317765600 |
2011-07-18 15:58 | dbaz | Assigned To | dbaz => mtaal |
2011-07-18 16:43 | mtaal | Note Added: 0039173 | |
2011-07-18 16:43 | mtaal | Status | new => feedback |
2011-07-19 13:03 | jecharri | Note Added: 0039223 | |
2011-07-19 13:04 | jecharri | Status | feedback => closed |
2011-07-19 13:04 | jecharri | Resolution | open => no change required |
Copyright © 2000 - 2009 MantisBT Group |