Problem using unit "mn"
|
09-06-2018, 01:31 AM
Post: #5
|
|||
|
|||
RE: Problem using unit "mn"
(09-05-2018 06:39 PM)parisse Wrote: min is a CAS command (minimum).[HOME] USIMPLIFY(1_(h)) [ENTER] 3600_s USIMPLIFY(1_(min)) [ENTER] 60_s [CAS] USIMPLIFY(1_(h)) [ENTER] 3600_s USIMPLIFY(1_(min)) [ENTER] => USIMPLIFY(1_'min') * or in the command line: USIMPLIFY(1_()'min') giving "Error:Bad argument type" which means that in the Command line parsing (or #cas program) the *UNITS* has to be checked first - even before CAS commands when you find the _ structure or rather _() This is the root of the problem that the user described Proper handling of the UNITS system ensures that there will never be a glitch like this between the CAS and the UNITS NOTE: Also the [Shift] [Units] soft menu "tab" [Units] 5 Time > 8 mn should be 5 Time > 8 min - - - VPN |
|||
« Next Oldest | Next Newest »
|
Messages In This Thread |
Problem using unit "mn" - ChrisSchw - 09-05-2018, 10:46 AM
RE: Problem using unit "mn" - DA74254 - 09-05-2018, 01:43 PM
RE: Problem using unit "mn" - StephenG1CMZ - 09-06-2018, 01:52 PM
RE: Problem using unit "mn" - ChrisSchw - 09-05-2018, 02:10 PM
RE: Problem using unit "mn" - parisse - 09-05-2018, 06:39 PM
RE: Problem using unit "mn" - CyberAngel - 09-06-2018 01:31 AM
RE: Problem using unit "mn" - CyberAngel - 09-06-2018, 03:04 AM
RE: Problem using unit "mn" - Tim Wessman - 09-06-2018, 03:32 AM
RE: Problem using unit "mn" - CyberAngel - 09-06-2018, 01:27 PM
RE: Problem using unit "mn" - parisse - 09-06-2018, 03:33 PM
RE: Problem using unit "mn" - CyberAngel - 09-06-2018, 04:08 PM
RE: Problem using unit "mn" - parisse - 09-06-2018, 06:54 PM
RE: Problem using unit "mn" - CyberAngel - 09-06-2018, 07:16 PM
|
User(s) browsing this thread: 1 Guest(s)