[Framers] more non-responsive pods - Reset Workspace might help

[Monique Semp]

Short story/theory:
* Resetting the workspace might fix things with respect to non-responsive 
pods.

Long story:

All of a sudden yesterday, the FrameMaker 2015 pods, which have been stable 
and placed in the same positions/tab groups for months and months (on the 
right: top tab group for the .book file; middle tab group for 
char/para/table catalogs/designers; bottom tab group for Cross References, 
Text Insets, Variables, and Conditions pods—yes, I have a big monitor that 
enables reasonable usability space for three stacked tab groups: 2560x1600 
:-) all of a sudden all disappeared, except for the .book file !

I've gradually added them back as I need them, and just today I noticed that 
the Cross Reference and Text Inset pods are non-responsive, as Keith Soltys 
described. But when I move the pods out of the group, the pods are again 
responsive.

Unlike Keith, I haven't deliberately changed/moved any of the pods/tab 
groups, so I don't know what caused them to disappear and to be 
non-responsive when re-added. But something sure went haywire. So I just 
tried resetting the workspace and (again) rearranging things as I want, and 
now things seem to be all working again. I don't know how long this fix will 
work, or if it actually isn't fixed, but time will tell.

And like Keith, I hope that this saves someone else some time.

-Monique


-----Original Message----- 
From: Keith Soltys
Sent: Friday, May 20, 2016 10:30 AM
To: Framers Mailing List (framers at lists.frameusers.com)
Subject: [Framers] Odd conditional text behaviour with two monitors

I’m using FrameMaker 10 on a 64-bit Windows 7 PC with two identical 23” 
monitors. My primary monitor is on the right.

Generally I keep most of my tabs and pods on the main monitor, but on the 
current document it seemed easier to move some of them to the secondary 
monitory. I just spent 10 minutes trying to figure out why my conditional 
text pod wasn’t responding (I could select a conditional but the selection 
buttons and icon buttons didn’t work). It finally occurred to me that 
usually I kept this pod at the bottom of my main monitor. As soon as I moved 
it back it worked again.

I haven’t noticed this with any other pods or dialogs.

Obviously this will never get fixed and I don’t have a more recent version 
of Frame to test to see if it affects later versions. I point it out just in 
case it might save someone else a bit of time.

Regards
Keith

--
Keith Soltys
Senior Technical Writer
Architecture
TMX Group
(416) 947-4397
http://www.tmx.com/

<snip - administrivia>