Clipboard operation exceptions persist in Flare 7.01

This forum is for all Flare issues not related to any of the other categories.
Post Reply
IanFrangs
Jr. Propeller Head
Posts: 3
Joined: Tue May 24, 2011 12:25 am

Clipboard operation exceptions persist in Flare 7.01

Post by IanFrangs »

Today, Flare 7.01 has FRUSTRATING decided to complain about 80% of my copying, cutting and pasting operations, with the following exception message: Failed to run command 'Cut' or 'Copy' or 'Paste'.

Rebooting and restarting Flare did not help and, since I have just installed Flare 7.01 on Windows 7 SP1 two days ago, as I reformatting my computer and moved from XP to Windows 7 - I double that reinstalling will help either.

Reading the forums, I see that this issue that ONLY AFFECTS FLARE, has raised its head in earlier version of Flare too. And in the past this issue has been blamed on the Windows operating system, which is strange since this problem is ALWAYS reported as a problem that is localized to Flare.

Is there a workaround for this issue and/or will it be addressed in future updates of Flare?

Ian.
IanFrangs
Jr. Propeller Head
Posts: 3
Joined: Tue May 24, 2011 12:25 am

Re: Clipboard operation exceptions persist in Flare 7.01

Post by IanFrangs »

Clearing the clip board seems to do the trick 8) - but why is this ONLY necessary for Flare?
nickatwork
Sr. Propeller Head
Posts: 457
Joined: Thu Sep 16, 2010 6:31 am
Location: London

Re: Clipboard operation exceptions persist in Flare 7.01

Post by nickatwork »

Out of curiosity, what kind of content are you pasting? I've never seen or heard of this at all...
Andrew
Propellus Maximus
Posts: 1237
Joined: Fri Feb 10, 2006 5:37 am

Re: Clipboard operation exceptions persist in Flare 7.01

Post by Andrew »

This used to happen to me all the time (maybe 25% of copies -- and it typically happened in a cluster). The copy still worked, it was simply annoying to click through an error message frequently. However, it's been almost non-existent in the past couple of Flare versions (possibly since v4, and definitely since v6), so it seems to be something MadCap is working on.

I'd report this as a bug - the more MadCap hears about a problem, the more likely they are to spend resources to address it.
https://www.madcapsoftware.com/bugs/submit.aspx
Flare v6.1 | Capture 4.0.0
Post Reply