GnuCash
Contact   Instructions
Bug 795071 - new account entry screen keeps on disappearing and coming back
Summary: new account entry screen keeps on disappearing and coming back
Status: RESOLVED INCOMPLETE
Alias: None
Product: GnuCash
Classification: Unclassified
Component: User Interface General (show other bugs)
Version: 3.1
Hardware: Other Windows
: Normal normal
Target Milestone: future
Assignee: ui
QA Contact: ui
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-08 07:02 EDT by Wm
Modified: 2021-09-23 16:04 EDT (History)
7 users (show)

See Also:


Attachments

Description Wm 2018-04-08 07:02:37 EDT
using either
Actions / New account
OR
Right click / New account

the New account entry window appears and then after a second or two disappears.  You have to click on it somewhere to make it stay there so you can enter the details of the new account.

I think it is something to do with where the mouse pointer is when the window appears on the screen /focus ?
Comment 1 John Ralls 2018-04-08 15:59:01 EDT
I'm not able to reproduce this. Does it happen on your Mac too?
Comment 2 Wm 2018-04-09 05:31:24 EDT
I don't have a Mac, I've just started building 3.0 on Linux in case it helps me describe this better.

This also happens with 

Tools / Price database
Tools / Security editor
File / Properties

you should get the idea

The subsidiary window isn't actually disappearing (I had the main gnc window full screen before) it is moving behind and in front of the main window, i.e. the focus is changing between the (virtual?) gnc windows.  So if you have a larger screen and the windows weren't substantially overlapping or obscuring each other you probably wouldn't notice it.

If we get stuck describing this I can make some screen shots.
Comment 3 Geert Janssens 2018-04-28 11:01:52 EDT
Do you have some autofocus (focus-follows-mousepointer or something like that) feature enabled on your windows box ?
Comment 4 Wm 2018-04-29 07:25:25 EDT
No autofocus, etc.  I think this will end up as a dup of 794853 or certainly likely to be related to it and fixed if that gets fixed

screen shots don't help as they don't show the "windows" (or whatever they are called now) switching of their own accord.

I've got hold of a screen recorder prog and I'm trying to get a short video of this happening without giving too much personal finance info away, screen shots are easy to edit, video not so easy ... for me at least.
Comment 5 Wm 2018-05-03 08:33:30 EDT
Help.

I've made some videos of this happening but they are bigger than the 3600KB limit allowed for upload.  The smallest file size is 15600KB or so for 1m23s of screen action.

I am getting tired of fucking about with video recordings, it is not my skill.
Comment 6 Wm 2018-05-03 08:57:08 EDT
Just for amusement, in case I was going nuts I checked for other files around 3600KB in size, one that showed up was a credit card agreement .pdf.  Am I really expected to make a screen recording of a problem fit into less bytes than a CC wording ?

May I just e-mail them to someone ?

Seriously, 3600KB isn't what it used to be :(
Comment 7 Geert Janssens 2018-05-03 09:37:35 EDT
Can you put it up in some public storage like dropbox or google drive ? That way several developers can download it.

Alternatively you can also send it to me in private. My mailserver accepts larger files. You can find my address by hovering over my name in one of the earlier comments.
Comment 8 Wm 2018-05-03 10:47:20 EDT
I'm not sure I understand this.  Isn't there meant to be a common place for us to  put things relevant to the project ?

Why is my personal space exposure required ?
Comment 9 Geert Janssens 2018-05-09 10:20:32 EDT
Exposure of your personal space is not required. I was trying to offer you options that would lower the barrier for you.

The common place we currently have is this bugzilla instance. However as you experienced it doesn't allow to update big files and none of the gnucash devs has sufficient privileges to change that. It's managed by the gnome admins.

If you want a common place you can try youtube or vimeo or any other online video hosting service.
Comment 10 Sergey 2019-02-13 10:43:53 EST
Ok. I caught it. Here is the way to reproduce this. This bug is related to multi-display Windows systems and handling the display the new window is created at.
1. Get one notebook with Windows 10 and dp/hdmi output.
2. Connect any external monitor via dp/hdmi (did not tested with vga)
3. Make that extarnal monitor to be 1st (on the left)
4. Turn off external monitor but don't plug it out!
5. Open GnuCash at notebook internal display
6. Open any of those dialogs like new account etc.
7. Turn on external monitor - here they are - all our "lost" windows

If you don't turn off that external monitor and move gnucash main window to second display - it will always open new windows at 1st display in system.

IMHO GnuCash should open new windows at the same display it's main window is.
Comment 11 Wm 2019-02-14 08:41:15 EST
Sergey, I'm not sure this is exactly related.

I do usually use a laptop but not an external monitor.

It does make me wonder if an occasional display driver problem I get could be significant; my laptop was mainly designed for business use rather than gaming or watching video and my display driver sometimes crashes or gets stuck and says it has recovered with various messages about

atikmdag.sys

Going back to my report is it possible this is upsetting the windowing / dialogue system? I am about as sure as I can be it isn't anything in my file.

Thinking about Sergey's report, some of what he describes is familiar to my problem, the windowing / dialogue system seems to be paying attention to something else, it certainly doesn't accept input while it loops.
Comment 12 Wm 2019-02-14 09:22:55 EST
P.S. My own way of working around this is to close the book, open it and immediately create or change an account.  Because I am used to this self-imposed work around I don't really notice it, I make a note of the accounts I need to add or change on a piece of paper and just do them next time.
Comment 13 Wm 2019-02-14 09:56:07 EST
P.P.S should the version be updated?  If I leave it as old for too long the bug becomes forgotten and joins that interminable list, if I update it often I am yelling "me, me, me".  What is the right protocol?

Note You need to log in before you can comment on or make changes to this bug.