http://monkeydyne.com/rmcs/opencomic.phtml?rowid=57289
Major suckage today. The past three days have been a nearly constant barrage of online arguments with Barb, followed up with more idiocy at work. Add the upgrade to a 30-minute workout, and I'm exhausted.
Barb and I are at least on civil terms again. There are still a lot of issues to be resolved, but I guess that is only to be expected.
Work-- ugh.
The component I am working on plays sounds. More precisely, it sends a message to another component that actually plays the sound that my component identifies.
Well, due to a design snafu, the component that I was supposed to send the message to was removed, and replaced with a different mechanism. Except they forgot about the sound, so there is nothing to actually play sounds at all.
So I've been pushing trying to identify who needs to actually create this piece. So far, it has been narrowed down to two teams, and they are fighting back and forth because neither one of them wants to do it. It has escalated up to the management level twice now.
The group that should be doing it won't even consider touching it until July. I was supposed to be done with it today.
Most of the past three days at work (or at least non-meeting time) has been spent working on a timer.
You see, timers are very specific to the hardware. And we don't have hardware yet, or at least not available to us. There is a hardware simulator, but it doesn't work. And there is no platform code, or core code, and the operating system has problems.
So we are developing and testing on Windows.
And Timers in Windows are completely different than timers in VxWorksAE.
Like the difference between a car and spelunking.
So I have to create a "wrapper" class that acts as a common interface, so that the guys who use the timer don't have to deal with operating system differences, they just use the timer. I've had that done since last week.
The problem is making the Windows timer behave similarly to the VxWorksAE timer.
And oh, yeah, I have to use callback functions, not message queues.
Major suckage today. The past three days have been a nearly constant barrage of online arguments with Barb, followed up with more idiocy at work. Add the upgrade to a 30-minute workout, and I'm exhausted.
Barb and I are at least on civil terms again. There are still a lot of issues to be resolved, but I guess that is only to be expected.
Work-- ugh.
The component I am working on plays sounds. More precisely, it sends a message to another component that actually plays the sound that my component identifies.
Well, due to a design snafu, the component that I was supposed to send the message to was removed, and replaced with a different mechanism. Except they forgot about the sound, so there is nothing to actually play sounds at all.
So I've been pushing trying to identify who needs to actually create this piece. So far, it has been narrowed down to two teams, and they are fighting back and forth because neither one of them wants to do it. It has escalated up to the management level twice now.
The group that should be doing it won't even consider touching it until July. I was supposed to be done with it today.
Most of the past three days at work (or at least non-meeting time) has been spent working on a timer.
You see, timers are very specific to the hardware. And we don't have hardware yet, or at least not available to us. There is a hardware simulator, but it doesn't work. And there is no platform code, or core code, and the operating system has problems.
So we are developing and testing on Windows.
And Timers in Windows are completely different than timers in VxWorksAE.
Like the difference between a car and spelunking.
So I have to create a "wrapper" class that acts as a common interface, so that the guys who use the timer don't have to deal with operating system differences, they just use the timer. I've had that done since last week.
The problem is making the Windows timer behave similarly to the VxWorksAE timer.
And oh, yeah, I have to use callback functions, not message queues.