| Anonymous | Login | Signup for a new account | 2013-06-20 08:54 CEST | ![]() |
| All Projects | FPC | Lazarus: Packages, Patches | Lazarus CCR | Mantis | fpGUI | fpcprojects: fpprofiler |
| Main | My View | View Issues | Change Log | Roadmap |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0014758 | Lazarus | Database | public | 2009-10-08 13:37 | 2011-12-01 11:24 | ||||
| Reporter | alexP | ||||||||
| Assigned To | Jesus Reyes | ||||||||
| Priority | normal | Severity | minor | Reproducibility | always | ||||
| Status | closed | Resolution | won't fix | ||||||
| Platform | fpc2.24 | OS | winxp32 | OS Version | 0.9.29 beta | ||||
| Product Version | Product Build | ||||||||
| Target Version | 0.9.30 | Fixed in Version | 0.9.29 (SVN) | ||||||
| Summary | 0014758: error in buttons DBNavigator | ||||||||
| Description | when you insert or edit command buttons DBNavigator refresh insert and delete are enabled as well as the first, prior, next and last. believe that the right would be to disable these buttons avoiding user error application. thanks | ||||||||
| Tags | dbcontrols | ||||||||
| Fixed in Revision | |||||||||
| LazTarget | 0.9.30 | ||||||||
| Widgetset | |||||||||
| Attached Files | |||||||||
Notes |
|
|
(0031213) alexP (reporter) 2009-10-09 04:04 |
I arranged a time and made some changes that worked well, follow the file for approval |
|
(0038483) samuel herzog (developer) 2010-06-11 19:34 |
I tested the changes from alexP and it seems to be ok. Uploaded the patch-file again. (against current SVN). |
|
(0038650) Jesus Reyes (developer) 2010-06-19 21:07 |
I'm sorry, i think the intended behavior is not ok, or at least it looks it's a feature just some applications need. Cursor buttons should not be disabled while editing, otherwise we would need a way to prevent the user to move to another record using mouse or keyboard (in a grid) Deleting a non-inserted or even an editing record, it's not a bug and the same can be made with keyboard (in a grid) In general features supported by underlaying dataset should not be artificially blocked, or if they must, then it's application specific behavior. In case an application needs to customize what buttons are enabled (or visible, but for that there is a VisibleButtons property) the programmer can access protected DbNavigator's Buttons Field using an access (or crack) class, or at request we can modify DbNavigator to include easy access to Button's enabled property, in that case, please submit a feature request for it. |
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2009-10-08 13:37 | alexP | New Issue | |
| 2009-10-08 14:30 | Vincent Snijders | LazTarget | => 1.0 |
| 2009-10-08 14:30 | Vincent Snijders | Status | new => acknowledged |
| 2009-10-08 14:30 | Vincent Snijders | Target Version | => 1.0.0 |
| 2009-10-09 04:03 | alexP | File Added: dbnavigator - diff.diff | |
| 2009-10-09 04:04 | alexP | Note Added: 0031213 | |
| 2009-10-09 08:38 | Vincent Snijders | LazTarget | 1.0 => 0.9.30 |
| 2009-10-09 08:38 | Vincent Snijders | Assigned To | => Jesus Reyes |
| 2009-10-09 08:38 | Vincent Snijders | Status | acknowledged => assigned |
| 2009-10-09 08:38 | Vincent Snijders | Target Version | 1.0.0 => 0.9.30 |
| 2010-03-15 03:04 | Jesus Reyes | Tag Attached: dbcontrols | |
| 2010-06-11 19:32 | samuel herzog | File Added: dbnavigator.patch | |
| 2010-06-11 19:34 | samuel herzog | Note Added: 0038483 | |
| 2010-06-19 21:07 | Jesus Reyes | Status | assigned => resolved |
| 2010-06-19 21:07 | Jesus Reyes | Fixed in Version | => 0.9.29 (SVN) |
| 2010-06-19 21:07 | Jesus Reyes | Resolution | open => won't fix |
| 2010-06-19 21:07 | Jesus Reyes | Note Added: 0038650 | |
| 2011-12-01 11:24 | Marc Weustink | Status | resolved => closed |
| Main | My View | View Issues | Change Log | Roadmap |



