| Summary: | Add option to change the behaviour when double clicking an object in the project navigator | ||
|---|---|---|---|
| Product: | [Applications] KEXI | Reporter: | Dimitrios T Tanis <dimitrios.tanis> |
| Component: | General | Assignee: | Kexi Bugs <kexi-bugs> |
| Status: | CLOSED FIXED | ||
| Severity: | wishlist | CC: | adam, inksi, staniek |
| Priority: | LO | Flags: | staniek:
Usability+
|
| Version: | 2.4 alpha3 (Calligra 2.4 alpha3) | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 3.1.0 | |
| Sentry Crash Report: | |||
|
Description
Dimitrios T Tanis
2011-07-17 20:53:50 UTC
Thanks for this feedback. It all depends what is type of the object in topic. Consistent behaviour is important and if we look at MS, it always executes macros/scripts/opens data views. If I remember correctly, the navigator is used by end-users as well so I do not agree with the argument about developers using the navigator. The use case for end-user is as follows: user develops own database for data analysis purposes. I and my coworkers have been using MSA this way a lot (we had dozens of insert/update queries, macros and so on and there was a lot of clicking in the navigator). I am not against option for changing the behaviour but this should be in 'advanced' section and the defaults would rather stay as they are now. The issue with functional queries that change the database can be solved: there could be warning set up, on by default (as in MSA, in fact in MSA developers have to explicitly bypass warnings individually or globally). IDEALLY it would be reported in separate bugs.kde.org wish. Navigator can be used by end users however a switchboard was suggested. This is why there was an option to hide the database objects window (MSA 2003 and earlier). In MSA 2007 the database object window was replaced by a navigator that was supposed to be used by end users also (as the switchboard was deprecated) however was hardly as it lacked the required UI capabilities needed (per user menus, etc). I agree that when developing/using a DB inhouse this makes no important difference whatsoever, however I believe it would be a nice feature to have an option during the designing phase. As for the queries, I didn't filed it seperately as I believe that was the planned behavior for some time in the future (to have warnings that is). On 18 July 2011 01:06, Dimitrios T Tanis <applyseries@gmail.com> wrote: > As for the queries, I didn't filed it seperately as I believe that was the > planned behavior for some time in the future (to have warnings that is). Well, but we'll have to remember this task even if it's small. We have the bugzilla for this or this page: http://community.kde.org/Kexi/TODOs (mur flexible but have to maintain the structure by hand). Most suitable approach: though a plugin or an internal about:config-like option so users that don't need such specific setting won't be confused when it's in Kexi options. Suppported in kexirc file since 3.1: Group MainWindow, option name SingleClickOpens. Expample: [MainWindow] SingleClickOpens=true Naturally we plan to have options supported in the GUI too but that's another wish. |