multibuttonentry really didnt follow elm conventions - it didnt use
namespacing for most singals/swallows - it dug into objects reading
object part geometry where it just should have calced min size and be
done. it did all sorts of other things it shouldnt/didnt need to.. so
i fixed that now... and dark theme has the support.
1. Do not need to print the same error message from all the widget codes.
2. Even though elm_widget_sub_object_add() can be used internally, there should be no error message at all.
Elm devs should fix it beforehand.
So it looks ok to print the error message in elm_widget_sub_object_add() to force elm devs to fix it.
3. Got additional code cleanups.
Smart data is already initialized so we do not need to re-initialize them if the value equals to 0, NULL, or EINA_FALSE.
Sometimes re-initializing smart data explicitly is needed for readability. So there are left overs.
SVN revision: 82228
+ elm_access_object_register();
+ elm_access_object_unregister();
+ elm_access_text_set();
+ elm_access_text_get();
+ elm_access_cb_set();
These APIs are to use edje part, evas object as an accessible object.
and do not create access object, because access object would be created at run time.
This is different with internal API _elm_access_object_register();
SVN revision: 81659
Subject: [E-devel] [patch][elementary] multibuttonentry - access feature
i have attached a patch which has access feature for the multibuttonentry.
it was hard time to implement access feature on the multibuttonentry than
others.
SVN revision: 77738
Subject: [E-devel] [Patch] multibuttonentry - data corruption issue of
the box list
here is a problem in the data corruption of the box list in
_box_layout_cb() of the multibuttonentry.
EINA_LIST_FOREACH is used to move and resize the objects.
but if box unpack/pack is called in the EINA_LIST_FOREACH loop,
the data of the box list will be corrupted.
This problem can not be solved immediately due to the structural
problems of
the MBE.
So the attached patch, a workaround, avoids calling unpack/pack in the
EINA_LIST_FOREACH loop.
I am in the process of refactoring MBE but in the mean time,
this patch will resolve the above issue.
SVN revision: 77192
Subject: [E-devel] [Patch] elc_multibuttonentry resize patch.
Currently, there is a problem in the logic of getting the size in the
MBE's
box.
For each line, the height of the line is calculated according to the
biggest
item's height
and is applied to the box size, but problem occurs when the newly added
item's height is larger than the one before.
For example, when the entry is located in the front of the last line,
the line's height is determined by the entry.
When the button is added by the user's input at this state,
because button's height is larger than the entry's height
I have modified each line to have the equal height.
SVN revision: 75453
Dear, all
I've attached a patch that fixed the memory leak.
There is not a free() in _del_hook().
Please review this patch.
Sincerely yours,
Jihyeon Seol
Signed-Off-By: JiHyeon Seol<jiheyon.seol@samsung.com>
SVN revision: 75439
Subject: [E-devel] [E-deve] [Patch] Add new apis for editable set/get
in multibuttonentry
Typically multibuttonentry is used as a composer.
But sometimes, Multibuttonentry can be used as a viewer.
Currently there is no way to use multibuttonentry as non-editable
viewer.
So I added new APIs which are elm_multibuttonentry_editable_set/get().
If editable is true, entry in multibuttonentry is activated and user can
compose item by pressing the return key.
If not, entry is hidden and muttibuttonentry works as a non-editable
viewer.
SVN revision: 73223
Subject: [E-devel] [?Patch]elm_?multibutto?nentry bug fix
I've attached patch to fix bug in multibuttonentry.
When this widget is unfocused, there's no code for making unfocused
entry in multibuttonentry.
Because of that, when multibuttonentry got focus again, entry couldn't
get focus normally.
so I've added code to fix this issue. when it's unfocused.
Also I removed unused value in resize_button() which is 'padding_inner'
SVN revision: 69583