elementary-dev-community team mailing list archive

[Cassidy James <c@xxxxxxxxxxx>]

Hm, this is true, I bet there're popovers in popovers for contact adding
and whatnot.

Dan, what do you think?

On Wed, Jan 11, 2012 at 2:04 AM, Kārlis Lukstiņš
<karlis.lukstins@xxxxxxxxx>wrote:

> oh, if mailed to you Cassidy, and not to the ML.
>
> 2012. gada 11. janvāris 10:04 Kārlis Lukstiņš
> <karlis.lukstins@xxxxxxxxx> rakstīja:
> > The DatePicker widget, has a popover for showing the calendar.
> >  So if you have a DatePicker in a popover it becomes a nested one. And
> > it is not working at the moment.
> >
> > If we decide to not allow such behavior, it need to be changed.
> >
> > 2012/1/11 Cassidy James <c@xxxxxxxxxxx>:
> >> Keep in mind this was me resurrecting a thread that nobody replied to
> back
> >> from October (check the original date on my first message). :P
> >>
> >> I just know some of the same issues had come up and thought it my be
> useful
> >> to address these points that were previously raised.
> >>
> >> Oh, and yeah, no popovers within popovers. That shouldn't be allowed. :P
> >>
> >> On Jan 10, 2012 4:28 PM, "Сергей" <shnatsel@xxxxxxxxx> wrote:
> >>>
> >>> I thought Granite.Init was already introduced, and added to
> >>> Granite.Application... weird.
> >>> I'm pretty sure LGPL was already agreed upon. I saw several "I agree"
> >>> posts on the ML at least.
> >>> And yes, Contractor methods seem to be a mess.
> >>>
> >>> --
> >>> shnatsel
> >>
> >>
> >> --
> >> Mailing list: https://launchpad.net/~elementary-dev-community
> >> Post to     : elementary-dev-community@xxxxxxxxxxxxxxxxxxx
> >> Unsubscribe : https://launchpad.net/~elementary-dev-community
> >> More help   : https://help.launchpad.net/ListHelp
> >>
>