make hatch layer default to use current

make hatch layer default to use current

tpl_arch
Contributor Contributor
3,353 Views
12 Replies
Message 1 of 13

make hatch layer default to use current

tpl_arch
Contributor
Contributor

In ACAD 2021, how can I make the hatch layer default to "use current" rather that whatever the last hatch layer was.

This wasn't a problem in previous releases.

0 Likes
3,354 Views
12 Replies
Replies (12)
Message 2 of 13

MSchille-1994
Collaborator
Collaborator

There is a function within the ribbon to use the current layer as the default layer.

Attitude, not Aptitude, Determines Altitude
0 Likes
Message 3 of 13

tpl_arch
Contributor
Contributor

I want that the current layer all the time unless I change it. Right now it defaults to whatever the last layer used was

0 Likes
Message 4 of 13

MSchille-1994
Collaborator
Collaborator

So once you set the default to be Current, does that stick the next time you try to hatch something?

Attitude, not Aptitude, Determines Altitude
0 Likes
Message 5 of 13

MSchille-1994
Collaborator
Collaborator

Try this............

 

MSchille1994_0-1713534691842.png

 

Attitude, not Aptitude, Determines Altitude
0 Likes
Message 6 of 13

tpl_arch
Contributor
Contributor

If you use "inherit properties" when doing one hatch, the next time you go to hatch, it defaults to that last layer you match properties for. I want it to always default to "use current" as on this screenshot. It has nothing to do with colors, just layers

0 Likes
Message 7 of 13

pendean
Community Legend
Community Legend

@tpl_arch wrote:

In ACAD 2021, how can I make the hatch layer default to "use current" rather that whatever the last hatch layer was.

This wasn't a problem in previous releases.


Nothing has changed between versions, unless your last version was in the 2000 era.

You need to always control and keep track of your HPLAYER command either with a startup LISP or taking advantage of and using SYSARMONITOR command to keep track of all the HP variables settings that matter to you like I do here

pendean_0-1713537791487.png

 

0 Likes
Message 8 of 13

Kent1Cooper
Consultant
Consultant

@tpl_arch wrote:

If you use "inherit properties" when doing one hatch, the next time you go to hatch, it defaults to that last layer you match properties for. ....


Yes, using that choice in the Hatch seTtings option dialog box does put the Layer of the Hatch pattern you select into the HPLAYER System Variable, making it the Hatch Layer but not otherwise the current Layer.  I can see the preferability of having it set that Layer current, and leave HPLAYER alone.  I take it you want HPLAYER to revert to "<use current>".  Do you also want all the other Hatch properties that were matched [pattern name, scale, angle, associativeness, if User-defined, spacing and single- vs. double-direction] to revert to what they were before, or do you want those to remain as defaults?

 

When wanting to Make More of an existing Hatch pattern, without changing the HPLAYER setting, my MakeMore.lsp with its MM command, >here<, works as I think you want, if used instead of the "Inherit Properties" button in Hatch seTtings.  It sets all those other things, including the Layer it's drawn on, but it does that by making it the general current Layer, not by changing the HPLAYER setting, so that will remain set to "<use current>" if that's your setting at the time.

Kent Cooper, AIA
0 Likes
Message 9 of 13

tpl_arch
Contributor
Contributor

Thanks, I just want the one property "use current" to remain the default every time.

Is there a way to do this without any other lisp routines?

0 Likes
Message 10 of 13

MSchille-1994
Collaborator
Collaborator

Did you check the System Variable setting I posted earlier?

Attitude, not Aptitude, Determines Altitude
0 Likes
Message 11 of 13

tpl_arch
Contributor
Contributor

The HPlayer value is set to "."  The problem is after you use "inherit properties" one time, it hold that layer on the next command rather then go back to "use current"

0 Likes
Message 12 of 13

MSchille-1994
Collaborator
Collaborator

My bad, this is a drawing setting rather than a registry setting.  The only thing I could think of is having a script or a custom button that you program a string in, that runs the hatch command and after the hatch command, sets the HPLAYER back to "current".

Attitude, not Aptitude, Determines Altitude
0 Likes
Message 13 of 13

pendean
Community Legend
Community Legend

@tpl_arch wrote:

...The problem is after you use "inherit properties" one time...


Exactly: as you may have noticed, your actions there changed HPLAYER's settings. To go back, you have to change it yourself too from the same pop-up (or commandline).

 

 

Point is, there is no auto-reset in the program if you the user don't create the auto-reset first. AutoCAD has no such option if you id not like or wish to use my tip in my last reply about using SYSVARMONITOR command.

 

Does that all make more sense now?

 

To recap:

1) If you only launch HATCH command from a button, then you can add HPLAYER to the start of the button macro in CUI command.
2) If you only type H to launch HATCH command, you create a LISP that is called H that does that and in the interim sets HPLAYER back.

3) if you do both, as many do, you'll need to pre-plan to have both fixes in place first.

4) Commit to only using SYSVARMONITOR command and it's alerts to reset everything back.

5) Startup Script, but that only works once.

 

How would you like to proceed? 1, 2, 3 and/or 4?

 

Let us know. Choices are limited my friend.

0 Likes