It's back to the drawing board for the Red X - removing the big resources doesn't seem to have done the trick, but I've two other avenues that I'm exploring.
Watch this space.
Tuesday, January 20, 2009
Thursday, January 15, 2009
Apologies & the Red X
Firstly, apologies are in order. It turns out that there's been a problem with the email forwarding from the support account to my own and so I didn't get notified of the messages that you folks sent. I wasn't just ignoring them and hopefully it's all been resolved now. I've also had an offer of a virtual machine exhibiting the problem which should really help matters along - assuming that the recent work hasn't already fixed matters.
A few people experiencing the Red X kindly offered to re-test. Now the email is working properly would you mind dropping some contact details to support@t6analytics.com please and I'll issue you a test version with the big graphical resources removed and an update of the control kit used?
Equally, it would be helpful (or nice at least) to hear from folks who are running without any problems at all! I've got my New Year motivation exercise back and it can only help maintain it :-) Based on the email backlog though, it might be that I'm the only one :-(
Cheers
A few people experiencing the Red X kindly offered to re-test. Now the email is working properly would you mind dropping some contact details to support@t6analytics.com please and I'll issue you a test version with the big graphical resources removed and an update of the control kit used?
Equally, it would be helpful (or nice at least) to hear from folks who are running without any problems at all! I've got my New Year motivation exercise back and it can only help maintain it :-) Based on the email backlog though, it might be that I'm the only one :-(
Cheers
Sunday, January 4, 2009
New Year
It's been a while since the lost post, so I hope everyone had a happy xmas and that 2009 is a good one for all.
I'd like to say that I've made exceptional progress fixing up the issues that have been reported so far, but I can't really. I've a few ideas why the ribbon isn't working as expected but other things have consumed quite a lot of time throught November and Decemeber is never a good bet at getting stuff done. I've had a succession of general colds, sniffles and what my wife refers to as TB (lol) so haven't done much training over December - not having new personal data doesn't provide inventive to push on.
That said, I've made a couple of minor changes by removing the large bitmaps - and it's possible that there are issues with some of the naming convetions for embedded graphics resources but the app needs to be repackaged for testing. One of the problems is that I do not have a machine that exhibits the same problems so it's particularly hard to diagnose - given that the error is a generic Windows error that bubbles up through a 3rd party toolkit. I'm intending to spent a little more time on this over the next month so hopefully there should be some further progress.
Personally I tend to be 110% on something for a while, then get a bit bored and move on to something else. In this instance it's been some work to interface with the PC POD for real-time data and the use of that data in an external manner. As such, I've spend a lot of the time over the last month or so playing with the software to interface with the PC POD and to communicate with external hardware to drive clusters of LED's in order represent heart rate rhythems. I knew next to nothing about electronics so it's been a bit slow going. Most of the individual components now work so it's a case of joining the things up. On the whole, it's not particularly relevant to the fitness software but it is related.
So, I'm looking to spend more time on it during January and will aim to post more frequent updates.
I'd like to say that I've made exceptional progress fixing up the issues that have been reported so far, but I can't really. I've a few ideas why the ribbon isn't working as expected but other things have consumed quite a lot of time throught November and Decemeber is never a good bet at getting stuff done. I've had a succession of general colds, sniffles and what my wife refers to as TB (lol) so haven't done much training over December - not having new personal data doesn't provide inventive to push on.
That said, I've made a couple of minor changes by removing the large bitmaps - and it's possible that there are issues with some of the naming convetions for embedded graphics resources but the app needs to be repackaged for testing. One of the problems is that I do not have a machine that exhibits the same problems so it's particularly hard to diagnose - given that the error is a generic Windows error that bubbles up through a 3rd party toolkit. I'm intending to spent a little more time on this over the next month so hopefully there should be some further progress.
Personally I tend to be 110% on something for a while, then get a bit bored and move on to something else. In this instance it's been some work to interface with the PC POD for real-time data and the use of that data in an external manner. As such, I've spend a lot of the time over the last month or so playing with the software to interface with the PC POD and to communicate with external hardware to drive clusters of LED's in order represent heart rate rhythems. I knew next to nothing about electronics so it's been a bit slow going. Most of the individual components now work so it's a case of joining the things up. On the whole, it's not particularly relevant to the fitness software but it is related.
So, I'm looking to spend more time on it during January and will aim to post more frequent updates.
Subscribe to:
Posts (Atom)