The accidental massive deleting thing can be avoided by deleting the hotkey
assigned to it. The problem with the size in the export module can be at
least partially solved by creating export presets and then select the
preset just before hitting the export button. But just to say I have never
had an issue as these described here, but been frustrated with some other
software, so I can understand these complaints.
El 01/08/2013 07:51, "Aahz Maruch" <[email protected]> escribió:
> On Wed, Jul 31, 2013, Patrick Shanahan wrote:
> >
> > Many undesirable things can and will happen if you are not thinking about
> > what you are doing. And it is necessary to understand the operation of
> > the software you are using. But this is universal, would you prefer the
> > windoz way, question: "Do you really want to do <what-ever>?", at every
> > step of the way?
>
> You are presenting a false dichotomy.
>
> > It is *my* job to know what I am doing, and my expectation that the
> > software will operate in an expected, consistant fashion.
>
> It's also the responsibility of the software to provide the information
> you need to keep track of everything. If you look at various studies,
> they show that people keep 3-7 items in "working memory"; software should
> be designed with that limit in mind, skewed toward the lower end because
> each person is likely thinking about different things during their
> workflow.
>
> Several people have pointed out that Darktable is already not consistent,
> neither with other software nor internally (particularly with the
> surprising hover behavior). The question is how to provide useful
> consistency. Remember:
>
> "A foolish consistency is the hobgoblin of little minds, adored by little
> statesmen and philosophers and divines." --Ralph Waldo Emerson
> --
> Hugs and backrubs -- I break Rule 6
> http://rule6.info/
> <*> <*> <*>
> Help a hearing-impaired person: http://rule6.info/hearing.html
>
>
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent
> caught up. So what steps can you take to put your SQL databases under
> version control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
> _______________________________________________
> Darktable-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/darktable-users
>
------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
Darktable-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/darktable-users
