hooks.
The former is now issued for all scrollables, with the behavior it had
before, and the latter is a new virtual base function, with a default
implementation leading to values matching the old case where one
didn't implement the hook.
Please help me test if everything is OK -- it seems so, here.
SVN revision: 75904
We had an inconsistency of two missing getters, that would "leak" API
deprecation on specialized scrollers (scrollables). Putting them in
for good now.
SVN revision: 73540
Its API will be the the common one on ALL scrollable widgets, too.
Any scrollable widget having a function behaviour clashing with one of
the elm_scroller_* will be marked as DEPRECATED from now on.
SVN revision: 73309
using elm_widget_focus_direction_go function, focus will be moved from
the current focused object to the near object in one direction.
Direction can be set by degree(for easy usability). Degree changes
clockwise, i.e. 0 means UP, 90 means RIGHT, 180 means DOWN, and 270
means LEFT. You can select any direction by changing this degree.
SVN revision: 70681
Previous part names are just the swallow part names
but in modified version, the part names chaned to simpler meaning names to use.
i.e for button
elm_object_content_part_set(button, "elm.swallow.icon", icon);
-> elm_object_content_part_set(button, "icon", icon);
SVN revision: 65295
Subject: [E-devel] [patch] elm_scroller - add gravity functionality
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.
SVN revision: 64073
fix two bugs - use elm_smart_scroller_edje_object_get in case of edje object
fix conditional statement when parameter is 0 in
elm_smart_scroller_page_show,
elm_smart_scroller_page_bring_in
SVN revision: 64010
I added 4 APIs for the page function of the scroller.
Those are,
EAPI void elm_scroller_current_page_get(Evas_Object *obj, int
*h_pagenumber,
int *v_pagenumber));
(Get scroll current page number.)
EAPI void elm_scroller_last_page_get(Evas_Object *obj, int
*h_pagenumber,
int *v_pagenumber);
(Get scroll last page number.)
EAPI void elm_scroller_page_show(Evas_Object *obj, int
h_pagenumber, int
v_pagenumber);
(Show a specific virtual region within the scroller content
object by page
number without animation.)
EAPI void elm_scroller_page_bring_in(Evas_Object *obj, int
h_pagenumber, int
v_pagenumber);
(Show a specific virtual region within the scroller content
object by page
number with animation.)
SVN revision: 62496
Revert "Elementary scroller: Fixed an issue in scroller. When a resize happens (or any change for that matter), we should go to the last "asked for" location. This for example fixes an issue with elm_scrolled_entry (and many other widgets) showing "empty regions" on some resizes."
This reverts commit f322bd28101518849c53e6d56b93c206e4129162.
SVN revision: 56282
Subject: [E-devel] [PATCH] elm scroller, scrolled entry: events
propagation, min size
It's not possible to connect event handler such as
EVAS_CALLBACK_KEY_UP to
elm_scrolled_entry because the scroller inside the scrolled entry does
not
propagate events. So this is the patch for adding events propagation set
function to scroller and setting it to EINA_TRUE in elm scrolled entry.
And one more thing in scrolled entry, while evaluating its size,
scrolled
entry does not consider its min size.
(It just refers to the min size of its scroller object instead of
scrolled
entry object.)
So here in the attached patch, scrolled entry compares its min size to
the
min size of the scroller object and set the bigger one to its min size
to
keep the min size set by intent.
looks good - some mistakes you made. you forgot the patch that adds
elm_scroller_propagate_events_set() to Elementary.h.in .... i added it
for
you. but remember to include it in your patch next time. Also the
documentation could be a LOT better! i fixed that for you too. also -
you
could have added a elm_scroller_propagate_events_get(). i added that
too for
you. oh.. and you didn't use ELM_CHECK_WIDTYPE().
SVN revision: 55609
If you try to create a new widget, you must be sure that the parent
is really an evas object.
With the previous implementation it was possible to call an _add
function for an elementary widget with any non-null pointer as parent
eventually causing crashes (like with the elm_box).
SVN revision: 55521
elm_scroller_policy_get was not verifying if its parameters are null.
elm_scroller_region_get was not getting the y if you pass x = null
and y != null
SVN revision: 54987
As I’ve talked to you just before, I’m sending you the patch file for
applying max size in sizing_eval function in the scroller.
This patch will work in the case below
- elm_scroller_content_min_limit() function is set to 1 (either
width or height)
- the content’s min size is growing up unlimitedly (such as
entry case)
Then the min size of the scroller cannot exceed the max size of itself.
(if we let it be grown up to the content’s min size, there is no way
to limit the size of the scroller and to enable scrolling.)
Please consider this way to avoid failure case (min is greater than
max) in the sizing_eval function,
and give me a feedback if it doesn’t meet any other requirement.
Thank you.
P.S.) patch file was created based on Rev. 54766.
SVN revision: 54978
Gustavo Lima Chaves
WooHyun Jung
Carsten Haitzler
Jihoon Kim
Jiyoun Park
ChunEon Park
Daniel Juyung Seo
Hyoyoung Chang
Mike McCormack
김재환
Jonas M. Gastal
Tom Hacohen
Myungjae Lee
3v1n0
helen
Tiago Rezende Campos Falcao
Bruno Dilly
Iván Briano