Re: [E-devel] Elm: alpha x transparency, incorrect getters for inline windows
On Tue, 4 Oct 2011 13:01:40 -0300 Gustavo Sverzut Barbieri barbi...@profusion.mobi said: Hi all, When we have inlined windows, the alpha_set will apply to win-img_obj. But on alpha_get it will query from win-ee, what's the reasoning in it? Who did it (Raster?), could envision more leftovers? fixed. :) Also, found transparency and since we had alpha and shaped I got really confused. Looking at the code seems that one sets: shaped: einfo-info.mask = ee-engine.x.mask; transparent: einfo-info.destination_alpha = transparent; alpha: einfo-info.destination_alpha = alpha; /* with couple of additions before */ Then I wonder why keeping these confusing names? Most code I've seen try alpha, then shaped and they don't even know about transparency. Why not just make ecore_evas_alpha_set() and an auxiliary mode to set possible attempts: ecore_evas_alpha_mode_set(ee, mode): mode is one of: ECORE_EVAS_ALPHA_ARGB = 1 ECORE_EVAS_ALPHA_BITMASK_SHAPED = 2 ECORE_EVAS_ALPHA_SOMETHING_I_DONT_GET_WHAT_TRANSPARENCY_IS = 4 ECORE_EVAS_ALPHA_BEST_EFFORT = 7 /* all of above, default */ then we deprecate the existing apis and keep only these 2, extending the enum as required. i'd actually just like to deprecate shaped entriely. i actually dont know what transparency is either... all i see is alpha :) thats all i care about. :) eventually shape will die... i hope. -- Gustavo Sverzut Barbieri http://profusion.mobi embedded systems -- MSN: barbi...@gmail.com Skype: gsbarbieri Mobile: +55 (19) 9225-2202 -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)ras...@rasterman.com -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Multitouch Not working
OK thank you :) I think we have it all figured out. Thanks again for the help! Regards HariHaraSudhan On Fri, Oct 14, 2011 at 6:38 AM, Park Sung-Jin input.hac...@gmail.com wrote: Hi :) You can find an multitouch version of evdev implementation on the following: http://cgit.freedesktop.org/~tissoire/xf86-input-evdev/ BR, Sung-Jin Park 2011/10/14 HariHara Sudhan h...@emo2.com: Also Sung-Jin, I read in the list, that you had written a patch to get mtdev working with ecore. I could not find a link to that patch, Can you point me to one, please. Regards HariHaraSudhan On Thu, Oct 13, 2011 at 4:21 PM, Park Sung-Jin input.hac...@gmail.com wrote: Event stream between kernel and X server doesn't matter. As I see your X input device configuration, you have only one porinter device. You can get touch events only for a finger which was issued from touchscreen If you want to make your multitouch working on EFL application, you need to rewrite your evdev driver or you need to get multitouch version of evdev driver. As Carsten mentioned earlier, ecore X backend expects mpx-style events. i.e. 3 finger needs 3 slave pointer devices. BR, Sung-Jin Park 2011/10/13 HariHara Sudhan h...@emo2.com: Hi I've attached the evtest output in the file.evtest gives a slotted output from mpx events i suppose. On Thu, Oct 13, 2011 at 3:51 PM, HariHara Sudhan h...@emo2.com wrote: Thanks.Here is the list. ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ touchscreen id=6 [slave pointer (2)] ⎜ ↳ SIGMACHIP USB Keyboard id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Power Button id=7 [slave keyboard (3)] ↳ Video Bus id=8 [slave keyboard (3)] ↳ Power Button id=9 [slave keyboard (3)] ↳ SIGMACHIP USB Keyboard id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=12 [slave keyboard (3)] and FYI the device path for touchscreen is /dev/input/by-id/usb-Hanvon_10.1-event-if00. Regards HariHaraSudhan On Thu, Oct 13, 2011 at 3:39 PM, Park Sung-Jin input.hac...@gmail.com wrote: Hi, Could you share your X input device configuration? Just the result of xinput list will be okay and it'll be helpful. : ) BR, Sung-Jin Park 2011/10/13 HariHara Sudhan h...@emo2.com: Let me rephrase this. I mean i use evdev driver for Hanvon device, evdev receives the events, but for some reason the efl is not getting the touch events. Now that you've confirmed that efl multitouch does work. I am worried it could be something with xorg. It would be great to get a xorg.conf file that works well. Just to understand what I am doing wrong. evdev and XI2 work well while doing manual tests. BR Hari On Thu, Oct 13, 2011 at 1:44 PM, HariHara Sudhan h...@emo2.com wrote: Hi, I'm using Hanvon Driver and use evdev for receiving events. evdev receives the events and processing touch events. I think xorg.conf is not configured properly for evdev. That might be the case. It'll be helpful if you can send a copy of xorg.conf for reference. On Wed, Oct 12, 2011 at 4:54 PM, Carsten Haitzler ras...@rasterman.com wrote: On Wed, 12 Oct 2011 14:00:55 +0530 HariHara Sudhan h...@emo2.com said: Hi all, EVAS_CALLBACK_MULTI_DOWN is not calling the appropriate function, I've xinput 2.1 which works perfectly on xinput --test and getting the events. I've tried both the release version and latest from the svn, but still i'm having the same problem. The multi-touch from elementary-tests shows only one touch point being clicked, though i place two fingers on canvas. Any solution? ecore-x handles the x - evas event stream and ecore-x looks at mpx-style multi touch events. works with the drivers i have here - though they are specifically implemented to support the exact hardware. -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler) ras...@rasterman.com -- Regards HariHaraSudhan -- Regards HariHaraSudhan -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net
Re: [E-devel] Question about event propagation routine of elm_scroller
On Thu, 13 Oct 2011 02:19:09 + (GMT) EunMi Lee eunmi15@samsung.com said: h. this is actually an interesting one. evas has some cool mechanisms that are used to make events reroute all over the place. what scroller does is this in objects stacking: = scroller --- --- - -- objects under scroller the scroller has an invisible rectangle that repeats events (repeat == object on top gets event then repeats the events to the next object down until either no object exists or some object swallows the event without repeating). so the event goes FIRST (in order of object stacking from top to bottom) to the scroller, then drops through to objects below (inside the scroller) Hello all, I have a question about event propagation routine among Evas_Object specially elm_scroller. I made an application which has Evas_Objects as follows: my object - elm_layout - elm_box - elm_scroller - elm_navibar (- means : left is contained to right) I expect that event is propagated from child to parent, but event propagation routine is as follows: elm_scroller - elm_navibar - my object - elm_layout - elm_box (- means : left object gets event early) Why elm_scroller always get event firstly even though it has child? I want to not propagate event to the elm_scroller using EVAS_EVENT_FLAG_ON_HOLD if my object consumes event. but I can not do that because elm_scroller gets event earlier than my object. If elm_scroller's event routine is correct, is there any other solution? (additional information: my object is not an elementary widget. it is just an Evas_Object.) Regards, Eunmi Lee -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)ras...@rasterman.com -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] [patch] elm_scroller - add gravity functionality
On Tue, 11 Oct 2011 19:38:09 +0900 Hyoyoung Chang hyoyoung.ch...@samsung.com said: reviewed! in svn it goes! :) good stuff! Dear developers. I made a gravity features for stopping scroller. Elm_scroller's fixed when child's growing lower. However if scroller's child is growing upper, the elm_scroller always moving and waving to upper direction. Because elm_scroller sets internal pan to keep current virtual position. Gravity functions introduce to stopping scroller. @doc * It set scrolling gravity. It adds scrolling weight values * to the scroller. Usually it uses for stopping the scroller. * To set y as 0.0 for lower growing child objects, * even though child objects are added to bottom, the scroller doesn't move. * To set y as 1.0 for upper growing child objects. And x is horizontal gravity. * By default 0.0 for x and y. @doc Thank you. -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)ras...@rasterman.com -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] elm_segment_control patch for enable/disable issue fix.
On Fri, 14 Oct 2011 06:20:00 + (GMT) PRINCE KUMAR DUBEY prince.du...@samsung.com said: thanks! short and simple! in svn! :) Hi , Can someone review and commit the attached segment control patch. Change Description: [Issue-Fixed] After disable, on enabling, the segment control, segment item's image remains of disable type. Thanks, Prince [cid:A6X7LP7KBSL8@namo.co.kr] [SeenTimeChecker? do=4c27f84bc5600e2e2d3b2dc4c7219ffd45a5d34f6725e6ed2f03c9b1 9f0b6f57ba777c355c197185c465c2cf80a2b7ef9aba4bb3b2b5ca43ddd7e184e0604d958075 b6b33f32d245b7f8aafe245478a5f1d21d5ebee74427cf878f9a26ce15a0] -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)ras...@rasterman.com -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Question about event propagation routine of elm_scroller
Thank you for your explaination :) I understand why scroller always gets event firstly. so, evas_object_propagate_events_set(scroller's content obj, EINA_FALSE) and event_flags |= EVAS_EVENT_FLAG_ON_HOLD in the scroller's content obj will not work! I'm sorry about that T_T I have to find other solution to stop scroller. --- Original Message --- Sender : Carsten Haitzlerras...@rasterman.com Date : 2011-10-14 19:10 (GMT+09:00) Title : Re: [E-devel] Question about event propagation routine of elm_scroller On Thu, 13 Oct 2011 02:19:09 + (GMT) EunMi Lee said: h. this is actually an interesting one. evas has some cool mechanisms that are used to make events reroute all over the place. what scroller does is this in objects stacking: = scroller --- --- - -- objects under scroller the scroller has an invisible rectangle that repeats events (repeat == object on top gets event then repeats the events to the next object down until either no object exists or some object swallows the event without repeating). so the event goes FIRST (in order of object stacking from top to bottom) to the scroller, then drops through to objects below (inside the scroller) Hello all, I have a question about event propagation routine among Evas_Object specially elm_scroller. I made an application which has Evas_Objects as follows: my object - elm_layout - elm_box - elm_scroller - elm_navibar (- means : left is contained to right) I expect that event is propagated from child to parent, but event propagation routine is as follows: elm_scroller - elm_navibar - my object - elm_layout - elm_box (- means : left object gets event early) Why elm_scroller always get event firstly even though it has child? I want to not propagate event to the elm_scroller using EVAS_EVENT_FLAG_ON_HOLD if my object consumes event. but I can not do that because elm_scroller gets event earlier than my object. If elm_scroller's event routine is correct, is there any other solution? (additional information: my object is not an elementary widget. it is just an Evas_Object.) Regards, Eunmi Lee -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)ras...@rasterman.com -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] two small fixes for mail module
Hi On Thu, Oct 13, 2011 at 6:27 PM, Tomas Cech tc...@suse.cz wrote: Hi, On Wed, Oct 12, 2011 at 01:06:01AM +0200, Tomas Cech wrote: Hi, there are two small issues with mail module. Patches attached. Is there any problem with applying these two patches? I believe they're trivial enough for accept. One typo and one initialization of variable... I'm going to apply them. Lucas De Marchi -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] two small fixes for mail module
On Tue, Oct 11, 2011 at 8:06 PM, Tomas Cech tc...@suse.cz wrote: Hi, there are two small issues with mail module. Patches attached. in svn. Thanks Lucas De Marchi -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] E SVN: raster trunk/ecore/src/lib/ecore_evas
I'm on the road (actually about to get into a plane), would you apply this
to EWS engine as well? It's basically a copy of buffer with few changes
On Friday, October 14, 2011, Enlightenment SVN no-re...@enlightenment.org
wrote:
Log:
1. make inline image ee buffer non-alpha by default. thats the default
for all eee's. this was wrong.
2. make sure it sets back data when finished - check data in and check
it out.
Author: raster
Date: 2011-10-14 00:28:45 -0700 (Fri, 14 Oct 2011)
New Revision: 64069
Trac: http://trac.enlightenment.org/e/changeset/64069
Modified:
trunk/ecore/src/lib/ecore_evas/ecore_evas_buffer.c
Modified: trunk/ecore/src/lib/ecore_evas/ecore_evas_buffer.c
===
--- trunk/ecore/src/lib/ecore_evas/ecore_evas_buffer.c 2011-10-14
07:23:09 UTC (rev 64068)
+++ trunk/ecore/src/lib/ecore_evas/ecore_evas_buffer.c 2011-10-14
07:28:45 UTC (rev 64069)
@@ -86,6 +86,8 @@
ERR(evas_engine_info_set() for engine '%s' failed.,
ee-driver);
}
}
+ if (ee-engine.buffer.image)
+ evas_object_image_data_set(ee-engine.buffer.image,
ee-engine.buffer.pixels);
if (ee-func.fn_resize) ee-func.fn_resize(ee);
}
@@ -93,9 +95,6 @@
_ecore_evas_buffer_shutdown(void)
{
_ecore_evas_init_count--;
- if (_ecore_evas_init_count == 0)
- {
- }
if (_ecore_evas_init_count 0) _ecore_evas_init_count = 0;
return _ecore_evas_init_count;
}
@@ -111,7 +110,7 @@
{
if (ee2-func.fn_pre_render) ee2-func.fn_pre_render(ee2);
if (ee2-engine.func-fn_render)
- rend |= ee2-engine.func-fn_render(ee2);
+ rend |= ee2-engine.func-fn_render(ee2);
if (ee2-func.fn_post_render) ee2-func.fn_post_render(ee2);
}
if (ee-engine.buffer.image)
@@ -120,16 +119,18 @@
evas_object_image_size_get(ee-engine.buffer.image, w, h);
if ((w != ee-w) || (h != ee-h))
- _ecore_evas_resize(ee, w, h);
+ _ecore_evas_resize(ee, w, h);
+ee-engine.buffer.pixels =
evas_object_image_data_get(ee-engine.buffer.image, 1);
}
updates = evas_render_updates(ee-evas);
if (ee-engine.buffer.image)
{
Eina_Rectangle *r;
+evas_object_image_data_set(ee-engine.buffer.image,
ee-engine.buffer.pixels);
EINA_LIST_FOREACH(updates, l, r)
- evas_object_image_data_update_add(ee-engine.buffer.image,
-r-x, r-y, r-w, r-h);
+ evas_object_image_data_update_add(ee-engine.buffer.image,
+ r-x, r-y, r-w, r-h);
}
if (updates)
{
@@ -451,6 +452,8 @@
{
if (((ee-alpha) (alpha)) || ((!ee-alpha) (!alpha))) return;
ee-alpha = alpha;
+ if (ee-engine.buffer.image)
+ evas_object_image_alpha_set(ee-engine.buffer.image, ee-alpha);
}
static Ecore_Evas_Engine_Func _ecore_buffer_engine_func =
@@ -662,7 +665,7 @@
Evas_Engine_Info_Buffer *einfo;
Ecore_Evas *ee;
int rmethod;
- int w, h;
+ int w = 1, h = 1;
rmethod = evas_render_method_lookup(buffer);
if (!rmethod) return NULL;
@@ -672,6 +675,8 @@
o = evas_object_image_add(ee_target-evas);
evas_object_image_content_hint_set(o, EVAS_IMAGE_CONTENT_HINT_DYNAMIC);
evas_object_image_colorspace_set(o, EVAS_COLORSPACE_ARGB);
+ evas_object_image_alpha_set(o, 0);
+ evas_object_image_size_set(o, w, h);
ECORE_MAGIC_SET(ee, ECORE_MAGIC_EVAS);
@@ -681,8 +686,6 @@
ee-driver = buffer;
- w = 1;
- h = 1;
ee-rotation = 0;
ee-visible = 0;
ee-w = w;
@@ -709,10 +712,6 @@
ee-engine.buffer.image = o;
evas_object_data_set(ee-engine.buffer.image, Ecore_Evas, ee);
evas_object_data_set(ee-engine.buffer.image, Ecore_Evas_Parent,
ee_target);
- evas_object_image_size_set(o, ee-w, ee-h);
- evas_object_image_alpha_set(o, 1);
- ee-engine.buffer.pixels = evas_object_image_data_get(o, 1);
- evas_object_image_data_set(o, ee-engine.buffer.pixels);
evas_object_event_callback_add(ee-engine.buffer.image,
EVAS_CALLBACK_MOUSE_IN,
_ecore_evas_buffer_cb_mouse_in, ee);
@@ -764,6 +763,7 @@
einfo = (Evas_Engine_Info_Buffer *)evas_engine_info_get(ee-evas);
if (einfo)
{
+ee-engine.buffer.pixels = evas_object_image_data_get(o, 1);
einfo-info.depth_type = EVAS_ENGINE_BUFFER_DEPTH_ARGB32;
einfo-info.dest_buffer = ee-engine.buffer.pixels;
einfo-info.dest_buffer_row_bytes =
evas_object_image_stride_get(o);
@@ -771,6 +771,7 @@
einfo-info.alpha_threshold = 0;
einfo-info.func.new_update_region = NULL;
einfo-info.func.free_update_region = NULL;
+evas_object_image_data_set(o, ee-engine.buffer.pixels);
if (!evas_engine_info_set(ee-evas, (Evas_Engine_Info *)einfo))
{
Re: [E-devel] e17 segfault on fresh install
On Fri, Oct 14, 2011 at 03:18:48PM +1100, Jochen Schröder wrote: Hi all, I just rebuild all of EFL and E17 gives me a segfault when starting with a clean config directory. Seems to be related to the recent sse3 work. What is your compiler version and CFLAGS? The parameters to _mm_set_epi32 look reasonable. The only reason I could imagine this failing is if your compiler isn't aligning things properly. cat /proc/cpuinfo processor : 1 vendor_id : GenuineIntel cpu family: 6 model : 15 model name: Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz stepping : 11 cpu MHz : 1998.000 cache size: 4096 KB physical id : 0 siblings : 2 core id : 1 cpu cores : 2 apicid: 1 initial apicid: 1 fpu : yes fpu_exception : yes cpuid level : 10 wp: yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm lahf_lm dts tpr_shadow vnmi flexpriority bogomips : 4654.98 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: bt attached. Cheers Jochen #0 0x7fa75897cbce in waitpid () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x00435961 in e_alert_show (sig=optimized out) at e_alert.c:57 #2 signal handler called #3 0x7fa75b037cc5 in _mm_set_epi32 (__q0=255, __q1=255, __q2=255, __q3=255) at /usr/lib/gcc/x86_64-linux-gnu/4.6/include/emmintrin.h:586 #4 _op_blend_mas_can_dp_sse3 (s=optimized out, m=0x1e7a4e1 \377\377\377\377\377\377, c=4278190080, d=0x7fa74c8b0df0, l=4) at op_blend_mask_color_sse3.c:79 #5 0x7fa75b01c147 in evas_common_font_draw_internal (dst=0x2268b70, dc=0x21c0eb0, x=29, y=12, text_props=0x21c4718, func=0x7fa75b037850 _op_blend_mas_can_dp_sse3, ext_x=29, ext_y=2, ext_w=313, ext_h=15, im_w=377, fn=optimized out, im_h=optimized out) at evas_font_draw.c:298 #6 0x7fa75b01c4cb in evas_common_font_draw (dst=0x2268b70, dc=0x21c0eb0, fn=optimized out, x=29, y=12, text_props=0x21c4718) at evas_font_draw.c:418 #7 0x7fa74f3893ea in eng_font_draw (data=optimized out, context=optimized out, surface=optimized out, font=optimized out, x=optimized out, y=optimized out, w=313, h=15, ow=313, oh=15, text_props=0x21c4718) at evas_engine.c:898 #8 0x7fa75afd609f in evas_object_text_render (obj=0x214e480, output=0x21c1380, context=0x21c0eb0, surface=0x2268b70, x=0, y=0) at evas_object_text.c:1665 #9 0x7fa75afebd3e in evas_render_mapped (e=0x21c37a0, obj=0x214e480, context=0x21c0eb0, surface=0x2268b70, off_x=0, off_y=0, mapped=0, ecx=0, ecy=0, ecw=377, ech=22) at evas_render.c:1256 #10 0x7fa75afeeaf1 in evas_render_updates_internal (e=0x21c37a0, make_updates=1 '\001', do_draw=1 '\001') at evas_render.c:1579 #11 0x7fa75a911d65 in _ecore_evas_x_render (ee=0x21c3580) at ecore_evas_x.c:256 #12 0x7fa75a90f041 in _ecore_evas_idle_enter (data=optimized out) at ecore_evas.c:52 #13 0x7fa75ad6c1de in _ecore_call_task_cb (data=optimized out, func=optimized out) at ecore_private.h:246 #14 _ecore_idle_enterer_call () at ecore_idle_enterer.c:165 #15 0x7fa75ad6daf5 in _ecore_main_loop_iterate_internal (once_only=0) at ecore_main.c:1699 #16 0x7fa75ad6debf in ecore_main_loop_begin () at ecore_main.c:864 #17 0x00433bf7 in main (argc=optimized out, argv=optimized out) at e_main.c:954 quit A debugging session is active. Inferior 1 [process 2371] will be detached. Quit anyway? (y or n) Detaching from program: /opt/e17/bin/enlightenment, process 2371 -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Jim Kukunas Intel Open Source Technology Center -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ enlightenment-devel mailing list
Re: [E-devel] e17 segfault on fresh install
On 14/10/11 19:20, Jim Kukunas wrote: What is your compiler version and CFLAGS? The parameters to _mm_set_epi32 look reasonable. The only reason I could imagine this failing is if your compiler isn't aligning things properly. It's the sse3 issue all over again. As you can see, his CPU doesn't support sse3 but sse3 code is called. FFS, we should either fix this or remove it, but we can't just leave this broken sse3 support as is. It does more harm than good. -- Tom. -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] e17 segfault on fresh install
On Sat, Oct 15, 2011 at 12:54:00AM +0200, Tom Hacohen wrote: On 14/10/11 19:20, Jim Kukunas wrote: What is your compiler version and CFLAGS? The parameters to _mm_set_epi32 look reasonable. The only reason I could imagine this failing is if your compiler isn't aligning things properly. It's the sse3 issue all over again. As you can see, his CPU doesn't support sse3 but sse3 code is called. His CPU does support SSE3, hence the ``pni'' in his /proc/cpuinfo. FFS, we should either fix this or remove it, but we can't just leave this broken sse3 support as is. It does more harm than good. -- Tom. -- Jim Kukunas Intel Open Source Technology Center -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] e17 segfault on fresh install
On Fri, 14 Oct 2011 16:16:44 -0700 Jim Kukunas james.t.kuku...@linux.intel.com said: On Sat, Oct 15, 2011 at 12:54:00AM +0200, Tom Hacohen wrote: On 14/10/11 19:20, Jim Kukunas wrote: What is your compiler version and CFLAGS? The parameters to _mm_set_epi32 look reasonable. The only reason I could imagine this failing is if your compiler isn't aligning things properly. It's the sse3 issue all over again. As you can see, his CPU doesn't support sse3 but sse3 code is called. His CPU does support SSE3, hence the ``pni'' in his /proc/cpuinfo. let's eliminate first shall we. tomas - can you either --disable-cpu-sse3 when configuring evas, OR set EVAS_CPU_NO_SSE3=1 as an env var before running e to see if this is sse3 stuff or not or a more generic problem. -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)ras...@rasterman.com -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] E SVN: raster trunk/ecore/src/lib/ecore_evas
On Fri, 14 Oct 2011 10:01:19 -0300 Gustavo Sverzut Barbieri
barbi...@profusion.mobi said:
done :)
I'm on the road (actually about to get into a plane), would you apply this
to EWS engine as well? It's basically a copy of buffer with few changes
On Friday, October 14, 2011, Enlightenment SVN no-re...@enlightenment.org
wrote:
Log:
1. make inline image ee buffer non-alpha by default. thats the default
for all eee's. this was wrong.
2. make sure it sets back data when finished - check data in and check
it out.
Author: raster
Date: 2011-10-14 00:28:45 -0700 (Fri, 14 Oct 2011)
New Revision: 64069
Trac: http://trac.enlightenment.org/e/changeset/64069
Modified:
trunk/ecore/src/lib/ecore_evas/ecore_evas_buffer.c
Modified: trunk/ecore/src/lib/ecore_evas/ecore_evas_buffer.c
===
--- trunk/ecore/src/lib/ecore_evas/ecore_evas_buffer.c 2011-10-14
07:23:09 UTC (rev 64068)
+++ trunk/ecore/src/lib/ecore_evas/ecore_evas_buffer.c 2011-10-14
07:28:45 UTC (rev 64069)
@@ -86,6 +86,8 @@
ERR(evas_engine_info_set() for engine '%s' failed.,
ee-driver);
}
}
+ if (ee-engine.buffer.image)
+ evas_object_image_data_set(ee-engine.buffer.image,
ee-engine.buffer.pixels);
if (ee-func.fn_resize) ee-func.fn_resize(ee);
}
@@ -93,9 +95,6 @@
_ecore_evas_buffer_shutdown(void)
{
_ecore_evas_init_count--;
- if (_ecore_evas_init_count == 0)
- {
- }
if (_ecore_evas_init_count 0) _ecore_evas_init_count = 0;
return _ecore_evas_init_count;
}
@@ -111,7 +110,7 @@
{
if (ee2-func.fn_pre_render) ee2-func.fn_pre_render(ee2);
if (ee2-engine.func-fn_render)
- rend |= ee2-engine.func-fn_render(ee2);
+ rend |= ee2-engine.func-fn_render(ee2);
if (ee2-func.fn_post_render) ee2-func.fn_post_render(ee2);
}
if (ee-engine.buffer.image)
@@ -120,16 +119,18 @@
evas_object_image_size_get(ee-engine.buffer.image, w, h);
if ((w != ee-w) || (h != ee-h))
- _ecore_evas_resize(ee, w, h);
+ _ecore_evas_resize(ee, w, h);
+ee-engine.buffer.pixels =
evas_object_image_data_get(ee-engine.buffer.image, 1);
}
updates = evas_render_updates(ee-evas);
if (ee-engine.buffer.image)
{
Eina_Rectangle *r;
+evas_object_image_data_set(ee-engine.buffer.image,
ee-engine.buffer.pixels);
EINA_LIST_FOREACH(updates, l, r)
- evas_object_image_data_update_add(ee-engine.buffer.image,
-r-x, r-y, r-w, r-h);
+ evas_object_image_data_update_add(ee-engine.buffer.image,
+ r-x, r-y, r-w, r-h);
}
if (updates)
{
@@ -451,6 +452,8 @@
{
if (((ee-alpha) (alpha)) || ((!ee-alpha) (!alpha))) return;
ee-alpha = alpha;
+ if (ee-engine.buffer.image)
+ evas_object_image_alpha_set(ee-engine.buffer.image, ee-alpha);
}
static Ecore_Evas_Engine_Func _ecore_buffer_engine_func =
@@ -662,7 +665,7 @@
Evas_Engine_Info_Buffer *einfo;
Ecore_Evas *ee;
int rmethod;
- int w, h;
+ int w = 1, h = 1;
rmethod = evas_render_method_lookup(buffer);
if (!rmethod) return NULL;
@@ -672,6 +675,8 @@
o = evas_object_image_add(ee_target-evas);
evas_object_image_content_hint_set(o, EVAS_IMAGE_CONTENT_HINT_DYNAMIC);
evas_object_image_colorspace_set(o, EVAS_COLORSPACE_ARGB);
+ evas_object_image_alpha_set(o, 0);
+ evas_object_image_size_set(o, w, h);
ECORE_MAGIC_SET(ee, ECORE_MAGIC_EVAS);
@@ -681,8 +686,6 @@
ee-driver = buffer;
- w = 1;
- h = 1;
ee-rotation = 0;
ee-visible = 0;
ee-w = w;
@@ -709,10 +712,6 @@
ee-engine.buffer.image = o;
evas_object_data_set(ee-engine.buffer.image, Ecore_Evas, ee);
evas_object_data_set(ee-engine.buffer.image, Ecore_Evas_Parent,
ee_target);
- evas_object_image_size_set(o, ee-w, ee-h);
- evas_object_image_alpha_set(o, 1);
- ee-engine.buffer.pixels = evas_object_image_data_get(o, 1);
- evas_object_image_data_set(o, ee-engine.buffer.pixels);
evas_object_event_callback_add(ee-engine.buffer.image,
EVAS_CALLBACK_MOUSE_IN,
_ecore_evas_buffer_cb_mouse_in, ee);
@@ -764,6 +763,7 @@
einfo = (Evas_Engine_Info_Buffer *)evas_engine_info_get(ee-evas);
if (einfo)
{
+ee-engine.buffer.pixels = evas_object_image_data_get(o, 1);
einfo-info.depth_type = EVAS_ENGINE_BUFFER_DEPTH_ARGB32;
einfo-info.dest_buffer = ee-engine.buffer.pixels;
einfo-info.dest_buffer_row_bytes =
evas_object_image_stride_get(o);
@@ -771,6 +771,7 @@
einfo-info.alpha_threshold = 0;
Re: [E-devel] e_config_dialog
On Fri, 7 Oct 2011 02:55:19 +0200 Leif Middelschulte leif.middelschu...@gmail.com said: 2011/10/6 Christopher Michael cpmicha...@comcast.net: On 10/06/2011 10:10 AM, Leif Middelschulte wrote: Dear ladies and gents, especially devilhorns (as I was told) as many of you know, I'm writing the display configuration dialog for randr=1.2 stuff. While doing so, I wrote an evas smart object, for the monitor arrangement. Now, I face an issue which seems to happen as follows: 1.) e: smart resize events are queued 2.) user: dialog closes dialog 3.) e: free dialog data 4.) e: resize callback gets executed 5.) CRASH! I am not sure about the queuing theory, but am sure that data is freed and resize callback is called afterwards. Am I missing something here? Do I have to destroy the smart object my self within free_data callback? In theory you should not have to. If you can provide some code for your smart object and dialog, I'll take a look. So is there any chance of non-canceled events beeing called? I'll provide the code, as soon as I have talked to raster and did some 'final' adjustments. I don't want to bisect the smart object, so I'll just send you the patch (once it's 'ready') and gdb will guide you to the crashing part ;-) being very vague there. ecore-events never get cancelled. callbacks arent queued. they get called inline. edje signals are queued in a message queue and called in callbacks when processing the queue. can't say much without code + gdb/valgrind :) -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)ras...@rasterman.com -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Question about event propagation routine of elm_scroller
On Fri, 14 Oct 2011 11:08:16 + (GMT) EunMi Lee eunmi15@samsung.com said: Thank you for your explaination :) I understand why scroller always gets event firstly. so, evas_object_propagate_events_set(scroller's content obj, EINA_FALSE) and event_flags |= EVAS_EVENT_FLAG_ON_HOLD in the scroller's content obj will not work! I'm sorry about that T_T I have to find other solution to stop scroller. can you explain in detail what you are trying to do? elm does this kind of thing when you put a scroller inside a scroller... --- Original Message --- Sender : Carsten Haitzlerras...@rasterman.com Date : 2011-10-14 19:10 (GMT+09:00) Title : Re: [E-devel] Question about event propagation routine of elm_scroller On Thu, 13 Oct 2011 02:19:09 + (GMT) EunMi Lee said: h. this is actually an interesting one. evas has some cool mechanisms that are used to make events reroute all over the place. what scroller does is this in objects stacking: = scroller --- --- - -- objects under scroller the scroller has an invisible rectangle that repeats events (repeat == object on top gets event then repeats the events to the next object down until either no object exists or some object swallows the event without repeating). so the event goes FIRST (in order of object stacking from top to bottom) to the scroller, then drops through to objects below (inside the scroller) Hello all, I have a question about event propagation routine among Evas_Object specially elm_scroller. I made an application which has Evas_Objects as follows: my object - elm_layout - elm_box - elm_scroller - elm_navibar (- means : left is contained to right) I expect that event is propagated from child to parent, but event propagation routine is as follows: elm_scroller - elm_navibar - my object - elm_layout - elm_box (- means : left object gets event early) Why elm_scroller always get event firstly even though it has child? I want to not propagate event to the elm_scroller using EVAS_EVENT_FLAG_ON_HOLD if my object consumes event. but I can not do that because elm_scroller gets event earlier than my object. If elm_scroller's event routine is correct, is there any other solution? (additional information: my object is not an elementary widget. it is just an Evas_Object.) Regards, Eunmi Lee -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)ras...@rasterman.com -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)ras...@rasterman.com -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] e17 segfault on fresh install
On Sat, 15 Oct 2011, Tom Hacohen wrote: On 14/10/11 19:20, Jim Kukunas wrote: What is your compiler version and CFLAGS? The parameters to _mm_set_epi32 look reasonable. The only reason I could imagine this failing is if your compiler isn't aligning things properly. It's the sse3 issue all over again. As you can see, his CPU doesn't support sse3 but sse3 code is called. raster told me that there is a check of sse3 availability at runtime. Maybe the check is buggy Vincent FFS, we should either fix this or remove it, but we can't just leave this broken sse3 support as is. It does more harm than good. -- Tom. -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] e17 segfault on fresh install
On 10/15/2011 01:37 PM, Carsten Haitzler (The Rasterman) wrote: On Fri, 14 Oct 2011 16:16:44 -0700 Jim Kukunas james.t.kuku...@linux.intel.com said: On Sat, Oct 15, 2011 at 12:54:00AM +0200, Tom Hacohen wrote: On 14/10/11 19:20, Jim Kukunas wrote: What is your compiler version and CFLAGS? The parameters to _mm_set_epi32 look reasonable. The only reason I could imagine this failing is if your compiler isn't aligning things properly. It's the sse3 issue all over again. As you can see, his CPU doesn't support sse3 but sse3 code is called. His CPU does support SSE3, hence the ``pni'' in his /proc/cpuinfo. let's eliminate first shall we. tomas - can you either --disable-cpu-sse3 when configuring evas, OR set EVAS_CPU_NO_SSE3=1 as an env var before running e to see if this is sse3 stuff or not or a more generic problem. I assume you mean me not Tomas, as I reported the segfault. This was on my PC at work so it will have to wait until Monday. This is a Core 2 Duo, which AFAIK does support SSE3 (wikipedia says SSE3 was introduced with Prescott). Cheers Jochen -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] e17 segfault on fresh install
On Sat, 15 Oct 2011 16:13:07 +1100 Jochen Schröder cycoma...@gmail.com wrote: On 10/15/2011 01:37 PM, Carsten Haitzler (The Rasterman) wrote: On Fri, 14 Oct 2011 16:16:44 -0700 Jim Kukunas james.t.kuku...@linux.intel.com said: On Sat, Oct 15, 2011 at 12:54:00AM +0200, Tom Hacohen wrote: On 14/10/11 19:20, Jim Kukunas wrote: What is your compiler version and CFLAGS? The parameters to _mm_set_epi32 look reasonable. The only reason I could imagine this failing is if your compiler isn't aligning things properly. It's the sse3 issue all over again. As you can see, his CPU doesn't support sse3 but sse3 code is called. His CPU does support SSE3, hence the ``pni'' in his /proc/cpuinfo. let's eliminate first shall we. tomas - can you either --disable-cpu-sse3 when configuring evas, OR set EVAS_CPU_NO_SSE3=1 as an env var before running e to see if this is sse3 stuff or not or a more generic problem. I assume you mean me not Tomas, as I reported the segfault. This was on my PC at work so it will have to wait until Monday. This is a Core 2 Duo, which AFAIK does support SSE3 (wikipedia says SSE3 was introduced with Prescott). It did say ssse3 in your flags, just not straight after sse2, it's two lines further down. flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm lahf_lm dts tpr_shadow vnmi flexpriority Dunno about that extra 's' though. For what it's worth, mine says sse4a later in the flags after sse2, but no sse3. -- A big old stinking pile of genius that no one wants coz there are too many silver coated monkeys in the world. signature.asc Description: PGP signature -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
