Author Topic: A time to use 'Send Command' ?  (Read 9258 times)

0 Members and 1 Guest are viewing this topic.

MickD

  • King Gator
  • Posts: 3619
  • (x-in)->[process]->(y-out) ... simples!
Re: A time to use 'Send Command' ?
« Reply #15 on: June 07, 2006, 01:02:34 AM »
Adding to what Glenn is saying -
 a snippet from the ARX api help on sendStringToExecute() -
Quote
....The new document will be locked according to the new command's lock level as specified during its registration.

Which all makes sense really :)
"Short cuts make long delays,' argued Pippin.”
J.R.R. Tolkien

Glenn R

  • Guest
Re: A time to use 'Send Command' ?
« Reply #16 on: June 07, 2006, 02:33:58 AM »
All sort of goes together really doesn't it? ;)

Glenn R

  • Guest
Re: A time to use 'Send Command' ?
« Reply #17 on: June 07, 2006, 02:37:12 AM »
Actually, this reminds me of an application I was involved with that was built by Autodesk for Telstra.

It had a custom palette with a tree of commands that was loaded from an XML file and once a tree item was hit, it was sending a command string with answers to the prompts...custom commands defined by the arx.

MickD

  • King Gator
  • Posts: 3619
  • (x-in)->[process]->(y-out) ... simples!
Re: A time to use 'Send Command' ?
« Reply #18 on: July 05, 2006, 11:03:58 PM »
I just discovered another reason you might want to use SendStringToExecute() behind your controls, if your last 'command' proper was undo, you lose all of your previous work!
Although a quick redo will fix it, it is annoying.
"Short cuts make long delays,' argued Pippin.”
J.R.R. Tolkien