> that's actually partly the definition of "passive", and you can get at this
> API-wise by using KWindowSystem (which is what PopupApplet is doing
Maybe I haven't explained myself. Passive window is a window that is not
managed by the window manager, that is, it can not have the focus. Is that
On Tuesday 24 March 2009, Ivan Čukić wrote:
> The thing that strikes me as bad is the fact that the auto-hide is a side-
> effect of whether the popup is passive or not, and not something available
> through APIs.
that's actually partly the definition of "passive", and you can get at this
API-wis
> > it would (with the current implementation) induce closing the popups when
> > they lose the focus, which is not desired (at least not for
> Passive or not is set on PopupApplet, not extenders (through
I know, I just mentioned them as an example where auto-close-on-lost-focus is
bad idea.
I a
On Tuesday 24 March 2009, Casper Clemence wrote:
> It would be great if it could somehow elegantly support both usage
> patterns. Some sort of button that could be pressed that clearly meant
> "don't disappear"... hmmm
what we did in kde3 was provide a close button. a generic "collapse this back"
After observing a few non-techie people use my laptop I have noticed
that they tend to panic slightly when the calendar pop-up doesn't
disappear automatically. Waggling the mouse about while they work out
where they need to click seems to be the usual response.
It would nice at least to give some
On Tuesday 24 March 2009 14:24:25 Aaron J. Seigo wrote:
> On Tuesday 24 March 2009, Rob Scheepmaker wrote:
> > as possible. The calendar only opens when the user wants to, in which
> > case passive popup isn't necessary at all.
>
> think about when and why the user opens the calendar: to check date
On Tuesday 24 March 2009, Rob Scheepmaker wrote:
> as possible. The calendar only opens when the user wants to, in which case
> passive popup isn't necessary at all.
think about when and why the user opens the calendar: to check dates. often
this is to coordinate something going on somewhere else
On Tuesday 24 March 2009 12:37:18 Ivan Čukić wrote:
> When a dialog is passive, it can only receive keyboard input when its
> parent application has the focus.
>
> This means that the text-box in the calendar (the clock-pop-out-calendar,
> not the calendar applet) meant for entering the date works
This is mostly dedicated to Aaron and Rob (IIRC, Rob did PopupApplet and
Extenders)
The passive pop-up problem got me thinking.
When a dialog is passive, it can only receive keyboard input when its parent
application has the focus.
This means that the text-box in the calendar (the clock-pop-ou
