The difference I see is the reports Generate button remain constant no matter how I resize the Report settings window. I’m not sure what causes yours to not remain constant, causing it not to show.
I don’t know, either. I have posted all my screen parameters from both RM and from Windows 10. And unlike the invisible circles problem, this problem does at least show up in my screen shots.
Are you making the report window full screen? That always works for me to see the Generate Report button. But I don’t like to make the report window full screen because doing so is frequently is followed by the “bling” problem of the report window popping under the main RM window.
I very rarely use RM at full screen. All my testing was done by resizing the window.
The best I can tell, that also insulates you from the Report screen causing the “bling” problem. I agree that running RM’s windows full screen is less than optimal, but I often have to do so in order to see what I need to see.
Re: the out-of-view Generate Report button
Just adding that I forced my laptop built-in display down from 1920x1080 to 1366x768 without losing the button even at impractically small window size. I didn’t restart RM, tho’ or reboot…
Have you ever tried renaming your RootsMagicUser.xml file (equivalent to a Ctrl+shift+U reset)?
Google search AI summarizer mentions a couple of “per program” possible troubleshooting steps in here:
Unless I’m missing something obvious, none of the remedies suggested by Google AI are available on my computer.
This looks like one of them:
How to Change DPI Scaling Settings in Windows 10 or 11 - MajorGeeks
I want to end the discussion of the Generate Report button at this point. None of the suggested fixes seemed to fix the problem, but the problem is fixed. Let’s see if I can explain.
A window on Windows can be maximized, minimized, or “mediumized”.
When a window is maximized, it is full screen and you can’t change the size except to make it minimized or “mediumized”. I could always see the Generate Report button my RM Report screen, and this was always my workaround to be able to see the Generate Report button.
When a window is minimized, it is invisible and you can’t change the size except to bring it forward by making it “mediumized” or maximized.
When a window is “mediumized”, you can change its size within limits. You can’t make it too small or too large, where Windows itself seems to be in control of how much is too small or too large. I can no longer get a screenshot of my problem because it’s fixed, but the “mediumized” version of my Report window in RM had become too large and the “mediumized” window was hanging off the bottom of the screen. Because the Generate Report button was at the bottom of the “mediumized” window, the Generate Report button was hanging off the bottom of the screen.
I should make note of the fact that you can drag a “mediumized” window so that part of it is off the side or the bottom of the screen. But you should always be able to drag it back so it fits on the screen without resizing it. A “mediumized” window should never be too big for the screen. But my “mediumized” Report screen had somehow become too large for the screen. Somehow, in the process of playing with this problem I have managed to get my “mediumized” Report screen small enough again that it will always fit on the screen, and I can’t find a way to force it to be too large again. This was apparently some sort of combination of user error and/or Windows strangeness that now seems to be fixed.
I would repeat that none of the suggested fixes worked nor were they necessary. All that was necessary was to get the “mediumized” version of my Report screen small enough again. Apparently that happened when I was playing around with the problem. I thank everybody for the time they spent investigating the problem.
1 Like
Belated thank you for the clarifications/corrections. I remember now, it was definitely RTF files, I remember studying the spec because of the index problem. And the community for isolating the problem further, it had been a few years since I looked into it in detail, fuzzy memory.