HPTransparency

[Anonymous]

Is there a way to make the sysvar "HPTRANSPARENCY" stay at "."? I am using hatches from the tools palette that have a preset transparency which does not work if the sysvar is not set to ".". The issue is that every time I add hatch manually, hptransparency changes to the transparency of that hatch.

[CodeDing]

@Anonymous ,

Show us some of your settings.. I am having no such issue. (AutoCAD 2020)

Initial Check:

From Tool palette:

Hatch has a preset transparency:

Hatch object:

Hatch complete:

final check of HPTRANSPARENCY

Is this the same process you are referring to?

Best,

~DD

[Anonymous]

When using the tools palette hatches, that is the process.

But, if you do "HATCH", modify the transp. and then place the hatch it will also change the sysvar.

Placing this hatch would set HPTransparency = 0;

I though, before, it was also changing hptransparency when I simply modified the transparency of an existing hatch. But I am not able to replicate that right now, so maybe not.

[CodeDing]

@Anonymous ,

To my knowledge, HPTRANSPARENCY is essentially the variable which remembers your transparency for hatching.. So when you change the transparency before you add your hatch, AutoCAD decides "Hey, I should remember this for when they come back." so it updates the variable.

Now, it seems to me that since it seems you are updating this manually BEFORE adding your hatch, to fix this workflow (because I do not think there is a better way) then perhaps you could change your method to just selecting the hatch AFTER it was created and updating the settings then. It is essentially the Same process, but sadly with 1 small extra step, and that is having to select the hatch after you create it. That does not seem too painful though when you're hatching manually.. Now, if we were talking about a programming routine with many hatches, then we could find another solution, but for the purposes of hatching manually, this would seem to be the best solution.

Maybe not the answer you were hoping for, but the best answer I can think to provide.

-- Edit --

Alternatively, perhaps an argument could be made that your transparency should be controlled by your layering, then you would not have to concern yourself as much with the HPTRANSPARENCY variable.. We do not know enough about your workflow or the purposes of your hatches to argue that approach, but it is definitely something to consider.

Best,

~DD

[Anonymous]

Thank you for your answer. That all sounds like what I have been thinking the past couple days. 

Adding the hatch before changing the transparency isn't a terrible suggestion. For everyone else dealing with this in my office, I added to the save macro so hptransparency resets to "," everytime they save. That helps, but I will let them know they should just modify trans. after placing hatch.

I have thought about the bylayer option. That's not really a change I want to make at the moment.