Family Historian User Group

Issue - The Family Historian Window is far too sticky.

Example - Within FH, I choose to save an individual Narrative Report to a text file. I get prompted with a popup - do you want to open the file? I reply, too right I do.

In the background the file is opened in Notepad Tabs (my default for txt files), but FH remains stubbornly active. When I choose to create and open a file I expect it's default application to (1) open in a new window and (2) become the active window.

This is just an example, I have noticed this behaviour in others actions. It impacts me in that this is not the same way as other Windows applications behave, and I find that I spend time working out why the action I requested failed, when in fact it 'worked' fine, it is just hidden from me.

Is this a planned feature of FH or an unplanned one that is on a list for rectification? Or am I the only one who has this issue? ie a setting I should be changing.

Is there a list of future bug fixes, enhancements that I can get access to?

Elricks,

I don't use Notepad Tabs so can't say what happens with it. I use Notepad++ as my default txt editor. When I get the popup and say to open the file, the Notepad++ window opens in front of FH. So I can't reproduce your problem.

I do not know of any setting which impacts this. You might try using a different txt editor and see what happens.

Bill

That's weird - because Bill couldn't reproduce the problem, I tried it myself. (Like Bill, I use Notepad++ as my default text editor.) And Notepad++ came right up active / in focus / whatever.

Likewise, whichever of the Save Report As options I choose, after saving the file, the associated application opens in focus in front of FH, i.e. Windows Notepad, MS Word, Acrobat Reader, etc. The same applies to Save Diagram As and other FH commands that involve opening a file in another application.

So perhaps it is some unusual feature of Notepad Tabs or maybe it needs some setting adjusted so that when it open it becomes the active in-focus window.

My apologies, it must have been a 'temp' setting of some sort. Between raising the issue, and getting your reply I have rebooted my system, and It is now working OK for me.