Closed GoogleCodeExporter closed 9 years ago
I'm not sure I understand what you mean, but there's a problem with offline
messaging
there which I hope is fixed with r361.
Original comment by paulburt...@gmail.com
on 5 Apr 2008 at 9:34
Yeah the logs you are giving us are showing errors with Offline Messaging, not
with
regular messages.
Can you please confirm that you are talking about live messages and not
receiving
offline ones?
Original comment by dra...@gmail.com
on 5 Apr 2008 at 9:40
yes, I'm talking about live messages.
Original comment by kasmol.a...@gmail.com
on 6 Apr 2008 at 2:05
I can verify this behaviour, I've seen it happen (but for me, it only occurs
about 5%
of the time), logs coming when it happens again
Original comment by ben.motm...@gmail.com
on 6 Apr 2008 at 11:20
Original comment by ben.motm...@gmail.com
on 6 Apr 2008 at 1:29
This is the javascript timer being removed... We need that back. Thats why those
messages dont show. Will be fixed soon. (BTW: It only happens when using Adium
message themes).
Original comment by dra...@gmail.com
on 8 Apr 2008 at 6:31
More Gecko oddities... Is there an event other than ProgressAll we can use to
know
when the page is fully loaded? We could use something like the DOM ready event
provided by many javascript libraries. A timer works but it's not ideal...
Original comment by paulburt...@gmail.com
on 8 Apr 2008 at 6:51
Original comment by dra...@gmail.com
on 8 Apr 2008 at 8:56
The timer is back as of r391, hopefully that'll fix this. Please test this out
to
check it works.
Original comment by paulburt...@gmail.com
on 17 Apr 2008 at 1:01
Galaxium freezes when trying to change the adium theme in the preferences window
Original comment by andrea.c...@gmail.com
on 17 Apr 2008 at 7:37
no, it crashes also when trying to send a message :)
Original comment by andrea.c...@gmail.com
on 17 Apr 2008 at 7:55
Could you try with r395? I think GuiSyncDispatch is broken, it never seems to
return
even though the code in the delegate does reach its end... Which caused any
ProcessJSQueue call after the first to hang.
Original comment by paulburt...@gmail.com
on 17 Apr 2008 at 9:13
Fixed
Original comment by andrea.c...@gmail.com
on 17 Apr 2008 at 9:53
I will keep this issue open for a while for the "GuiSyncDispatch" method, there
are
some minor adjustments in libanculus-sharp which might fix any problems with
synchronous dispatching.
So we will have to re-evaluate this after the move from libcommon to libanculus
Original comment by ben.motm...@gmail.com
on 17 Apr 2008 at 11:16
Original comment by dra...@gmail.com
on 26 Apr 2008 at 10:02
Original comment by dra...@gmail.com
on 26 Apr 2008 at 10:04
This is still the case with libanculus-sharp 0.3.1. I opened issue 1 in the
libanculus issue list, its more relevant there.
Original comment by paulburt...@gmail.com
on 25 May 2008 at 10:51
Original issue reported on code.google.com by
kasmol.a...@gmail.com
on 5 Apr 2008 at 8:22