Author Topic: Strange behavior of block insertion  (Read 1539 times)

0 Members and 1 Guest are viewing this topic.

Giuseppe Beatrice

  • Newt
  • Posts: 43
Strange behavior of block insertion
« on: October 30, 2017, 12:39:42 PM »
I noticed a strange behavior of a vlisp instruction. :nerdyembarassed:
I wrote a set of instructions for inserting blocks into the paper space of a layout, visualized by it's extension:
....
(command-s "_-insert" bl$ "_sc" scbl# ptbl 0)
....
I had previously set the 'OSMODE system variable to 0 or 16384, but in some cases the insertion point of the block moved to the nearby line or block.
The only method I have come up with is to first launch a zoom command, narrowed at the insertion point or at a far point, with a factor of 30 or less.
Does anyone know the reason for such behavior?

huiz

  • Swamp Rat
  • Posts: 919
  • Certified Prof C3D
Re: Strange behavior of block insertion
« Reply #1 on: October 30, 2017, 12:48:04 PM »

Yes, somewhere in Options you control scripted insertions, I have no AutoCAD at the moment but I'll look up later.
It also has a variable so you can avoid it by setting this at the top of your lisp.

The conclusion is justified that the initialization of the development of critical subsystem optimizes the probability of success to the development of the technical behavior over a given period.

Lee Mac

  • Seagull
  • Posts: 12914
  • London, England
Re: Strange behavior of block insertion
« Reply #2 on: October 30, 2017, 01:40:04 PM »
I would suggest using:
Code: [Select]
(command-s "_.-insert" bl$ "_S" scbl# "_R" 0.0 "_non" ptbl)

Marc'Antonio Alessi

  • Swamp Rat
  • Posts: 1453
  • Marco
Re: Strange behavior of block insertion
« Reply #3 on: October 30, 2017, 01:43:01 PM »

I noticed a strange behavior of a vlisp instruction. :nerdyembarassed:
I wrote a set of instructions for inserting blocks into the paper space of a layout, visualized by it's extension:
....
(command-s "_-insert" bl$ "_sc" scbl# ptbl 0)
....
I had previously set the 'OSMODE system variable to 0 or 16384, but in some cases the insertion point of the block moved to the nearby line or block.
The only method I have come up with is to first launch a zoom command, narrowed at the insertion point or at a far point, with a factor of 30 or less.
Does anyone know the reason for such behavior?
Prova così (non serve disattivare OSMODE):
Code: [Select]
(command-s "_-insert" bl$ "_sc" scbl# "_NONE" ptbl 0)


huiz

  • Swamp Rat
  • Posts: 919
  • Certified Prof C3D
Re: Strange behavior of block insertion
« Reply #5 on: October 31, 2017, 06:25:59 AM »
It is the variable OSNAPCOORD which is default 2 (Keyboard entry except scripts), but if you set it to 1 (keyboard entry) you can import blocks without accidental object snaps.

You'll find this also in the Options dialog, tab User Preferences, part Priority for Coordinate Data Entry.
The conclusion is justified that the initialization of the development of critical subsystem optimizes the probability of success to the development of the technical behavior over a given period.

Giuseppe Beatrice

  • Newt
  • Posts: 43
Re: Strange behavior of block insertion
« Reply #6 on: November 01, 2017, 04:18:21 AM »
Thanks to all of you for the valuable informations.
Marc'Antonio, your command is less fast than Lee-Mac, but the difference is really very small.
You all are always the best, thank you again.

Marc'Antonio Alessi

  • Swamp Rat
  • Posts: 1453
  • Marco
Re: Strange behavior of block insertion
« Reply #7 on: November 01, 2017, 06:04:59 AM »
Thanks to all of you for the valuable informations.
Marc'Antonio, your command is less fast than Lee-Mac, but the difference is really very small.
You all are always the best, thank you again.
...intendevo che Lee più stato più veloce a risponderti... (
I meant Lee was quicker to answer you)