lmi
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lmi] first version of multi dimensional data editor control checked


From: Wendy Boutin
Subject: Re: [lmi] first version of multi dimensional data editor control checked in
Date: Thu, 22 Dec 2005 16:52:59 -0500
User-agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)

Boutin, Wendy wrote:
Vadim Zeitlin wrote:

Hello,

I've checked in the first version of MDGrid in the cvs, on mdgrid_branch
(i.e. you have to do "cvs up -r mdgrid_branch" to see it). There is a small
test which shows the control in action, please let me know if you have any
remarks about either its appearance/behaviour or its API.


These are my initial comments on MultiDimGridAny Test App, but
I'm sure I will have more as I spend more time on it. I wanted
to take this opportunity to start a discussion here and invite
a few co-workers, who usually test our GUI, to provide their
thoughts and comments too. Here are mine:

Now that I can see the color in action, I don't think it really
adds much value; the field that's greyed out says the same thing as the color-coding.

When the same options are selected for the x- and y-axis, it
seems strange that those options just swap axes.

When 'strike' is selected and I change the values in the two text controls, the new values aren't retained--the default values are restored.

I can't figure out how the numbers are translated from the
text controls to the grid. Using these inputs:
  x-axis is blank
  y-axis is strike
  change second text control to '45', then 'Alt-A'
I observe the grid display changes to a range of ten through forty,
but the text control value changes back to '100'; shouldn't it
remain '40'? Also, '15' seems to == '15' in the display, so how
I mean    45
because that was the value I entered in the GUI.

does '100' translate to '90', but then '95' also translates to '90'?
[I triple-checked the numbers I documented here, so I'm sure there
aren't any typos.]

But a quadruple check proved I did have a typo. Sorry about that.

long int seems to be the data type for values entered in the display
grid; I believe we'll need float. Does that cause any problems?

Why do the range fields have a scaling unit of five?

The first and second time I opened the program, I managed to make
enough changes (only ten or so) in the interface to invoke the
assertion I copied below. My usual practice is to provide the exact
steps I took when I observed the problem. Unfortunately, I can't
easily reproduce this one, but thought you should still be aware, so
I've also shared the inputs as they were right before the program
shut down.

GUI inputs:

       x-axis: Strike
text controls: 10 and 100
       y-axis: Option type
  Option type: Put
Exercise type: American
       Strike: 10
     Maturity: January

Assertion:

---------------------------
wxWidgets Debug Alert
---------------------------
../include/wx/dynarray.h(807): assert "uiIndex < m_nCount" failed.
Do you want to stop the program?
You can also choose [Cancel] to suppress further warnings.
---------------------------
Yes   No   Cancel
---------------------------

---------------------------------------------------------
This e-mail transmission may contain information that is proprietary, privileged and/or confidential and is intended exclusively for the person(s) to whom it is addressed. Any use, copying, retention or disclosure by any person other than the intended recipient or the intended recipient's designees is strictly prohibited. If you are not the intended recipient or their designee, please notify the sender immediately by return e-mail and delete all copies.
---------------------------------------------------------



_______________________________________________
lmi mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/lmi








reply via email to

[Prev in Thread] Current Thread [Next in Thread]