Le Tue, 01 Oct 2002 12:17:43 +0000 "Tuomas Jaakola" <[EMAIL PROTECTED]> a écrit: > Thanks for the screenshot! I've never experienced this same problem, > UNLESS I've played with that chatmode messageview option. If you have > had that option off when you opened the first message, the msg will be > opened to a window like that upper window in your screen (I call it > event window). If then you turned that option on and tried to reply the > sender, the result will be two windows, just like in that screenshot > (new window is that lower window, I call it chat window). > > If I haven't touched that chatmode messageview option, everything has > been fine. Please tell me if the patch doesn't still work properly. > It's still strange, with some messages it will go well (after first reply the event window disappears and it's ok), but some times it won't (event window sticking or reappearing). And I promise I didn't toy with the options :)
But I'm beginning to think this could be a problem with Window Maker: when
another window has the focus (like this sylpheed compose window :) ), it's
strange behaviors time (event windows coming back,...). And it's worse
when I change to another 'bureau' (translation: desktop? you know Galeon
on one, sylpheed on another, a few terms on another one, xmms on...), i
get an event window with the last message (even if the chat window is
still open on another window).
> I know the event window feels a bit annoying, but at the moment it is
> vital window to handle other events (like chat requests or file
> transfers).
Sorry I hadn't noticed it. So the changes won't be trivial...
>
> This is just my opinion, but I'd like to have only one window which we
> could use to handle all events. Normally it would be that event window,
> but with chatmode messageview option on, the reply text field could be
> added- not to the bottom of the chat window but to the event window,
> right below that message field (where we can read the messages /
> events). Reading events would work just like before, one event at once.
> The window would look like this then:
>
> +----------------+
> | event table |
> +----------------+
> | message |
> | field |
> +----------------+
> | reply |
> | field |
> +----------------+
> | buttons |
> +----------------+
>
> Maybe this would be the solution for those guys who want to read
> messages one by one? On the other hand, maybe some people like to read
> all messages at once, not clicking everytime that Next button or the
> next event from the event table. Any ideas or comments?
To sum it up, that would mean regrouping the fields from both windows
into a single one. Effectively this looks like a good idea (and I guess it
means less recoding).
Also for people who like to read all messages at once, I guess we could
add (yes another one!) an option like 'auto-next' that would call the
'method called when clicking on next button' each time a new message
arrives (is there an event for that?)
Regards,
--
Bernard Cafarelli
aka Voyageur
ICQ:66024647
msg01369/pgp00000.pgp
Description: PGP signature
