On 19/10/12 09:29 PM, Tobias Ellinghaus wrote:
> Am Freitag, 19. Oktober 2012, 12:10:31 schrub Christian Tellefsen:
...
>> Sqlite already detects that another process has locked the library.
>> It prints a bunch of warnings to console, but dt continues to work.
>>
>> I see two approaches:
>> a) exit darktable with an error complaining there's already an instance
>> running
>
> FIXED
An alternative is to pop up a message box with a slap:
Hey bozo, you've left darktable running in the corner, with pid $X.
No changes you make in this session will be written to the database.
HTH, YMMV, kthxbai
or something :)
>> b) switch to the already running darktable process (like lots of other
>> software, e.g. Firefox)
>
> That will need some IPC. Some day I will add DBUS support to darktable ...
ugh, please don't - it violates the principle of least surprise.
Much, much better to exit with a warning.
cheers,
James
--
Solaris kernel software engineer, system admin and troubleshooter
http://www.jmcpdotcom.com/blog
Find me on LinkedIn @ http://www.linkedin.com/in/jamescmcpherson
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
darktable-devel mailing list
darktable-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/darktable-devel
