What about the problem in this post?http://developer.byond.com/forum/ index.cgi?action=message_read&id=468651&forum=2&view=0

Good job, progress is always good news. Keep up the good work, and I'm looking forward to see many bug fixes in Beta 6!

What about the problem in this post?

That's unlikely to be the same issue. This one purely deals with Dream Seeker not appearing at startup. However, I also fixed another bug last night where the pager would often hang for 10-15 seconds when shutting down. It's possible that's related but I'm still skeptical. Undoubtedly this does not fix every single issue that's been reported with the pager, but it's probably the most common one.

I can't confirm yet whether this fixes any of the following, since I can't reproduce them easily:

* Anything caused by firewalls blocking communication

* ID:439940, ID:439991, ID:472958 - same symptoms, but when opening a game from the Pager. The fixed bug should only occur when opening games from outside the Pager.

* ID:443032 - DS connects but doesn't receive login info. Perhaps related to the above, but should not be related to the fixed bug, which prevented any connection at all.

* ID:459401 - evidently dropping connections with the hub. Should be completely unrelated.

* ID:466883 - "BYOND Central is not accessible." Should not be related to the DS open bug, but perhaps the second one I fixed (shutdown delay) is related.

* ID:468651 - pager freeze may be related to bugfix #2, may not.

* ID:477657 - same symptoms, but occurs when Pager is already open. The fixed bug usually occurs only when Pager isn't open yet, and gets started up when joining a game. The scenario in this post could possibly be the same problem, but it should happen much less frequently than the primary scenario.


The thing that bothers me the most is that the bug doesn't happen consistently for people (including me). Based on my understanding, it should happen randomly about 50% of the time when:

* The game is opened from outside the Pager
* The Pager isn't yet running

But I've had plenty of test sessions where it works every time, and other people have reported either no problems whatsoever, or that problems went away for a long period of time. My analysis suggests that it should happen reliably about 50% of the time when opening games in this manner. Bah!

Finally nailing that stubborn little bug is a nice vindictively satisfying feeling, isn't it?

Not when you have the foreboding sense that there are several other, unrelated issues that are not fixed by this! We'll find out soon enough.

All hail Mike H! Smiter of bugs!

Hiead wrote:

What about ID:447773

Not unless you can conjure Dan. That's one of the more complex parts of the compiler.

Also(too lazy to forum search now), when I leave my PC for a while, and it goes into standby and I receive pager alerts, when I re-login to my user account in WinXP the pager system tray icon remains as that of the alert "!" thing. Fixed, is it?

Nope. I'm not a Windows programmer at all, and I can't find any straightforward tutorials on doing systray icons. It's very common, but seems to require way more code than I think it ought to (how complex can it be? attach a menu with callbacks, change the icon as desired). We use a free library for this and I can't imagine any reason why user switching could possibly affect it. The last "fix" was a stab in the dark that obviously didn't hit the target.

And, heh, I thought the last beta was the last beta before 4.0?

Not even close. I expect many more...

Airjoe wrote:

Anything on ID:481001?

I'm pretty sure that's a feature. In the text window output, newline resets all tags. Removing this feature would make a lot of games look really funny because of unclosed tags on previous lines. I'd suggest simply adding a new <center> tag on each line that needs it.

Any word on this problem? I think it would be a quick fix, but I don't really know.

Congratulations on taking down that behemoth!