Code - Auto/Visual Lisp: [Select]

(defun c:mf (/ fr)
  (if (and (setq fr (getstring "\nEnter fillet distance. "))
           fr (not (zerop (atof fr))))
    (progn
      (eval
        (vl-list* 'defun
                  (read (strcat "c:r" fr)) 'nil (list 'setvar ''filletrad (atof fr))
                  '((vl-cmdf "_.fillet")
                    (while (< 0 (getvar 'cmdactive)) (vl-cmdf "\\"))
                    (princ)
                   )
        )
      )
      (princ (strcat "\nCommand R" fr " created"))
    )
    (princ "\nFailed to create a command.")   
  )
  (princ)
)

Works fine.the only problem is this.
command: mf
Enter fillet distance. 5.5

Command R5.5 created

command:
command: r5

command: dra DIMRADIUS

mf a fillet 5.5 command,but it only can use by r5 but not r5.5.the messenger"Command R5.5 created"is not correct.

another thing.

command: mf
Enter fillet distance. dsa
Failed to create a command.

command:
command:  MF
Enter fillet distance. 3r
Command R3r created

command:
command: r3r
command: dra DIMRADIUS

atof Function
 



Converts a string into a real number

(atof string)

Arguments

string

A string to be converted into a real number.

Return Values

A real number.

command: (atof "r3r")
0.0

command: (atof "3")
3.0

As I understand it, the SSM API is only exposed to VBA and .NET... At best, you'd have to use .NET to develop some sort of schmancy library of custom .NET LispFunction Methods in order to expose specific LISP Data-Typed Properties (no passing SSM Objects to ResultBuffer), and Methods to LISP API (untested).

Cheers

What is frustrating is when I switch the palette path, it resets to the big list that is worthless.  Does Autodesk think we have such huge monitors that we only need 1 icon per line?

Correct however most if not all NEW users to C3D do not need the confusion of seeing customized commands or functions
during their training sessions. So I would be doing them no favour to have MY installation of C3D customized to any degree
during a training class. 
Yes it is fantastic that we can customize and build commands to suit our needs!  Again, must don't need to be confused by
seeing commands or function that they will not have access to, right Out of the Box.

And along those lines, this is where I also disagree with most 'implementation' plans that include the establishment of
a 'templates' prior to training. As for me it is imperative that the users ALL know the how and why of Styles creation, and feature settings. But not teaching them these things does them a disservice in the long run.

I think that's a difference from being in a position of training new users versus being a long-time professional working in the industry working in an established office with office standards and procedures. I agree that all new users need to learn how to create things from scratch and why things are set up the way they are in the native program. They don't always have that level of training when they get a cad job.
 
So yes if you're in a position of training new people, it's best to use OOTB tools etc.
 
If I'm helping someone at thier computer, I need to remember what the native commands are on thier machine, because all my cool tricks won't work.

you would go to drawing settings, ambient settings and set
Direction>>>>Format DD MM SS.SS

that is what it is set at currently. *shrug*

>>Specify quadrant (1-4): 2
Current direction unit: degree, Input: DD° MM' SS.SS" (spaced)
>>Specify bearing: 89 >> <- space here same as enter