MadCap Software Forums

Thanks for the input guys. Definitely I prefer not to have them download anything--ideally I would like to put the HTML5 content up on a website for them to view.

I want to be able to distribute my Flare output to potential clients or others, preferably giving them a link--for free, if I can, (assumption is that they do not have Flare, just want to show the HTML5 output, for example). Since I store my Flare project in Dropbox, I tried sharing a link for the ....

No matter what I do, I seem to have a problem with the PNG images in my WebHelp Mobile output looking low-resolution. I don't know why this has happening. I tried unchecking the "automatically resize low DPI images " option in Options > General tab but to no effect. Any ideas? This is maki...

We have two targets, a desktop HTML5 one and a mobile Webhelp Mobile one. Normally, if a user is on the Desktop version of the application, they see the HTML5 Desktop version, and if they are on a mobile device, they will see the Webhelp Mobile version. Here's what I am trying to do: when a user is ...

Actually strangely enough, it shows when I use show:Property Groups. However if I show:Set Properties it doesn't show. How does that make sense?

Yes it appears on the stylesheet in both mediums.

I have a class of span in my stylesheet that is supposed to tell the text to be a certain font size and weight. For some reason, though it shows up in HTML5 output, it doesn't in the WebHelp Mobile target. Any ideas on what is going wrong here?

Yeah I am pretty sure that responsive output isn't going to cut it here. Basically we are now developing a version of our web application which is nearly the same but has a different UI for mobile/tablet purposes. Naturally, there will be some small but significant sections of the help that should d...

Yes it seems that responsive output probably isn't appropriate for this purpose. I was hoping it would be, because it is so much easier to set up. But, if I am reading your responses correctly, conditioning text doesn't seem to be an option in responsive output, at least not without some kind of com...

The problem here I am trying to solve is that this is a web-application that we are also going to have a mobile (web-based) application for. Some topics (or parts of topics) will not be applicable to mobile. My goal here is to try to find the best way of excluding text from the help when it is click...

Is it possible to condition text to appear (or not) in the three different mediums of an HTML5 skin with responsive output?

I.e., some text that is applicable to mobile to not appear in the same help page when it is at desktop resolution, etc.

I am building help for an online application and we want to introduce a mobile version. Is it possible to publish two targets to the same URL and have the mobile target only show up for mobile and the primary target when you are on the desktop?

Actually, I am not even sure where to begin with this issue.

Or maybe get rid of Avast entirely, since it is a drain lol

Sounds complicated, on the face of it...

I have been trying to set the output of a Relationships proxy to look like a Related Topics or Concept help control popup. So far, my efforts have fallen flat. Is there a way to do this?

What do you want to have happen? I want there to be only one spelling of the glossary term in the glossary, while having the ability to have glossary term links on multiple spellings. For example, defining a glossary term "action" which also encompasses "Action", "actions&q...

Does anyone know the best way to allow for multiple spellings of a given glossary term? I know that Flare lets you insert several different terms (one per line) in the Glossary dialog, however this results in multiple glossary entries, one for each spelling or use of capitalization. This adds an und...

All I can see in the source is that dropDownHead is like a container for the dropDownHotspot. I am not sure what else it does...

What I don't understand is: what is dropDownHead for? To change the heading only dropDownHotspot seems to work...

I tried adjusting margin-left and margin... neither results in any change. I must be missing other property?

Oh so I need to try margin or padding instead?

I thought this way--but so far I created a class for MadCAp | dropDownBody and adjusted, for example, the text-indent. This seems to do nothing--it looks exactly like the other drop-downs

I have tried messing with the advanced Stylesheet Editor and creating new classes, but I can't seem to get drop-down text and headings to indent so they start farther to the right than the standard drop-down. Anyone have insight/experience on how to do this? I am not sure which properties I should b...

Can you point us to a public example that we can look at? What version of Flare are you using? Does the topic you are looking at (when you try to click the next/previous button) exist in your TOC structure? Absent a browse sequence, Flare uses the TOC structure to figure out where to go with the pr...