raster pushed a commit to branch master.
commit 9e05a6beea55e53ff67904a8d5ccbd15395b7a21
Author: Carsten Haitzler (Rasterman) <[email protected]>
Date: Mon Aug 5 11:51:29 2013 +0900
dont assume ethumb daemons are always around AND connected to. wrong.
---
src/bin/ephoto.c | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/src/bin/ephoto.c b/src/bin/ephoto.c
index 5a8fe22..051253c 100644
--- a/src/bin/ephoto.c
+++ b/src/bin/ephoto.c
@@ -42,6 +42,12 @@ elm_main(int argc, char **argv)
if (!efreet_mime_init())
ERR("Could not init efreet_mime!");
+/*
+ * this isn't valid to assume oan ethumbd is ALWAYS around and ALWAYS
+ * connected - especially on startup. ethumbd may go away (timeout) and
+ * thus the client connection may go. if you want to do this kind of thing,
+ * you will need to extend elm_thumb itself to store these and "implement"
+ * them on connect
client = elm_thumb_ethumb_client_get();
if (!client)
{
@@ -52,7 +58,7 @@ elm_main(int argc, char **argv)
ethumb_client_crop_align_set(client, 0.5, 0.5);
ethumb_client_aspect_set(client, ETHUMB_THUMB_CROP);
ethumb_client_orientation_set(client, ETHUMB_THUMB_ORIENT_ORIGINAL);
-
+ */
elm_policy_set(ELM_POLICY_QUIT, ELM_POLICY_QUIT_LAST_WINDOW_CLOSED);
DBG("Logging initialized");
--
------------------------------------------------------------------------------
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