Started small project to add proper support for joysticks to Railworks. Basically goals for now are:

• Support for multiple joysticks
• Proper support for joystick ranges (the one driver I found supported only 1/2 of the range)
• Proper support for combined throttle/break for DMU

Project sources can be found here. Hope to release binary somewhere next week.

I was thinking that when Internet will be widely spread then we are going to have easy access to information. Funnily enough this isn't happening. For instance:

iTunes: Toy Story 3 is available in USA in HD, in Canada only regular resolution which cost like HD version in the USA 

iTunes/Amazon: I couldn't buy movies from Japan (in japanese and with japanese subtitles)

All this is quite sad. One would think that everybody should be interested in this. Like movie makers will get some money if I buy it from them. People will have a chance to watch movies from other countries. Should be as easy as pay-download-watch. But no we are building fences and supporting piracy...

Please watch this -> HOME! It's an awesome move. Do watch it!

Added support for CDT (C/C++) and DLTK (PHP, Ruby, TCL, JavaScript) plug-ins. Also fixed some small bugs.

At last I released new version on Task Tag Decorator. Please check documentation for more details.

There's going to be a delay in release due to unforeseen things (me being busy). Good thing is that I managed to simplify API again and add generic support for any task tags. I think until this point I didn't really understand the beauty of the following saying (I don't remember exact wording, and I am still trying to find it):

 

"You know you've finished API not when you couldn't add anything else but when you couldn't remove anything"

Was too busy to work on anything, but I am back. Plan to release first new version of Task Tag Decorator by June 19th.

I bought my 1st Apple. And I am totally enjoying it and I think I know why. Instead of making stuff more complex Apple is trying to make it simpler. I share the same philosophy.

"Make everything as simple as possible, but not simpler."
- Albert Einstein

After some changes made on the server side (WCF) I started to receive funny errors. Funny because they didn't make any sense! Luckily I've quickly found that culprit is using (...) { ... } statement.

1  using (var service = channelFactory.Create()) {
2    service.methodA(...);
3  }

Basically if line 2 throws error line 3 (when service.Dispose() is called) might throw another exception and original exception will be lost. I like contract for destructors in C++. Sigh...

Added a couple of 'how to's. It took me some time to figure out how to do all of them (still have some issues) so I decided to document and publish them.