I was hoping to combine the latest XSB update with the additional Linux sound logging code. However, it's taking longer than I wanted to get the next version out.
It's taking longer because I decided to add an additional preference window for a new setting, which allows the user to specify the width of the text window and chat bar. This is especially handy for those using the Matrox triple-head solution, because X-plane sees that as one screen and thus would stretch the text box all the way across all three screens.
The reason a simple dialog box is taking a bit of time is because it's more complex than you might think. Each coordinate of each element in the dialog box must be specified manually. Try to place some things, compile, launch X-plane, test. Move them a little bit, compile, launch X-plane, test. Wash, rinse repeat.
And of course the biggest time consumer is that real-life things are getting in the way, like my seven-year-old son's baseball season.
However, I know Linux users are tired of waiting, so I'm going to go ahead and put up a private download by the end of the weekend for Linux users. It will contain only additional logging code for sound - no other new features.
Tuesday, April 28, 2009
Friday, April 10, 2009
So what's up with XSB?
I'm getting ready to release an update for XSB that fixes three things: the "Windows Beep of Death," adds some extra text window controls, and resolves the lack of automatic download of the VATSIM server list.
I've had a fix available for the Windows "Beep of Death" for a while and have been handing it out privately to anyone who needs it.
The VATSIM server list doesn't sound like a big deal, but it's been awfully confusing for new users to download XSB and then have no idea what to put in the server field, so a fix is long overdue.
Additionally, I'm going to be handing out a private update to Linux users who wish to test it that will include additional logging code to try to find the "sound disappears after 30 minutes bug." I know this one has really been annoying the Linux users and I hope I we can find the problem. Linux troubleshooting is particularly difficult for me because I don't have a Linux machine on which to debug - I simply have a VM on which I can build.
I have other features on "The List" which I plan to implement when I have time. Several are big requests of many users, but they take quite a while to implement or have other logistical or legal entanglements which need to be sorted out first.
"The List" (pretty much in the order I think things will happen)
• Setting a reasonable visibility for airports not reporting anything for visibility (currently they get zero visibility)
• Find the reason some users are getting lots of CSL loading errors
• COM2 support
• SELCAL support
• Upper-level wind
• Using the OBJ model for CSLs
This list isn't by any means comprehensive and is always subject to change.
If you want to add additional feature requests, please log in to my bug tracking database, at dogwatchsw.com/mantis
I've had a fix available for the Windows "Beep of Death" for a while and have been handing it out privately to anyone who needs it.
The VATSIM server list doesn't sound like a big deal, but it's been awfully confusing for new users to download XSB and then have no idea what to put in the server field, so a fix is long overdue.
Additionally, I'm going to be handing out a private update to Linux users who wish to test it that will include additional logging code to try to find the "sound disappears after 30 minutes bug." I know this one has really been annoying the Linux users and I hope I we can find the problem. Linux troubleshooting is particularly difficult for me because I don't have a Linux machine on which to debug - I simply have a VM on which I can build.
I have other features on "The List" which I plan to implement when I have time. Several are big requests of many users, but they take quite a while to implement or have other logistical or legal entanglements which need to be sorted out first.
"The List" (pretty much in the order I think things will happen)
• Setting a reasonable visibility for airports not reporting anything for visibility (currently they get zero visibility)
• Find the reason some users are getting lots of CSL loading errors
• COM2 support
• SELCAL support
• Upper-level wind
• Using the OBJ model for CSLs
This list isn't by any means comprehensive and is always subject to change.
If you want to add additional feature requests, please log in to my bug tracking database, at dogwatchsw.com/mantis
So, what's a Dogwatch?
Dogwatch:
1. Nautical. either of two two-hour watches, the first from 4 to 6 p.m., the latter from 6 to 8 p.m.
2. The complete failure of a developer to come up with a company name, thus having to revert to his Navy days for something - anything at all. (This definition obviously mine)
Yep. A while ago I was thinking about publishing some shareware, so I needed a company name for such individual projects, as opposed to the stuff I do with Mark 9 Systems, LLC (Targetware).
So in a fit of desperation, I came up with Dogwatch Software. Why? Well, I was in the Navy, the dogwatch is a Navy watch in the evening and I do most of my work at night. And with that massive effort and reasoning, I had a company name, and then decided not to finish the software products.
I've never been tremendously happy with the name, so I'm always open to suggestions. The best names are short and easily remembered. Bungie, Panic, Blizzard, Pangea, etc. But I haven't come up with any of those and I'm now several years into Dogwatch, so I'll stick with it until I think up something better.
So there you go, the very unremarkable history of the name.
The purpose for the blog is to catalog my independent projects, which at this point, primarily consists of XSquawkBox (http://www.xsquawkbox.net), the VATSIM client (http://vatsim.net) for X-plane.
Often I'll talk about the motivations for working on one feature versus another, particular difficulties I'm facing, or just other random facts and trivia.
1. Nautical. either of two two-hour watches, the first from 4 to 6 p.m., the latter from 6 to 8 p.m.
2. The complete failure of a developer to come up with a company name, thus having to revert to his Navy days for something - anything at all. (This definition obviously mine)
Yep. A while ago I was thinking about publishing some shareware, so I needed a company name for such individual projects, as opposed to the stuff I do with Mark 9 Systems, LLC (Targetware).
So in a fit of desperation, I came up with Dogwatch Software. Why? Well, I was in the Navy, the dogwatch is a Navy watch in the evening and I do most of my work at night. And with that massive effort and reasoning, I had a company name, and then decided not to finish the software products.
I've never been tremendously happy with the name, so I'm always open to suggestions. The best names are short and easily remembered. Bungie, Panic, Blizzard, Pangea, etc. But I haven't come up with any of those and I'm now several years into Dogwatch, so I'll stick with it until I think up something better.
So there you go, the very unremarkable history of the name.
The purpose for the blog is to catalog my independent projects, which at this point, primarily consists of XSquawkBox (http://www.xsquawkbox.net), the VATSIM client (http://vatsim.net) for X-plane.
Often I'll talk about the motivations for working on one feature versus another, particular difficulties I'm facing, or just other random facts and trivia.
Subscribe to:
Posts (Atom)
