HP 50G: Dialog box using INFORM Command - Printable Version +- HP Forums (https://www.hpmuseum.org/forum) +-- Forum: HP Calculators (and very old HP Computers) (/forum-3.html) +--- Forum: General Forum (/forum-4.html) +--- Thread: HP 50G: Dialog box using INFORM Command (/thread-5234.html) |
HP 50G: Dialog box using INFORM Command - Maro - 11-29-2015 05:37 PM when using the INFORM command to define an input dialog box, the second argument of INFORM is the list of field specifications: {"label" "helpInfo" TYPE}. If TYPE is 0 (real number), how can the number be displayed in SCI or in ENG format within the input fields of the dialog box? In my application I'm dealing with very small numbers and it is quite cumbersome to see the numbers within the input fields always being displayed in STD format. Any solution to this? Thanks and Regards Maro RE: HP 50G: Dialog box using INFORM Command - cyrille de brébisson - 11-30-2015 06:13 AM Hello, What happen if the display is set to SCI? does it not display the number in SCI int he dialog box? Cyrille RE: HP 50G: Dialog box using INFORM Command - Maro - 11-30-2015 06:51 AM No, that would be too easy. No matter which settings are used in calculator MODE, the numbers in the dialog box are always displayed in STD format and if I have e.g. a two column box and a very small number (e.g. 1E-9), the display shows 0.000000 with the significant numbers truncated. However, the numbers are of course stored correctly. RE: HP 50G: Dialog box using INFORM Command - David Hayden - 12-03-2015 10:26 AM It's a hack, but what if you replaced "label" with << 3. SCI "label" >> ? I believe that all of those fields can be objects that evaluate to the appropriate thing. RE: HP 50G: Dialog box using INFORM Command - Maro - 12-04-2015 10:03 AM (12-03-2015 10:26 AM)David Hayden Wrote: It's a hack, but what if you replaced "label" with << 3. SCI "label" >> ? I believe that all of those fields can be objects that evaluate to the appropriate thing. when using this the INFORM command reports: "INFORM Error: Bad Argument Type". So up to now there seems to be no solution |