Cinnamon Hummingbird

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.
Setup your Forum photo and profile here.

In the View/Edit wi...
 
Notifications
Clear all

[Solved] In the View/Edit window checking the box after comment gives inconsistent results

4 Posts
2 Users
1 Likes
48 Views
Posts: 21
Topic starter
(@judyhs)
Eminent Member
Joined: 2 years ago

Jeff,

I just entered sightings for mammals seen on a recent trip using the Mammals 2018 taxonomy.  Entry worked as expected including generating the confirmation list.  I then tried to View/Edit (specifying either the trip or the date range) and got an empty grid.

I eventually realized that I had checked the box after the comment field but had not entered any text.  This combination prevented any of the newest sightings (2021 and 2022) from being displayed.  (Some of the new sightings had comments, but others didn't.)

Details: With no Name, Dates, Trip, etc., selected except the Comment box checked, View/Edit generated a list of sightings (those without comments) from 1993 to 20 Jan 2020 even though I should have also seen sightings from Jun 2021 and more recent.  If I uncheck the box, I see all my sightings, with and without comments, including the recent ones.  I see the same incorrect behavior with the Whales taxonomy. However, if I select Clements 2022 with the comment box checked, I do see all sightings (without comments) including those from 2021 and 2022.

image

I don't use any other taxonomies.

I'm using 6.0 Build 20.

Judy

 

 

Reply
3 Replies
Jeff
Posts: 687
 Jeff
Admin
(@jeff)
Creator & Technical Support
Joined: 3 years ago

Hi Judy,

Thanks for posting. This brings up an interesting situation that was caused by the addition of saving Rich Text Formatted comments. When this was implemented (v4.0? or so) empty comments are never empty. There is always blank RTF formatting code present in each comment field. Not visible to the eye, but it affects queries such as these.

You can convert all existing Sightings Comments to plain text and then always use plain text when entering sightings going forward. This will get around this problem.

image

But if you do this, you will lose all advanced formatting in all Sightings Comments; such as bolding, bulleted lines, font size and type, etc.

If you don't have a specific need to do this, you are probably just better off knowing about this caveat and working around it.

Let me know if you have any questions.

Reply
Posts: 21
Topic starter
(@judyhs)
Eminent Member
Joined: 2 years ago

Jeff,

Checking the comments box and not entering any text was not intentional.  Now that I know why I saw no sightings, not a problem.

I'm not at all concerned about about losing advanced formatting so I will switch all comments to plain text. I import most of my bird sightings from eBird but enter the mammals manually.

I was puzzled for a while by having 3 different fonts/sizes for comments in a trip report.  I had selected a unique looking font on the report setup page for comments.  I saw that font displayed for what I now know were plain text entries; a large Arial font which was the default font/size for sightings entered this week from the Add page; and an Arial 10 font which was on older trip reports.  Apparently in past years the default for RTF was Arial 10.

Thanks,

Judy

Reply
Jeff
Posts: 687
 Jeff
Admin
(@jeff)
Creator & Technical Support
Joined: 3 years ago

Thanks for the update Judy. You are correct on everything.

Reply
Share: