Is there a good explanation of deserialization?

[bltdavid]

I'll take a look at how hard/easy it is to adapt my sample to show the problem. If not too hard I'll get on it.

Thanks!

BTW, I do have another recent thread in this list asserting that custom type converters for expandable objects never get called. Do you know anything about that?

Perhaps, post a link to the thread.

[ETFVoyageur]

7 items down this list just now.

http://ninjatrader.com/support/forum/showthread.php?t=88122

Not a very deep thread. I'll be interested to hear what your experience is in that regard.

--EV

[bltdavid]

7 items down this list just now.

http://ninjatrader.com/support/forum/showthread.php?t=88122

Not a very deep thread. I'll be interested to hear what your experience is in that regard.

Thanks, I've replied to that thread.

[ETFVoyageur]

This thread has gotten so that it would be pretty unreasonable to expect NT support to understand the bug I am reporting. I now have a simple test program that shows the bug, complete with instructions in the comments at the top describing exactly how to reproduce the bug. The hardest parts were:
(a) remembering how to produce the problem
(b) getting the instructions written down, since the editor is modal

I am going to start a new thread that should be clear on the bug., so it is reasonable for NT to act on it.

(done: http://ninjatrader.com/support/forum...ad.php?t=88257)

[ETFVoyageur]

I've had no problems (in NT7) using Font properties.
What problems were you trying to solve?

The main issue motivating me was that SimpleFont, which is what V8 uses, has size ONLY in pixels. Furthermore, that is not even screen pixels, as most non-tech-y users would expect. It is DIPs (device independent pixels). That means:

• A user who is used to points needs to multiply by 96/72 to get DIPs
• A user who expects screen pixels needs to know he is specifying 96 ppi pixels, and adjust accordingly.
• If a user really does care about exact screen pixels there is no way to do that.

I'll add support for pixels, both DIPs and screen pixels, to my todo list. For now, though, my font picker supports points, which I contend is the single most expected sizing for a font.