On Thu, Apr 9, 2009 at 3:00 PM, Sergey Semernin <sergey.semer...@gmail.com> wrote: > Hello, All. > > As I see only TEXTBLOCK element have property 'entry_mode', to set it editable > or no. This is using in elm_entry.c. > Many other widgets contain TEXT element, such as 'e.text.label', but seems no > similar property in it. Therefore, no basic callbacks are initialized when > creating. And no way to change entry_mode in runtime. > What shall I do? Simply make 'e.text.label' to TEXTBLOCK type? Or any else is > possible? For example make similar callbacks for 'e.text.label' when edit, > but this is a lot of duplicate code...
just change it to textblock, add new signals to make it editable (enter edit mode). You can choose to when the signal to become editable is sent to edje object you hide the TEXT part and show a new one with TEXTBLOCK already in edit mode. > Second. Is acceptable to enable/disable accepting message events by parts of > widget runtime (via edje_edit_part_mouse_events_set)? no, do not use any of edje_edit api outside edje-editor (or similar) applications. you should create a transparent rectangle on top with mouse_events:1 on TOP. make it visible:1 when you want to block events, visible:0 when you want to stop (as invisible objects will not get events). -- Gustavo Sverzut Barbieri http://profusion.mobi embedded systems -------------------------------------- MSN: barbi...@gmail.com Skype: gsbarbieri Mobile: +55 (19) 9225-2202 ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
