Dear All, Hello!
The transition effect is added to the ctxpopup when it comes.
Please review the attached patch. Thanks always!
Sincerely,
Shinwoo Kim.
SVN revision: 62735
Dear All, Hi!
Previously, the ctxpopup have used only direction up or down if there is no
enough area to display.
So, there was some dead codes and TODO list for this..
By using wd->horizontal, we can decide between "up/down" and "left/right"
If elc_ctxpopup is horizontal, "up/down" is more proper than "left/right"
and vice versa.
Sincerely,
Shinwoo Kim.
SVN revision: 62420
Hi All,
The ctxpopup arrow is attached on the drag-able part.
If arrow height/width is smaller than drag-able part,
then there is a gap between arrow and ctxpopup base.
So this patch comes for resolving this issue. Thanks.
Sincerely,
Shinwoo Kim.
SVN revision: 61462
Subject: Re: [E-devel] [Patch][CtxPopup] Add Arrow on the drag-able
area of Base
Dear Mr. Hermet,
Hello, I have attached more accurate patch based on latest elementary. The
last patch already there.
All your review items are reflected on the attached patch.
Please review this again, sorry for any inconvenient.
SVN revision: 59911
Subject: [E-devel] [Patch][CtxPopup] Add Arrow on the drag-able area
of Base
If CtxPopup has elm_slider for content, the elm_slider indicator is covered
by CtxPopup arrow.
So, I have made a patch for resolving this issue. As the title the arrow
will be swallowed in the base.
Even though user uses his/her own style, the attached patch will work
properly.
Sincerely,
Shinwoo Kim.
SVN revision: 59890
Subject: [PATCH] elc_ctxpopup
Here code is for the ctxpopup.
Since the functionalities of ctxpopup are somewhat different,
I'm trying to overwrite the ctxpopup code entirely first.
The main reason is,
Original ctxpopup could determine it's size and position by itself.
Of course, upstreamed version supports this. But it can not be reduced
it's
size
And it supposes the arrow position to center of box edje.
Basically,
This version calculates it's box size first then find available space
from
the it's position.
The origin position of the box is not expected, it finds the available
positions.
But if there is not enough space to be shown, then it finds a best
direction
to be shown again.
In this case, it reduces it's size also as to be shown entirely.
Since the ctxpopup supports scroller, the reduced box could show the all
items also.
(The point is ctxpopup should know the size of total items...)
I'm not sure the upstreamed version could cover the above scenario,
If then, I need to modify it first.
(fixed some minor formatting issue too)
SVN revision: 56021
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