Re: [darktable-dev] possible data loss scenario

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,

Re: [darktable-dev] possible data loss scenario

* 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

Re: [darktable-dev] possible data loss scenario

* 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

Re: [darktable-dev] possible data loss scenario

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

Re: [darktable-dev] possible data loss scenario

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