Since we can't have multiple visibility states in DB's (C'mon, man!), I am using a lookup table as a workaround (a-hem!)
I have a small panel indicating a 2" filler that I will need to show or hide. It has a dot hatch pattern in it. The block will (eventually) have other visibility states, so I can't use one for the show/hide. Instead, I'm attempting to "stretch" the rectangle (the hatch boundary) to a very small width (0.01"), essentially hiding the panel & its hatch pattern. I use a linear parameter (for the stretch) driven by a lookup (with "show" & "hide" options).
The hatch is associative, and will stretch properly, except when it gets that small. The hatch stays the original width (2"). Is there a limit to how "thin" a hatch boundary can be? In this case, I even adjusted the hatch origin so that there was just a row of dots still visible within the thin hatch boundary. No luck.
I left the linear grip on for testing. Once working, I'll turn it off.
Oh, for multiple visibility states......