mc-hidden vs mc-disabled

[mojebabicka]

Hello all,

I was just wondering what is the difference between mc-hidden and mc-disabled. Until now we have used mc-disabled and it was ok. But now I stumbled uppon mc-hidden and it made me wondering. I suppose the only difference is that mc-disabled will hide the style from UI and from stylesheet editor in Flare but mc-hidden will hide the style only from the UI and it will still be visible in the stylesheet editor. Am I right?

Best Regards,

Tomas

[NorthEast]

It appears to work that way - it's not actually documented though, so it's trial-and-error to see if there are any other differences.
http://webhelp.madcapsoftware.com/flare ... erties.htm

[MCPBecker]

I can't see that the setting does anything. The styles I have marked mc-hidden: hidden, still show in the Style Window. I'm really looking for a way to shut these off. What might I be doing wrong?

[dorcutt]

using the Options- Disabled dialog in the Stylesheet has worked for me. I'm not using this on any "mc" styles or any unclassed "base" tags, and it's been working well for me. No issues so far.

Not sure why mc-hidden isn't working for you, though. That's kind of weird; I'm pretty sure it worked for me once I used the proper syntax. I just use "disabled" because of the convenience of the dialog.

[ChoccieMuffin]

Careful with disabling styles that you don't use, as there are some styles that you won't use but that are still needed (e.g. <a>, which is used for hyperlinks). I learned that the hard way. I would love to have a way to hide these styles in the Flare UI so that only the styles I actually apply are in the list, but until that happens, I just have to live with it.

[dorcutt]

My general rule is to NEVER disable a base, unclassed tag. I think that helps you avoid at least 90% of issues. Also, keep in mind if something weird happens to think about the disabled styles first.

[MCPBecker]

Careful with disabling styles that you don't use, as there are some styles that you won't use but that are still needed (e.g. <a>, which is used for hyperlinks). I learned that the hard way. I would love to have a way to hide these styles in the Flare UI so that only the styles I actually apply are in the list, but until that happens, I just have to live with it.

Yes. "Living with it" is giving me carpal tunnel syndrome. Scroll, scroll, scroll to format. Ugh. It's driving me nuts and hurting my hand. Applying a common style should only take one click. Anything else is bad UI design. At least let us make some custom buttons or keyboard shortcuts.

[Msquared]

Submit a feature request for the ability to define shortcut keys. I have dozens I use every day in Word for applying styles and I do miss them for Flare. I think that was the first feature request I submitted back when I started with Flare 7. Obviously MadCap don't think it's that important.

Like you, I now have loads of styles to scroll through too.

[ChoccieMuffin]

Feature request submitted:

Subject:
Make it easier to apply frequently used styles or hide unused styles without disabling them

Description:
To apply a style I use very often, I highlight the text or paragraph I want to apply a span to, and then in the Styles window have to scroll down past all the styles I never use to get to the span or p class I have defined.
Several suggestions to help alleviate my RSI.
Allow the user to do one, or several of the following:
* Hide styles from the Styles window without disabling them.
* Select frequently used styles from a separate, user-defined Favourite Styles window.
* Create and use keyboard shortcuts for applying styles (FrameMaker has been doing this forever).

You will get a MASSIVE vote of thanks from your users if you can do this.

Feel free to submit a feature request - the more people that do so, the more likely it is that MadCap will listen. (Link in my footer.)

[dorcutt]

I submitted a related request, but it more focused on being able to customize shortcuts and to provide a more universal, user-configurable shortcut system.

The "favorite styles" menu is pretty sweet, though. I like that idea quite a bit... especially if it came with built in shortcuts (ctrl-1 through ctrl-4 and shift ctrl-1 through shift ctrl-4 was what I used in word and worked really well)