Having had the small disaster of my date field becoming too wide to see anything (including said date field), I have had to create a new database and copy my data over from the broken one.
Having done that, and having figured out where some of my custom fields had gone, I find that I have no custom REPORTS from my previous database file; I had thought they all were available between different databases, but was disappointed.
While I try to find out whether I have to start over there as well, I re-created one new custom report, and found a new bug: I can’t see the name of the report as I am saving it. RMG throws up a big window to TELL me to name it, but blocks out the window where I type the name. Once I typed the name blindly, I found I had a typo. When I went to rename it and correct the typo, the same big window appeared and blocked me from seeing what I was typing.
This is frequently a forum for user requests for new features. I want to offer the idea that RMG should stop giving us new features for a while, and concentrate on fixing the bugs that are still troubling us in the last three version upgrades. IOW, I really am uninterested in seeing a Version 11 UNTIL we have all the bugs from Versions 8, 9, and 10 corrected, and then do some more extensive testing before that hypothetical V.11 is ready for release.
Here I completely agree. Although RM advertises being user-friendly, there is still a lot to do. Bring the options forward for us to see, not hidden behind. Get the Description field [Desc] in place on all Facts. Use of the description field is an excellent tool for providing additional information.
Just go the the Fact and check the box to display Description.
It’s a 1 time nuisance thing to do but not the end of the world - there’s not alot of them.
Actually, comparing it to your screenshot, I can do so, but ONLY if I maximize the box. I did not have to do this before, and frankly I am getting tired of having to find workarounds for things that worked in previous versions.
Did you not see my post and my DM to you that has the fix for your Date column using a SQLite query? I wondered why you had not responded. Offer still stands.
Yes, I have the description fields at my facts for several years now, but I see from the Norwegian User group which I manage
that it is not entirely easy to get this in place. Why can’t RM do that for all Facts, then it’s up to the individual to use them. I have understood that the developers have avoided it. I would like to see the reasoning there.
I am very keen that a Narrative report should be very telling, not just a summary of Facts. In that case it is very convenient to use the Description field.
The narrative reports in RM are not general narratives, nor are they meant to be. They are based on standard by a couple of American genealogy groups, NEHGS and another who’s acronym I can not recall.
Users make assumptions that just because they are ‘narrative’ they should function in the way you describe. If users want their own type of narrative, this is going to involve some type of generic reports in which users can add or subtract the bits and pieces that they want. I picture coding the report generator for this to be quite a nightmare.
The lack of the description field in some of the event/facts is probably due to the GEDCOM 5.5.1 standard which does not support them in those events/facts. I haven’t checked the GEDCOM 7.0 yet to see if they are supported in all event/facts but RM 10 does not yet support that standard and I don’t expect it until release 11.
As @kbens0n suspects, it is a scaling issue. On my laptop with Windows scaling at the recommended 125%, boosting the RM Font Scaling to 150% perfectly replicates what you see. You can maximise (as you have discovered) or drag the edges of the window to expand it to reveal the edit field. Backing the RM Font Scaling down to 125% also reveals the field in the default window size.
Even at 150%, the type is not large on my laptop. I don’t know if it’s the laptop (an LG, of which I have never been particularly fond) or the software. Setting it even smaller, I STILL get this issue:
Did you reset RM using SETTINGS under the monitor and then restart RM?
I changed my settings in RM to 150 and get what you have above–when I go to 100, I get
Follow @kbens0n’s line of inquiry. I replicated your problem by reducing the resolution on my laptop from the recommended 1920x1080 to 1280x960 with the RM FontScaling set to 150. When you change either one, close and reopen RM to make sure it takes effect.
