Frame 2017 - Bug with the "Replace Fonts" pod?

[feline_1973]

I am getting annoying behaviour with the "Replace Font" pod on my dual monitor Frame 2017 set up.

Firstly, I have the Fonts pod open, with a list of all the fonts in my document.

If I double-click a font in that list, it opens the "Replace Font" pod...

but then, if I drag the Replace Font pod onto my 2nd monitor (out of the way of my document), it collapses, only leaving its title bar. The only way to reopen the pod is to click the button to reduce it to an icon, then click the icon to reopen the pod again.

Is this a bug? I've tried half a dozen other pods and I can drag them onto my 2nd monitor fine, without them collapsing to their title bar only.

[Barb Binder]

Is this a bug? I've tried half a dozen other pods and I can drag them onto my 2nd monitor fine, without them collapsing to their title bar only.

Certainly sounds like it. You can report it here: Tracker

[feline_1973]

If a couple more of you folks with 2-monitor setups can replicate it, I will!

[Arnis Gubins]

Does it end up looking something like this?

Unfortunately, it doesn't automatically collapse when I drag it on to my 2nd monitor. However, if I accidentally drag near the top right, I have activated the collapse icon control. Here's what I get trying to duplicate your scenario:

[feline_1973]

I'm on leave next week so I won't be able to try this out again until the week after - I don't *think* I was dragging via the top-right, but I'll experiment and let you know when I'm finally back in front of my computer at work!

[feline_1973]

Arnis, I'm back from leave now

And no, your suggestion isn't what's happening. I'm not accidentally clicking the "collapse to icon" control.

What I get looks like this:

The only way I can get the pod back is to click the little "<<" button to "collapse it to an icon" so that it *does* look like your screen grab - then I can toggle the collapsed version back to full visibility again.

So no-one else can replicate this?

[Stefan Gentz]

Thanks for reporting. We are already aware of this bug and are actively investigating it. We will provide a fix asap.

[feline_1973]

Thanks Stefan.