RamonS wrote:Worth a try, but given the many complaints about other issues with RH9 in the Adobe forums you are gaining a bit and loosing somewhere else.
I can only speak to the robohelp IDE itself. The v9 IDE is much faster and responsive than Flare's is. There are also a long list of problems in Flare (keyboard-friendliness, presentation of conditional text and elements, etc) that are not present in RH9.
Before jumping over to Flare, be sure RH9 is not a fit. If RH9 works, use it.
My entire documentation team experiences this issue with Flare as well, but we also notice a strange behavior based on project size:
For projects 20MB or smaller, Flare will wind down to 0% CPU usage when idle. For projects 40MB in size and larger, Flare never goes less than 50% CPU usage, even when completely idle. No matter how big the project gets (120MB+) the CPU will never idle more or less than 50%.
We all have a minimum of Intel Core 2 Duo @ 2.4Ghz, and our new machines are coming with core i7's and stil experience the same issue.
TechnicalDisaster wrote:My entire documentation team experiences this issue with Flare as well, but we also notice a strange behavior based on project size:
For projects 20MB or smaller, Flare will wind down to 0% CPU usage when idle. For projects 40MB in size and larger, Flare never goes less than 50% CPU usage, even when completely idle. No matter how big the project gets (120MB+) the CPU will never idle more or less than 50%.
We all have a minimum of Intel Core 2 Duo @ 2.4Ghz, and our new machines are coming with core i7's and stil experience the same issue.
Definitely report this to MadCap (assuming you haven't already done so). I have projects of several hundred MB where I do not encounter this issue; however, those projects *do* stick at 50% CPU for a while at times, because they are (presumably) updating the analyzer database.
Andrew wrote:Definitely report this to MadCap (assuming you haven't already done so).
I have opened this issue with MadCap multiple times and have gotten absolutely nowhere.
I don't think MadCap tech support can help on this one (that is my clear experience).
The more reports they get, the more likely it is they can pin down what might be wrong. And, indeed, the problem TechnicalDisaster's team is suffering may not be the same one you are.
Submitting issues is the best way to get these issues taken care of. Please don't let anyone discourage you from submitting problems to Tech Support.
Support may not be able to solve a particular issue, but they can get it to the development team which may lead to getting the problem solved.
rhollinger wrote:Submitting issues is the best way to get these issues taken care of. Please don't let anyone discourage you from submitting problems to Tech Support.
Support may not be able to solve a particular issue, but they can get it to the development team which may lead to getting the problem solved.
The discouraging thing is how I can work on an issue for a long time with madcap and get nowhere.
This is an issue in Flare, but they waste time going in other directions.