> > > It is the same tracker, created before the main loop. This supposes you
> > > need it at all, i.e. having an updated list of all windows with their
> > > meta data at any moment (except for window flags). You don't need it for
> > > simple tasks, having a window id is often enough.
> >
> > Sorry, I don't really get the point. So, just to be sure:
> > When I want to write a plugin that gets the windowid of every opened
> > window that doesn't have the SkipWindowList-Flag set, I've to use a
> > tracker ( $tracker = $module->track("WindowList"); ) and after that I've
>
> If you need just ids of windows matching some criteria, you don't need a
> tracker. If you need the non-id data, like window name, page or
> coordinates, then you may use WindowList tracker (although you may just
> manually listen to appropiate events yourself instead if you like).
>
> > to send a message to all windows that don't have the flag
> > ( $module->send("All (!WindowListSkip) SendToModule $module->{name}
> > apply"); )?
>
> This command does not send message to all windows, it sends "apply"
> messages to your own module, one per window. This way you may collect all
> matching ids. It is possible you also need to send "end-of-list" message
> after all "apply" messages, so you can know when to stop to collect.
> If all this is hard to understand, then wait for support of flags.
No, I understand your idea clearly. But I don't know how to get the windows
ids, when I get the M_STRING-event. When I get the event I can do
my ($module, $event) = @_;. Are there any information hidden in $event?
It's unfortunately not covered in the documentation.
> Please ask on the list, not privately.
Uh, yeah, sorry. I took the wrong message - I always receive two answers from
you.
Marcel
