Break at Point

Break at Point

carl.coghill
Advocate Advocate
14,931 Views
10 Replies
Message 1 of 11

Break at Point

carl.coghill
Advocate
Advocate

Hi,

 

Please see attached screencast.

 

I have the same problem everytime I want to break multiple lines. I use the "Break at Point" tool.

 

The first time; it breaks the line at the point that I select.

I then press Enter to start the command again.

The second time; it breaks the line at the point that I select and also shortens the line.

 

Am I doing something wrong?

 

If I select the Break at Point tool fresh each time, then it works, but this is a slower way of doing things.

Carl Coghill
Senior Designer
AutoCAD 2018
Windows 7 Professional 64bit
LinkedIn
0 Likes
Accepted solutions (2)
14,932 Views
10 Replies
Replies (10)
Message 2 of 11

gotphish001
Advisor
Advisor
Accepted solution

That's how it functions unfortunately. I'm assuming the break at point just runs the break command with a sub-option, so when you hit return to redo the command it only does the break command and doesn't jump to the sub-option. 

 

I use break at point often so I added a button for it on the quick access toolbar. The button functions the same if I use it and then hit enter it only runs the break command on the second use. Pressing the button each time is still faster for me than the alternative of opening the modify tab then opening the break command drop down to select the break at point tool.

 

Before I added the button I would use the break command then press F to pick first point. I would then just pick the first and second points as the same point at the location I wanted to break the line. You could do it that way if you didn't want to mouse click a button and only use keyboard shortcuts.

 

You could also make a keyboard shortcut for the break at point command and use that each time. I don't think it has a default shortcut.

 

 



Nick DiPietro
Cad Manager/Monkey

Message 3 of 11

imadHabash
Mentor
Mentor

Hi,

 

the only way to work successfully with BREAK at point ( ribbon command ) is to select it always from ribbon every time you want to use.you may need a macro that could serve your issue.

Imad Habash

EESignature

0 Likes
Message 4 of 11

Kent1Cooper
Consultant
Consultant

@gotphish001 is correct that the menu icon calls a command macro that feeds in some options to the BREAK command, but does not call a defined command that itself includes those options, so when you hit Enter to recall, what is recalled is just the "root" BREAK command.

 

You can define a specific command name  that does the same thing, such as this:

 

(defun C:BF1 (); = Break with First option at 1 point
  (command "_.break" pause "_first" pause "@")
)

 

and then make that  the command that is called by that button, rather than the macro of the basic command with First option and @.  In the CUI Editor:

 

BreakAtPoint.PNG

 

Then, when you hit Enter after using it, it's the BF1 command that is recalled, not just the BREAK command.

 

Make sure that command gets loaded in every drawing by acaddoc.lsp, or you'll get an unknown-command error when you pick on that menu icon.

Kent Cooper, AIA
Message 5 of 11

Anonymous
Not applicable

HI

 

BREAK AT POINT TOOL DON'T HAVE COMMAND.

 

And Break At Point is a Section of Break command.

 

So that, if you press enter, Break command will goes to active.

0 Likes
Message 6 of 11

Kent1Cooper
Consultant
Consultant

@Anonymous wrote:

.... 

BREAK AT POINT TOOL DON'T HAVE COMMAND. .... So that, if you press enter, Break command will goes to active.


Exactly, as already pointed out twice.  My suggestion was to make  the icon in the ribbon have a special-purpose Break command, so that if you press Enter, that special command will be what is recalled.

Kent Cooper, AIA
0 Likes
Message 7 of 11

Anonymous
Not applicable

Excellent. It works. But ¿how can i put the lisp permanent, so i can not have to paste the command in every session?

 

Thank you a lot!


@Kent1Cooperwrote:

@gotphish001 is correct that the menu icon calls a command macro that feeds in some options to the BREAK command, but does not call a defined command that itself includes those options, so when you hit Enter to recall, what is recalled is just the "root" BREAK command.

 

You can define a specific command name  that does the same thing, such as this:

 

(defun C:BF1 (); = Break with First option at 1 point
  (command "_.break" pause "_first" pause "@")
)

 

and then make that@  the command that is called by that button, rather than the macro of the basic command with First option and @.  In the CUI Editor:

 

BreakAtPoint.PNG

 

Then, when you hit Enter after using it, it's the BF1 command that is recalled, not just the BREAK command.

 

Make sure that command gets loaded in every drawing by acaddoc.lsp, or you'll get an unknown-command error when you pick on that menu icon.


 

0 Likes
Message 8 of 11

Anonymous
Not applicable
Accepted solution

At the CUI simply just edit the 'Break at point' command macro:
put an asterisk >>   *   << at the front, so it will stay in the command:

 

^C^C_break \_f \@   >>   *^C^C_break \_f \@

 

You can exit with ESC.

Message 9 of 11

Anonymous
Not applicable
(defun c:BAP (/ entity point)
(setq entity (entsel))
(setq point (getpoint))
 
(command "_.break" entity "_F" "_non" point "_non" point)
 

)

I use this most of the time.

0 Likes
Message 10 of 11

Anonymous
Not applicable

Hello,

Thanks OP for the similar question. Thanks portabl3lapy for the lisp! I like it, but I kind of like the idea of placing a POINT object at the location of the break point. I am only familiar with lisp through using other's routines, but it seems that this would be a simple addition to your lisp. Do you know how this could be added, by chance?

 

Thanks,

Michael

0 Likes
Message 11 of 11

Anonymous
Not applicable

Nevermind, I figured it out.

 

I just added the following:

 

(defun c:BAP (/ entity point)
(setq entity (entsel))
(setq point (getpoint))
 
(command "_.break" entity "_F" "_non" point "_non" point)
(command "_.point" point)
 

)

 

Thanks again for the lisp!

Michael

0 Likes