Dynamische Eingabe / Bemassung

MATTHIAS SCHWANNER

 

Wenn während der Eingabe gezoomt wird, Ändert sich die Anzeige der dynamischen Bemassung nicht. Sie bleibt viel zu groß und pixelig.

Siehe Screenshot

 

[img]http://img3.fotos-hochladen.net/uploads/dynzuvy6faihg.png[/img]

 

Kann das irgendwo iingestellt werden?

Roy Klein Gebbinck

As far as I know there is no setting for this. It is one of the reasons why I have Dynmode switched OFF. I would advise you to look into Entity Snap Tracking or Polar Tracking. With the polar angles set up correctly, or with Orthomode switched ON, you only have to move the cursor in the direction of one of the predefined angles and enter a distance for a new point. This is also in answer to your question on 'SPUR' (=Tracking) on the Meeting Point.

MATTHIAS SCHWANNER

Hi Roy

thank you for the answer. I switch dymode off, what should I do.

The tracking tip is ok, but too slow for precise and fast work.  Maybe i ask Olaf from CTB to make a tool like Spur.
if You use Spur under Autocad ortho mode ist temporary activ. So you ca work  precise.

Knut Hohenberg

Hello Roy,

nice to hear that I'm not the only person who prefers to leave dynmode off - I find all this dancing interface elements very visually distracting (not to say ugly). There is, however one real advantage of dynmode over polarmode: in dynmode, the cursor tracking gets frozen as soon as you start typing in a value, while in polarmode tracking continues, which can lead to unwanted results (if your mouse moves while you type). Probably it shouldn't be that way, maybe I'll file a SR for that.

Also, I never understood why stracking is temporarily disabled when you use the 'from' snap - but maybe there is a deeper sense to it?

 

Knut Hohenberg

Oh sorry, I meant polar mode not stracking

Roy Klein Gebbinck

Polar Tracking works in combination with my (AltFrom) snap:
http://www.b-k-g.nl/BKG_AdditionalSnaps.html
(Note: not tested on Linux)

Knut Hohenberg

Hi Roy,

looks interesting, but doesn't seem to work on Linux (I first got an error because vla_startundomark is not available, and then all snaps just promt 'additional snaps cannot be stacked').

Didn't realize til now that  bcad's _from doesn't even work with the _per snap - people at Bricsys might think it has been completely superseded by strack and don't care anymore...

Anyway, repairing all that seems as trivial as this:

(defun from ( / tmppnt)
 (setvar "LASTPOINT" (setq tmppnt (getpoint "\nOffset from: ")))
 (command (getpoint tmppnt "\nNext point: "))
 (princ)
)

 

MATTHIAS SCHWANNER

@Roy

thank you! It works fine. 

Roy Klein Gebbinck

@Knut:
Maybe not that trivial: your (from) can conflict with running osnaps.
Improved version:

(defun from ()
  (command "_none" (getpoint (getpoint "\nOffset from: ") "\nNext point: "))
  (princ)
)

@Matthias:
Glad you like it.

Knut Hohenberg

@Roy

thanks, so I'd say the solution is even more trivial as I proposed (don't know why I thought I had to set LASTPOINT in order to get the tracking vector):

simply replacing '_from' with '(command "_none" (getpoint (getpoint "\nOffset from: ") "\nNext point: "))' in the 'osnap_from' tool via the customize dialog gets the work done - no need to load anything. Wasn't this the way (in conjunction with polar mode) AutoCAD's '_tt' snap (Spur/Tracking) worked?

btw, interference with running osnaps should only occur if you set OSNAPCOORD to 0 (which no sane user will ever do), but of course the extra caution doesn't hurt.

Roy Klein Gebbinck

@Knut:
To clarify:
By default OSNAPCOORD is set to 2:
'Keyboard entry overrides entity snap settings except in scripts'
This means (lisp is considered a script) that "_none" is required.

Note: this variable was 'broken' in V10 and V11.

Version:  OSNAPCOORD:  Is "_none" required:

V12       0            Yes
          1            No
          2            Yes

V11       0            Yes
          1            Yes
          2            Yes

V10       0            Yes
          1            Yes
          2            Yes

Knut Hohenberg

@Roy

Oops, you're completely right... I thought OSNAPCOORD=2 would only affect scripts, but it does affect lisp, too.

Must have forgotten about all this, when I look at the lisp stuff that I wrote (a long time ago), I always used "_none" to pass points...

MATTHIAS SCHWANNER

@Roy

can i put the link on my homepage? The tools are very good

Roy Klein Gebbinck

@Matthias:
Linking is allowed.
Dass würde mich sogar freuen.