Re: dm

[kerstien@luke.atdiv.lanl.gov (Deb Kerstiens)]

> 
> As long as we're talking about changes to dm, here are some suggestions that
> I would like to see implemented.
> 
> I would really like to be able to enter hex numbers into a "text entry" object
> for things that require numbers but I don't see any way to do it.  Could dm
> be modified to interpret numbers with a leading "0x", "0X" or trailing "x" or 
> "X" as hexadecimal numbers?  I include the last two choices only to be 
> consistent with the way dm displays hex numbers with "text update" objects.
> 
The display list was recently modified to include formats on text_entry 
objects.  My plan was to allow hex numbers if the format was set to do so,
and have it be an error otherwise.  Alternatively, for DBR types that are
not double or float, I could just allow them.  (I could even allow them
for floats and doubles, but I'm not sure that it makes as much sense.)
Comments?  I'm assuming that if the hex format was chosen, CA updates to the
text_entry object would reflect that choice.  Last question: if the hex
format is selected, do I reject input other input?  (I vote no, as long as
it fits the %i format of scanf)
Ditto for octal format....

> I find that in some cases undesired behavior is produced when continuously 
> updating the .VAL field with a changing valuator.  I realize that this behavior
> can be changed with the menu on the live valuator, but I would rather like to
> be able to set the defaults in this menu with edd when the valuator is created
> or modified.

Also in the display list, so you can configure it in edd.  Soon (hopefully) it
will be implemented in dm.  I, too, hate to have to configure things every 
time I bring up a display.

> 
> 	Ric
> 

Deb