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 <alexander.v.rabtchev...@gmx.net> [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 cursor occasionally leaves the control for some other
control (except label), the latter steals focus and the keyboard input is
not hooked by the original edit control one is actually typing in. If one is
typing digits at that moment, they are interpreted as star rating. If any
images are selected, that rating is mutually applied for them.
If one have selected some images by some search criterion, including rating,
applying wrong star rating can be fully destructive as that cannot be undone
without the full knowledge about the set of affected images and their
initial ratings.
With respect,
Alexander Rabtchevich
Patrick Shanahan wrote:
* Alexander Rabtchevich <alexander.v.rabtchev...@gmx.net> [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:
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
cannot you provide steps and conditions which led to your "almost"
condition that someone may provide a solution? only you can see and
experience what is in front of you, other just have to guess or summons
their crystal balls, or iron or ....
perhaps your methods need examining. the *only* time I recall "almost"
loosing data was when I was being quite foolist and in too much hurry
mode. but I caught myself, re: almost.
and I have "trash" disabled.
I read the list and have read your posts and I have used dt extensively
for several years and cannot recall more than once or twice having the
mouse pointer "wander", but I use a track-ball. Maybe that is the
difference. I did suggest you examine your methods and maybe you can
minimize or stop the "cursor from leaving control" and stop almost losing
data.
and I cannot recall nor see that any "blame" has been assigned you, only a
suggestion that your methods may be suspect. skin thin?
___________________________________________________________________________
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
