Author Topic: How to reset variables in the get midpoint functions  (Read 9536 times)

0 Members and 1 Guest are viewing this topic.

chlh_jd

  • Guest
Re: How to reset variables in the get midpoint functions
« Reply #30 on: August 05, 2011, 11:39:06 AM »
Sorry , I must go out now .  I 'll discuss with you tomorrow .

gile

  • Gator
  • Posts: 2520
  • Marseille, France
Re: How to reset variables in the get midpoint functions
« Reply #31 on: August 05, 2011, 11:50:28 AM »
Quote
I've actually got that set up in my CUI as a keyboard shortcut: Ctrl+M
1+
Speaking English as a French Frog

jaydee

  • Guest
Re: How to reset variables in the get midpoint functions
« Reply #32 on: August 05, 2011, 01:11:19 PM »
Thankyou all reponding to my post. your advice help me alot.
Have a good weekend.

chlh_jd

  • Guest
Re: How to reset variables in the get midpoint functions
« Reply #33 on: August 06, 2011, 01:32:38 AM »
Sorry , I must go out now .  I 'll discuss with you tomorrow .
Or just type M2P or MTP  :)
I've actually got that set up in my CUI as a keyboard shortcut: Ctrl+M

All I can figure from the "System Access Device" ...  :o ... perhaps the OSnap? Strange though ... I've never run into such situation where the midpoint picked an endpoint. Maybe I've just been "lucky".

I'm sorry for my poor English . 'System Access Point Device in use'  perhaps is that
The CommandLine Now allow to input a point  or point coordinates .

irneb

  • Water Moccasin
  • Posts: 1794
  • ACad R9-2016, Revit Arch 6-2016
Re: How to reset variables in the get midpoint functions
« Reply #34 on: August 06, 2011, 01:55:15 AM »
Oh! That's fine I suppose, but you're converting a point's XYZ into a string to pass to the SendKeys method. The accuracy is not going to be a good as when you pass the value directly from lisp through the command/vl-cmdf functions.

Also you don't prefix the point with the forced None object snap. Though I'm unsure why I've never had such a problem with using M2P instead.
Common sense - the curse in disguise. Because if you have it, you have to live with those that don't.

chlh_jd

  • Guest
Re: How to reset variables in the get midpoint functions
« Reply #35 on: August 06, 2011, 02:26:14 AM »
Oh! That's fine I suppose, but you're converting a point's XYZ into a string to pass to the SendKeys method. The accuracy is not going to be a good as when you pass the value directly from lisp through the command/vl-cmdf functions.

Also you don't prefix the point with the forced None object snap. Though I'm unsure why I've never had such a problem with using M2P instead.

The accuracy can be set higher through (rtos a 2 8) or higher

Lee Mac

  • Seagull
  • Posts: 12923
  • London, England
Re: How to reset variables in the get midpoint functions
« Reply #36 on: August 06, 2011, 08:37:13 AM »
I'm sorry for my poor English . 'System Access Point Device in use'  perhaps is that
The CommandLine Now allow to input a point  or point coordinates .

Does this not work for you:

Code: [Select]
Command:
Command: _line Specify first point:
Specify next point or [Undo]: m2p
First point of mid: Second point of mid:
Specify next point or [Undo]:
Specify next point or [Close/Undo]:

chlh_jd

  • Guest
Re: How to reset variables in the get midpoint functions
« Reply #37 on: August 07, 2011, 08:09:45 AM »
I'm sorry for my poor English . 'System Access Point Device in use'  perhaps is that
The CommandLine Now allow to input a point  or point coordinates .

Does this not work for you:

Code: [Select]
Command:
Command: _line Specify first point:
Specify next point or [Undo]: m2p
First point of mid: Second point of mid:
Specify next point or [Undo]:
Specify next point or [Close/Undo]:
the command m2p or mtp can be use in my ACAD2010, but not for ACAD2004

irneb

  • Water Moccasin
  • Posts: 1794
  • ACad R9-2016, Revit Arch 6-2016
Re: How to reset variables in the get midpoint functions
« Reply #38 on: August 08, 2011, 03:24:11 AM »
The accuracy can be set higher through (rtos a 2 8 ) or higher
Just not sure why you'd want to go that route! It seems a lot of extra just so you can send a piece of converted text (which is unnecessary with command) through an ActiveX Script-Object to the running command. I can understand using it when your running command is also a lisp routine, but not for normal commands / non-lisp addons.
Common sense - the curse in disguise. Because if you have it, you have to live with those that don't.