Break bug?

Why is it that sometimes the break command prompt is different from other times.

Command: break
Select object:
Specify second break point or [First point]: f

Specify first break point:
Specify second break point:

So all is fine until you use it again.

Command: break
Select object:
Specify first break point:
Specify second break point:

Is there a reason for this or is it just another anomally that has been ignored by Autodesk for ever.

Bill

 

Curious, I get the same sort of thing (R2002). Perhaps first time in (this session), break inits the points, based on optional 'F'. Then, assumes you want to pick 'F'irst next time. I doesn't seem to want you to select the '2nd' point - keyword not there..S doesn't do it..
SO, why does it bother to ASK ?. Just go ahead and do 1st, 2nd and do it..gees.


Bob

 

It also seems to make a difference it you "pick" the object or pass an ename like (entlast).
The only reason I asked was because I ran into some trouble with a command call in lisp (command "break" pause pt "@")
so I though I'd better ask in case there was some logic to the madness.

Thanks

Bill

 

I see the quandry. I always calculate the points, then do
(command "_break" "_c" pt1 pt2 pt3 pt4)
..where pt1 and pt2 are +- 0.0625 from 'pick' point and
pt3, pt4 are breakpoints. This way, it grabs a line, checks for
'LINE', then proceeds.
I haven't used it 'interactive', and repeated..so I don't know if
you can get around it or not..good question.

Bob

 

Works like I would expect, here. Sounds like you have some other app redefining BREAK. Try using .break (notice dot) see if it still acts odd.