Submitted by DavidF on 2016/11/18 16:34
hi,
 
I'm finding in 0.9.86b that F12, instead of moving focus to the HTML Pane (which is open), opens a new HTML Pane.
 
DavidF.

Comments

Works here... perhaps reset your keyboard shortcuts
What does View > Goto Pane > Grid << >> HTML pane  do ?
 
Pierre_Admin
IQ Designer
 

DavidF

2016/11/18 19:55

In reply to by Pierre_Admin

... gone back in and now it's back to normal. I think this has very occasionally happened in previous versions as well. Nothing special about the setup: at first, F12 (or View > Goto Pane etc) always created a new HTML pane; close and reopen and it's OK. Not a major problem.
 
DavidF.

I had this too.
The way I solve it when it happens : in my main HTML pane, I click on "Lock editor on this item" (the icon is a little black lock) and redisable it.
 
-
IQ geek
Windows 8.1
CPU: Intel i5 2.6ghz

DavidF

2016/11/19 08:46

In reply to by Armando

Thanks Armando, I'll try that if it happens again.
 
DavidF.

DavidF

2016/11/19 09:43

In reply to by Armando

... tried the "switch lock pane on and off" solution. Didn't work. F12 consistently opens a  new HTML pane rather than give focus to the one that's there. I haven't tried this in different databases or with different layouts loaded to see if there's any common factors at work.
 
DavidF.

Armando

2016/11/19 11:41

In reply to by DavidF

[quote=DavidF]
... tried the "switch lock pane on and off" solution. Didn't work. F12 consistently opens a  new HTML pane rather than give focus to the one that's there. I haven't tried this in different databases or with different layouts loaded to see if there's any common factors at work.
 
DavidF.
[/quote]
 
Try to first close all HTML panes.
Then open one HTML pane and see if it works again (F12)
If not, switch the lock on, then see what it does. Then switch it off. 
I remember this fixed it at some point, but it hasn't happened in a while.
 
-
IQ geek
Windows 8.1
CPU: Intel i5 2.6ghz

DavidF

2016/11/19 11:57

In reply to by Armando

In the end it seemed to only be affecting one database, so I did what I should have probably tried before - Database Repair. And it worked! Somehow I didn't expect that.
 
DavidF.