Style Window shows too many
Style Window shows too many
Is there a way to shorten up the list of styles in the Style Window? I have a lot of styles that are only used programmatically and should never be applied directly. I don't want these styles to show up in the Style Window as they cause a whole lot of unnecessary and painful scrolling. I have tried to apply the mc-hidden parameter to these styles, but that seems to have no effect. They can't be disabled, because they are actually used.
~M Becker
-
atomdocs
- Sr. Propeller Head
- Posts: 308
- Joined: Tue Jun 18, 2013 3:00 am
- Location: Eastern Seaboard, Thailand
- Contact:
Re: Style Window shows too many
Hi M, this works ok for me. How did you set it up - by editing the stylesheet directly, or through the Flare gui? If you edited it directly, did you set the value to hidden?
Also check that you've set it up in the right medium (and that you are viewing topics with the right medium toggled).
Also check that you've set it up in the right medium (and that you are viewing topics with the right medium toggled).
Tom
Flare 2022, Capture 7

Flare 2022, Capture 7

Re: Style Window shows too many
I don't quite get what you mean by 'used'.MCPBecker wrote:They can't be disabled, because they are actually used.
Disabling a style removes it from the styles list, XML editor and stylesheet editor; but it doesn't affect that style in the output.
I have dozens of disabled styles which are used in the output, but I don't want people to be able to select them from the Styles list in a topic.
Setting mc-hidden: hidden also appears to work, although it's not a documented feature so I can't comment on what it is intended to do.
-
ChoccieMuffin
- Senior Propellus Maximus
- Posts: 2650
- Joined: Wed Apr 14, 2010 8:01 am
- Location: Surrey, UK
Re: Style Window shows too many
I clearly remember an instance when I disabled the <a> tag that I never apply via the styles window and I managed to break my build.
Quote from Flare Help:
Warning: Even if you have some styles that you never modify, you may want to avoid disabling them in your stylesheet. The reason for this is that disabling a style in a stylesheet also disables its use in the rest of the interface. For example, let's say that you have inserted several images in your project. When you do this, an <img> tag is used. Therefore, although you may never edit the style properties for the <img> tag, you still require it in order to insert images in the future. Otherwise, features such as the option to insert images become disabled in the interface. The bottom line is that you should use caution when disabling styles, making sure that you truly will not need to use those styles.
Quote from Flare Help:
Warning: Even if you have some styles that you never modify, you may want to avoid disabling them in your stylesheet. The reason for this is that disabling a style in a stylesheet also disables its use in the rest of the interface. For example, let's say that you have inserted several images in your project. When you do this, an <img> tag is used. Therefore, although you may never edit the style properties for the <img> tag, you still require it in order to insert images in the future. Otherwise, features such as the option to insert images become disabled in the interface. The bottom line is that you should use caution when disabling styles, making sure that you truly will not need to use those styles.
Started as a newbie with Flare 6.1, now using Flare 2024r2.
Report bugs at http://www.madcapsoftware.com/bugs/submit.aspx.
Request features at https://www.madcapsoftware.com/feedback ... quest.aspx
Report bugs at http://www.madcapsoftware.com/bugs/submit.aspx.
Request features at https://www.madcapsoftware.com/feedback ... quest.aspx
Re: Style Window shows too many
Curious. You had build errors due to a disabled property?ChoccieMuffin wrote:I clearly remember an instance when I disabled the <a> tag that I never apply via the styles window and I managed to break my build.
I have several a tags in my CSS which are disabled, and I've not experienced problems; same goes for p, div, or generic classes.
Most of the styles I disable are for alterations to MadCap generated styles in the output.
It isn't advisable to disable styles just for the sake of it, and I'm aware that you can break parts of the interface; e.g. if you disable MadCap|dropDown, you can't insert dropdowns.
-
kwag_myers
- Propellus Maximus
- Posts: 810
- Joined: Wed Jul 25, 2012 11:36 am
- Location: Ann Arbor, MI
Re: Style Window shows too many
It seems the Style menu has been taking a lot of punches lately, as we've been discussing this feature in a number of threads these past few weeks:
how to turn off preview of stylesheets in style select menu?
IMG class not appearing in UI
To answer the OP, you have two options:
1. If you have dual monitors, float the Style Window to the secondary monitor and go full screen.
2. Use the context menu as suggested in the IMG class not appearing in UI thread. The context menu limits the list of styles to classes for the style:
how to turn off preview of stylesheets in style select menu?
IMG class not appearing in UI
To answer the OP, you have two options:
1. If you have dual monitors, float the Style Window to the secondary monitor and go full screen.
2. Use the context menu as suggested in the IMG class not appearing in UI thread. The context menu limits the list of styles to classes for the style:
You do not have the required permissions to view the files attached to this post.
"I'm tryin' to think, but nothin' happens!" - Curly Joe Howard
Re: Style Window shows too many
I have styles that are apparently only used by madcap. For example, if the styles MadCap|snippetBlock and MadCap|snippetText are disabled, you can't drag snippets into your topic. I am using jquery to make a tabbed interface. If I disable the styles that format the tabs, they come out as plain text.Dave Lee wrote:I don't quite get what you mean by 'used'.MCPBecker wrote:They can't be disabled, because they are actually used.
Disabling a style removes it from the styles list, XML editor and stylesheet editor; but it doesn't affect that style in the output.
I have dozens of disabled styles which are used in the output, but I don't want people to be able to select them from the Styles list in a topic.
Setting mc-hidden: hidden also appears to work, although it's not a documented feature so I can't comment on what it is intended to do.
Maybe I am confused.
~M Becker
Re: Style Window shows too many
I don't understand the point of diabling/hiding MadCap| styles, since they don't actually appear in the Styles list - which I thought was the reason in the original post.MCPBecker wrote:I have styles that are apparently only used by madcap. For example, if the styles MadCap|snippetBlock and MadCap|snippetText are disabled, you can't drag snippets into your topic. I am using jquery to make a tabbed interface. If I disable the styles that format the tabs, they come out as plain text.
Maybe I am confused.
If you disable/hide styles like MadCap|snippetBlock, it means you can't add a snippet via the Flare interface; but it doesn't actually break the build - i.e. snippets in your project are still built correctly in the output. But again, I don't see why you'd want/need to disable/hide the style in the first place.
I'd assumed you'd wanted to hide styles that are actually displayed in the Styles list/picker; e.g. things like superfluous p, div, span, or headings.
All the disabled/hidden styles that I use still work fine in the output; i.e. the styles still exists in the output CSS.
Re: Style Window shows too many
I think something has gone awry with my setup. The image shows what I see in my Style Window and also in my Create Group dialog. There are lots of styles there that I should not see. I also have two linked style sheets that deal with Jquery scripts that I don't want to see styles from. AND, contrary to other people's posts, stuff stops working when I disable styles, like being able to drag snippets into my topics. As far as I can tell from my experiments, disabling a style makes it not work. There's something going wrong here. Would it help to post my .css files?
You do not have the required permissions to view the files attached to this post.
~M Becker