Hello 이명재,

Index: src/lib/elm_entry.c
===================================================================
--- src/lib/elm_entry.c (revision 65568)
+++ src/lib/elm_entry.c (working copy)
@@ -579,6 +579,7 @@ _recalc_cursor_geometry(Evas_Object *obj)
         Evas_Coord cx, cy, cw, ch;
         edje_object_part_text_cursor_geometry_get(wd->ent, "elm.text",
                                                   &cx, &cy, &cw, &ch);
+        printf("[%s::%d] cx(%d) cy(%d) cw(%d) ch(%d) \n", __func__, __LINE__, 
cx, cy, cw, ch);
         if (wd->cur_changed)
           {
              elm_widget_show_region_set(obj, cx, cy, cw, ch, EINA_FALSE);

Is there some need to add printfs here?  How about removing them or using the 
EINA logging mechanism?

thanks,

Mike


On 11/25/2011 09:17 AM, 이명재 wrote:
> Dear, Tom, Raster and EFL people.
> 
> After applying the previous changeset 64721, the cursor geometry is wrong
> in a char-wrapped or a mixed mode entry contented in a scroller (not a
> scrolled entry).
> In other words, a word-wrapped entry or a scrolled entry (when
> elm_entry_scrollable_set is set to TRUE) doesn't have this problem.
> 
> Because the cursor geometry that comes from the
> evas_textblock_cursor_geometry_get function(en->cursor, ...) is wrong (w is
> fixed to small value and h is getting bigger when text is written
> horizontally), when we type texts into the entry near the top lines, entry
> is scrolled to the bottom lines.
> 
> Please apply attached patch file, "entry_test.patch.txt" (patch to
> elm_entry.c and test_entry.c files) and see what happens in the below test
> path.
> 
> Test path : 'Elementary Test' -> 'Entry 5' -> Insert any text into the 1st
> line
> Result : Entry is scrolled to the bottom line so inserted texts in the 1st
> line are not shown until entry is scrolled to the top
> 
> 
> I also attached a quick patch for this problem. ("elm_entry.patch.txt")
> In the patch file, I just changed the order of these 2 function calls and
> now it works fine in all line wrapping mode.
> 
>    edje_object_size_min_restricted_calc(wd->ent, &fw, &fh, 0, 0);
>    edje_object_size_min_restricted_calc(wd->ent, &minw, &minh, resw, 0);
> 
> It's really weird that changing the order of calling
> 'edje_object_size_min_restricted_calc' functions affects the size of
> textblock cursor geometry in entry.
> 
> Please look into this bug and if you find the main problem on textblock's
> side, please fix it.
> 
> If it takes time to fix this, please apply the attached quick patch file
> and fix it when you're available because we have some scroll issues with
> entry in scroller here at this moment.
> 
> Thank you.
> 
> 
> 
> ------------------------------------------------------------------------------
> 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. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
> 
> 
> 
> _______________________________________________
> enlightenment-devel mailing list
> [email protected]
> 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. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to