I am not sure if this is viewable to all users or if it is viewable only to the poster. Perhaps this is the issue tracker's equivalent to doing a quick reply to a standard forum topic. If you do see it, here is something to remember. Treat hexadecimal the same way that you do decimal, except use sixteen instead of ten.
Some teachers have students draw charts that look similar to the one below.
1,048,576|65,536|4,096|256|16|1

So, in the case of sixty-four, place a four in the sixteen column and multiply the two together. This returns sixty-four. Place a zero in the one column to fill in the gap. It is not necessary to place zeros at the beginning—only the end. Add them together. 64 + 0 = 64. 64 in decimal = 40 in hexadecimal.
This works for any amount. For example, 255 = 15 (F) × 16 (240) + 15 × 1 (15). The chart above can be expanded to any amount. Remember though, those should be powers of sixteen, beginning at zero (1) (anything to the power of zero is one). By the way, this technique works for any base greater-than or equal to two (though if you want to base your math on the ASCII table, then you would be stopping at 256 (ÿ)) because this is the end of it. I hope that this make sense and helps you in future conversions.

This is fixed?

As a side effect of something different I wanted to implement, this is now fixed: The status bar now shows the same verbose information as the Note Properties dialog, so for example for a tempo command, it shows the tempo in decimal, etc.
An updated test version (r4707 or later) can as always be grabbed from http://buildbot.openmpt.org/builds/