Welcome to the Birder's Diary Forum for Support And General Questions
Use the Support forum for all questions or issues.
Use the Wish List forum to leave your ideas for improving Birder’s Diary.
Hi Jeff. After downloading the update yesterday I have found that the text in the comments section of the sightings entry screen is huge! I though maybe that was intentional, and the reports would show it as normal size. However, my entries today stand out in the report as large compared with the older entries! I am referring to comments I have entered. All other fields such as name, location, etc are okay. Wayne
Hi Wayne,
Ok, I assume you are at v5.2 Build 30 then. But just to be sure, please confirm.
Comments Font Size are set in View | Options. This was not correctly being applied to new Comments prior to build 30.
So, first thing, is to set that Font and Size to what you want for future comments.
Now - to correct currently BIG comments in recent sightings, you will need to edit each sighting.
Enter the Comments Editor and the font size will be changed to that currently selected in View | Options.
Ctrl+S from the Comments Editor to save your changes and then Save your edits.
Sorry about this. I bet others are going to have this same problem
Let me know if I missed anything.
Jeff
Hi Jeff. Yes, Build 30. I will let you know of my progress with this. All I want is for the present font and size to match what is already there!
Wayne
I have followed your instructions and sorted this. Thanks Jeff. Somehow the update changed the default comment font size to Arial 14. I changed it back to my original setting of Arial 8 and then sorted the two entries made today. So, all good once again. Regards. Wayne
Jeff,
I updated to Build 30 and checked my View/Option setting. It is set at Comment Font Arial 14 and Grid Font Arial 10. It has been that for centuries.
I have not added or edited any sightings after update. As a test, I opened an old sighting and clicked to edit it. The comments field font is humongous.
I went to the View/Options/General window and saved my settings (Arial 14 and 10) to refresh the choices. Editing a sighting still gives me the humongous comments font.
I went to Reports and the test case has humongous font. Editing the comments did not fix the font after updating my font choices
. Unfortunately I overwrote build 30 over 29 so there is no going back.
See attachments
Regards, Al Borodayko
Cypress, CA
Hi Al,
Thanks for posting.
You say humongous, but is that not just Arial 14?
As a test, create a test Sighting and add a comment. No bolding or anything, just the text "Test". And see how it compares.
The new change should not affect any existing comments. They will stay as they always have - or they should unless I did something wrong; but I've never made a mistake! Winky eye emoticon!
I just tested all sorts of things around this, and old comments retain the font/size they were entered as. Try as I may, I don't get any unexpected results.
Do some testing please and let me know what you find. Change your settings in View|Options and see what you get. Record the exact steps you use to get unexpected results and let me know.
Also, please note, that Comments in the Sightings View Grid are stripped of any formatting and always display the selected Grid Font/Size, so don't expect the comments there to use the Comments size.
Let me know please.
If you like, you can zip and upload your database per the File Upload page on this site, and I can interrogate your database to see exactly what font is set for the Sightings comments in question.
Thanks,
Jeff
Jeff,
I attempted to make the changes and was not successful so I'm sending my database. The one I played with was one of my American Dipper sightings.
Al
Ok Al.
There are two options for your Sightings Comments...
- Rich-Text Formatting (RTF), or
- Plain Text (no bold, italics, font, etc)
These AMDI comments are originally all Plain Text comments. No RTF formatting. Meaning, they were entered before I added the default RTF commenting feature back in v4.0 or so (based on the date, this is probably the case), or you selected the Plain Text option on Sightings Entry.
A few more things.
- If you are editing a plain text comment sighting, then the comment will show up in your default comments font in the editor.
- The font you are seeing in the sightings editor is Arial 14
- The fact that this one sighting shows up as Arial 14 in your report means that you edited and updated this sighting's comment, which unless you check plain text option on the editor, gets converted to RTF. The database you sent me did NOT have this sighting's comment converted to RTF; so this had me confused for a bit.
- You can easily edit this sighting and convert the comment back to plain text
If you set plain text on keyboard entry or the editor, then it will remember your setting from here on out until you change it again.
Let me know if this is not what you find when you test this. Or if this generates more questions.
Thanks,
Jeff
Jeff,
Plain text was unchecked. I did not uncheck it. I checked it now and it works. The Arial 14 I assumed was there before build 30 because I did not change it. I reduced the comment font to Arial 9 and it looks like the size I used before. I also had to uncheck BOLD which somehow got changed. Anyhow, the silent changes threw me for a loop.
I have things back to normal so all is good.
Thanks, Al
Hello Jeff,
Just by accident, I did a test on one of my sightings to verify that the settings are remembered. Accidentally, I picked one that had the text misaligned in the Report window. After the edit, I noticed the alignment was corrected.
This exercise produced a fix for an old nuisance problem that occurred with text alignment in the reports. If you recall, I had text that was not always aligned even though all the words were the same (See Before). So I tried again with the American Pika. I edited the first and last of the series and they aligned with the others (See After). In the Edit Sightings window all I did was (1) check the comments box and (2) clicked "Update" without changing any of the text in the comments.
Unfortunately each one has to be edited individually, but on a cold and rainy day when I have nothing to do, I will clean up those that don't align.
Put that in your pipe and smoke it, Al
Latest Post: Run-time error 9 subscript out of range Our newest member: gamedevsu Recent Posts Unread Posts
