[Framers] Processing time

[Mike Wickham]

This sounds a little like a bug I encountered in FrameMaker 9. If I used 
the arrow keys to scroll, the cursor moved extremely slowly and would 
travel at only about one character per second. I'm not sure what the 
issue was, but it occurred when the Paragraph Designer was open and got 
worse if the Character Designer was also open. The "Hide panels on 
Close" setting was the key. Perhaps this old bug has worked its way back 
into new code. It wouldn't be the first time with FM.

Anyway, Amit Agarwal of Adobe sent me a fix that worked for my problem. 
Perhaps it will solve your problem, too:

========

1. For the problematic workspace, check from Window -> Panels (this shows the list of open panels, the checked ones are visible panels, others are open but might not be visible)
2. Click on the para designer.
3. Now, with these steps:
	i.       File -> Preferences -> Interface
	ii.      Uncheck "Hide panels on Close" (This option kills a panel on close,
		   else a panel would stay open in the background)
	iii.     Close Para Designer

========

Mike Wickham

On 4/7/2021 11:49 AM, Harding, Dan wrote:
> It's definitely pod-based. With 0 pods displayed, I can move quickly through text using the keyboard and the CPU 1 load won't rise above 5%. However, as I display more pods on the screen, the load ramps higher, with Character Designer and especially Paragraph Designer being the worst offenders. Having just Paragraph Designer displayed and quickly moving through text will spike to 90%+ CPU 1 utilization. With both paragraph and Character designer, it maxes at 100% utilization almost immediately. Any more than those 2 open and there starts being noticeable lag in cursor movement.
>
> Since Frame apparently wasn't coded to utilize multiple CPU cores, modern CPUs with multiple cores/threads are of minimal benefit. What Frame wants is one ginormously powerful CPU core rather than distributed CPU power. Other Adobe apps like Photoshop were developed to utilize multiple CPU cores as well as the GPU horsepower... which is what Frame needs.
>
> Ugh.
>