Re: [darktable-dev] possible data loss scenario

2017-10-27 Thread Jean-Pierre Verrue
I was also trapped by the loss of focus. I found a very simple parade. I modified the shortcuts r, 1,2,3,4 and 5 for the light table and darkroom to CTRL-r, CTRL-1,..., CTRL-5. Since I have no problem! JP Le 25/10/2017 à 23:51, Patrick Shanahan a écrit : * Alexander Rabtchevich [10-25-17 15:

Aw: Re: [darktable-dev] possible data loss scenario

2017-10-26 Thread Alexander Rabtchevich
Hello Let's consider the problematic cases and try to make some suggestions. As I recall, there are several possibilities of unintentional actions: 1. In the darkroom mode, ratings etc are applied to an image under cursor, not to the selected or processed one. That can occasionally lead to unpr

Re: [darktable-dev] possible data loss scenario

2017-10-25 Thread David Vincent-Jones
There are standards that most have used across numerous systems and over many years. Double click to select a word element or number and then simply type-in a replacement. This input method is respected across all programs on my system .. except for darktable on which it can, unfortunately, le

Re: [darktable-dev] possible data loss scenario

2017-10-25 Thread Patrick Shanahan
* David Vincent-Jones [10-25-17 12:39]: > The steps that I detailed (below) were quite specific > > David > > > On 10/25/2017 09:18 AM, Patrick Shanahan wrote: > >* Alexander Rabtchevich [10-25-17 12:12]: > >>Hello > >> > >>Yesterday I've almost lost my data again. That time that hadn't happen

Re: [darktable-dev] possible data loss scenario

2017-10-25 Thread Patrick Shanahan
* Alexander Rabtchevich [10-25-17 15:07]: > I've provided all the required steps in the thread before, step by step. > Maybe it's better to spend some time for reading before blaming, isn't it? > > One of the user-cases is: start editing in some edit control (image size for > export etc.) If the

Re: [darktable-dev] possible data loss scenario

2017-10-25 Thread Alexander Rabtchevich
I've provided all the required steps in the thread before, step by step. Maybe it's better to spend some time for reading before blaming, isn't it? One of the user-cases is: start editing in some edit control (image size for export etc.) If the cursor occasionally leaves the control for some o

Re: [darktable-dev] possible data loss scenario

2017-10-25 Thread Matthias Andree
Am 13.10.2017 um 02:12 schrieb Jonathan Richards: > On 12/10/17 22:57, Tobias Ellinghaus wrote: >> Am Donnerstag, 12. Oktober 2017, 17:24:30 CEST schrieb Marcello Mamino: >>> I can reproduce the bug on Debian stable, under Xfce, master branch >>> just compiled, every setting default. The steps to f

Re: [darktable-dev] possible data loss scenario

2017-10-25 Thread David Vincent-Jones
The steps that I detailed (below) were quite specific David On 10/25/2017 09:18 AM, Patrick Shanahan wrote: * Alexander Rabtchevich [10-25-17 12:12]: Hello Yesterday I've almost lost my data again. That time that hadn't happened because no images were selected. It's some kind of Russian rou

Re: [darktable-dev] possible data loss scenario

2017-10-25 Thread Patrick Shanahan
* Alexander Rabtchevich [10-25-17 12:12]: > Hello > > Yesterday I've almost lost my data again. That time that hadn't happened > because no images were selected. It's some kind of Russian roulette to > change image size. > > With respect, > Alexander Rabtchevich > > David Vincent-Jones wrote: >

Re: [darktable-dev] possible data loss scenario

2017-10-25 Thread Alexander Rabtchevich
Hello Yesterday I've almost lost my data again. That time that hadn't happened because no images were selected. It's some kind of Russian roulette to change image size. With respect, Alexander Rabtchevich David Vincent-Jones wrote: Most noticed occurrence: Select items to print > double cl

Re: [darktable-dev] possible data loss scenario

2017-10-17 Thread David Vincent-Jones
Most noticed occurrence: Select items to print > double click to select current width for normal replace > type '0' > All selected images are now 'X' rated. I can only change width and height valued by backspacing. David On 10/13/2017 12:29 AM, David Houlder wrote: > On 13/10/17 08:57, Tobias E

Re: [darktable-dev] possible data loss scenario

2017-10-14 Thread David Houlder
On 14/10/17 03:53, Alexander Rabtchevich wrote: As I understand, the desired action to be click-less is mouse scrolling over a control. Yes, but also... Why should it hook keyboard actions? So you can use the arrow keys, and maybe page-up, page-down, etc. to adjust the slider. Maybe the hove

Re: [darktable-dev] possible data loss scenario

2017-10-13 Thread Alexander Rabtchevich
Hello David Houlder wrote: So here's an idea: make all fields and widgets except for sliders require explicit focus (mouse click or tab key), on the grounds that sliders can be inadvertently changed by click-to-focus in a way that other controls cannot. In the case where a slider was not exp

Re: [darktable-dev] possible data loss scenario

2017-10-13 Thread David Houlder
On 13/10/17 08:57, Tobias Ellinghaus wrote: Am Donnerstag, 12. Oktober 2017, 17:24:30 CEST schrieb Marcello Mamino: I can reproduce the bug on Debian stable, under Xfce, master branch just compiled, every setting default. The steps to follow are *exactly* these 1. Open the "export selected" tab

Re: [darktable-dev] possible data loss scenario

2017-10-12 Thread Marcello Mamino
On Thu, Oct 12, 2017 at 11:57 PM, Tobias Ellinghaus wrote: > Am Donnerstag, 12. Oktober 2017, 17:24:30 CEST schrieb Marcello Mamino: >> I can reproduce the bug on Debian stable, under Xfce, master branch >> just compiled, every setting default. The steps to follow are >> *exactly* these >> >> 1. O

Re: [darktable-dev] possible data loss scenario

2017-10-12 Thread Jonathan Richards
On 12/10/17 22:57, Tobias Ellinghaus wrote: > Am Donnerstag, 12. Oktober 2017, 17:24:30 CEST schrieb Marcello Mamino: >> I can reproduce the bug on Debian stable, under Xfce, master branch >> just compiled, every setting default. The steps to follow are >> *exactly* these >> >> 1. Open the "export

Re: [darktable-dev] possible data loss scenario

2017-10-12 Thread Tobias Ellinghaus
Am Donnerstag, 12. Oktober 2017, 17:24:30 CEST schrieb Marcello Mamino: > I can reproduce the bug on Debian stable, under Xfce, master branch > just compiled, every setting default. The steps to follow are > *exactly* these > > 1. Open the "export selected" tab > 2. Click in the "max size" filed.

Re: [darktable-dev] possible data loss scenario

2017-10-12 Thread Marcello Mamino
I can reproduce the bug on Debian stable, under Xfce, master branch just compiled, every setting default. The steps to follow are *exactly* these 1. Open the "export selected" tab 2. Click in the "max size" filed. 3. Slowly move the pointer *downwards* 4. As soon as the pointer reaches the "allow

Re: [darktable-dev] possible data loss scenario

2017-10-11 Thread Jonathan Richards
On 10/10/17 18:11, Alexander Rabtchevich wrote: > Hello > > And the scenario is still working. > 1. Select an image in the lighttable mode. > 2. Click into the edit window Max size in the export dialog. > 3. Move mouse just slightly outside the edit window. It loses focus > immediately. > 4. Type

Re: [darktable-dev] possible data loss scenario

2017-10-10 Thread Alexander Rabtchevich
xdpyinfo | grep version version number:11.0 X.Org version: 1.18.4 Mate is build as a consequence of gnome 2. Current version is based on gtk3. Linux Mint 18.2 uses Ubuntu 16.04 package base. With respect, Alexander Rabtchevich Roman Lebedev wrote: I have standard Mate from 18.2 Mint a

Re: [darktable-dev] possible data loss scenario

2017-10-10 Thread Roman Lebedev
On Tue, Oct 10, 2017 at 8:28 PM, Alexander Rabtchevich wrote: > Yes, I'm pretty sure :) > > When cursor reaches another control somewhere within the main window, the > edit window looses focus. It should be some control (slider, another edit > window etc), not a label. > I have standard Mate from

Re: [darktable-dev] possible data loss scenario

2017-10-10 Thread Alexander Rabtchevich
Yes, I'm pretty sure :) When cursor reaches another control somewhere within the main window, the edit window looses focus. It should be some control (slider, another edit window etc), not a label. I have standard Mate from 18.2 Mint and proprietary AMD GPUpro video driver. With respect, Ale

Re: [darktable-dev] possible data loss scenario

2017-10-10 Thread J. Liles
Not OP, but chiming in, I have also been bitten by the focus-follows-mouse model in Darktable. Very tricky to use any of the text inputs. I've been reluctant to complain because I use a pretty esoteric WM (StumpWM) which doesn't interact well with some of Darktables widgets (like the left-click ar

Re: [darktable-dev] possible data loss scenario

2017-10-10 Thread David Vincent-Jones
I have had similar problems when typing and have found images re-rated ... it is also really confusing if the sort is set by the rating and the image 'disappears'. David On 10/10/2017 10:11 AM, Alexander Rabtchevich wrote: > Hello > > And the scenario is still working. > 1. Select an image in th

Re: [darktable-dev] possible data loss scenario

2017-10-10 Thread Roman Lebedev
On Tue, Oct 10, 2017 at 8:11 PM, Alexander Rabtchevich wrote: > Hello > > And the scenario is still working. > 1. Select an image in the lighttable mode. > 2. Click into the edit window Max size in the export dialog. > 3. Move mouse just slightly outside the edit window. It loses focus > immediate

Re: [darktable-dev] possible data loss scenario

2017-10-10 Thread Alexander Rabtchevich
Hello And the scenario is still working. 1. Select an image in the lighttable mode. 2. Click into the edit window Max size in the export dialog. 3. Move mouse just slightly outside the edit window. It loses focus immediately. 4. Type the digit you want. It is recognized as rating for the image

Re: [darktable-dev] possible data loss scenario

2017-10-09 Thread Alexander Rabtchevich
Here is the result of the output of cat darktable/build/src/version_gen.c #ifndef RC_BUILD #ifdef HAVE_CONFIG_H #include "config.h" #endif const char darktable_package_version[] = "2.3.0+974~g4c0754d"; const char darktable_package_string[] = PACKAGE_NAME " 2.3.0+974~g4c0754d"; con

Aw: Re: [darktable-dev] possible data loss scenario

2017-10-09 Thread Alexander Rabtchevich
" An: darktable Betreff: Re: [darktable-dev] possible data loss scenario * Alexander Rabtchevich [10-09-17 08:32]: > I'll do it at 6 O'clock. > Gesendet: Montag, 09. Oktober 2017 um 15:17 Uhr > Von: "Roman Lebedev" > Can you please show the output

Re: [darktable-dev] possible data loss scenario

2017-10-09 Thread Patrick Shanahan
* Alexander Rabtchevich [10-09-17 08:32]: > I'll do it at 6 O'clock. > Gesendet: Montag, 09. Oktober 2017 um 15:17 Uhr > Von: "Roman Lebedev" > Can you please show the output of $ cat darktable/build/src/version_gen.c > ? > > Gesendet: Montag, 09. Oktober 2017 um 13:51 Uhr > > Von: "Roman Lebed

Aw: Re: Re: Re: [darktable-dev] possible data loss scenario

2017-10-09 Thread Alexander Rabtchevich
I'll do it at 6 O'clock.   With respect, Alexander Rabtchevich     Gesendet: Montag, 09. Oktober 2017 um 15:17 Uhr Von: "Roman Lebedev" An: "Alexander Rabtchevich" Cc: darktable Betreff: Re: Re: Re: [darktable-dev] possible data loss scenario On Mon, Oct

Re: Re: Re: [darktable-dev] possible data loss scenario

2017-10-09 Thread Roman Lebedev
ot;Roman Lebedev" > An: "Alexander Rabtchevich" > Cc: darktable > Betreff: Re: Re: [darktable-dev] possible data loss scenario > On Mon, Oct 9, 2017 at 1:49 PM, Alexander Rabtchevich > wrote: >> git master > Uhm, that is confusing. Which

Aw: Re: Re: [darktable-dev] possible data loss scenario

2017-10-09 Thread Alexander Rabtchevich
Pull from yesterday.   With respect, Alexander Rabtchevich   Gesendet: Montag, 09. Oktober 2017 um 13:51 Uhr Von: "Roman Lebedev" An: "Alexander Rabtchevich" Cc: darktable Betreff: Re: Re: [darktable-dev] possible data loss scenario On Mon, Oct 9, 2017 at 1:49 PM, A

Re: Re: [darktable-dev] possible data loss scenario

2017-10-09 Thread Roman Lebedev
gt; Gesendet: Montag, 09. Oktober 2017 um 13:42 Uhr > Von: "Roman Lebedev" > An: "Alexander Rabtchevich" > Cc: darktable > Betreff: Re: [darktable-dev] possible data loss scenario > On Mon, Oct 9, 2017 at 9:50 AM, Alexander Rabtchevich > wrote: >> Hello >

Aw: Re: [darktable-dev] possible data loss scenario

2017-10-09 Thread Alexander Rabtchevich
git master   With respect, Alexander Rabtchevich   Gesendet: Montag, 09. Oktober 2017 um 13:42 Uhr Von: "Roman Lebedev" An: "Alexander Rabtchevich" Cc: darktable Betreff: Re: [darktable-dev] possible data loss scenario On Mon, Oct 9, 2017 at 9:50 AM, Alexander Rabtche

Aw: Re: [darktable-dev] possible data loss scenario

2017-10-09 Thread Alexander Rabtchevich
OK, I have a backup of the database, but it is at least a mounth old.   With respect, Alexander Rabtchevich   Gesendet: Montag, 09. Oktober 2017 um 13:24 Uhr Von: "Moritz Moeller" An: "Alexander Rabtchevich" , darktable-dev@lists.darktable.org Betreff: Re: [darktable-dev

Re: [darktable-dev] possible data loss scenario

2017-10-09 Thread Roman Lebedev
On Mon, Oct 9, 2017 at 9:50 AM, Alexander Rabtchevich wrote: > Hello > > Yesterday I almost lost a three-years work. I selected 4-stars images since > 2015 in lighttable and started to type image resolution in export settings. > Cursor shifted a little from the control window due to mouse movement

Re: [darktable-dev] possible data loss scenario

2017-10-09 Thread Moritz Moeller
On 09.10.17 08:50, Alexander Rabtchevich wrote: Yesterday I almost lost a three-years work. [...] > If the mouse had shifted when I had been typing 1, I would not be able to recognize my selected works from 3 years anymore. So you are saying you do not have a backup? .mm _

[darktable-dev] possible data loss scenario

2017-10-08 Thread Alexander Rabtchevich
Hello   Yesterday I almost lost a three-years work. I selected 4-stars images since 2015 in lighttable and started to type image resolution in export settings. Cursor shifted a little from the control window due to mouse movement and dt recognized typed digit as a rating number. For my luck it wa