Page 1 of 1

Annoying UI behavior--is this a bug?

Posted: Mon Mar 11, 2019 8:15 pm
by Carl
I've run into this very annoying UI "glitch" that sometimes occurs. Here are the steps to reproduce:
  1. Open several ditamaps in the DITA Maps Manager. In my test, I opened child (chapter) ditamaps from within my user manual.
  2. In one ditamap, open a topic for editing.
  3. Close the topic that you just opened.
Expected: The ditamap that was opened in the Maps Manager remains in focus.
Actual: The Maps Manager inexplicably switches to another open ditamap! This is really annoying because you lose mental focus as you're suddenly looking at a map that you weren't working with at the time.

I can reproduce this, but not consistently. Here is a video showing this glitch in action:

https://drive.google.com/open?id=1348Z_ ... 2Q1dBHe2qf_
  1. You see that phemi_central_spitfire_ui.ditamap initially has focus.
  2. I switch focus to export_destinations.ditamap and the open the topic Create a New Export Destination.
  3. I close Create a New Export Destination. My expectation is that export_destinations.ditamap remains in focus. However, you see that the focus has jumped back to phemi_central_spitfire_ui.ditamap!

Re: Annoying UI behavior--is this a bug?

Posted: Tue Mar 12, 2019 11:10 am
by sorin_carbunaru
Hello Carl,

As we use to say in the software industry, "it's not a bug, it's a feature" :D. This happens because you have the "Link with editor" option selected in the toolbar of the DITA Maps Manager, as shown in the image below.

Image

If this behavior bothers you, just disable it and it won't happen anymore.

All the best wishes,
Sorin Carbunaru
oXygen XML

Re: Annoying UI behavior--is this a bug?

Posted: Fri Mar 15, 2019 2:08 am
by Carl
Interesting. I just learned something new!

But, if you watch my video clip again, that "Link with Editor" button is not active (unless I'm misinterpreting the depressed/not depressed buttons. You really do need better icons!). The point may be moot though--I just tried my test again, with the button in both states, and the problem didn't resurface. So it may be an intermittent thing.