uh oh--omnipresent ref set rears its ugly head (again)

1 view
Skip to first unread message

7qax...@earthlink.net

unread,
Jul 30, 2007, 1:06:33 PM7/30/07
to gr...@googlegroups.com
The omnipresent reference sets have appeared again, and I am positive they did not occur because I continued onto the next page during saving. I hit the tab for the next page at the top of the screen after saving had completed for that page. The reference sets are from v1319_s1_p052.jpg, and automatically continue onto the following pages. Should I submit another report?

Jessica

-----Original Message-----
>From: 7qax...@earthlink.net
>Sent: Jul 30, 2007 9:40 AM
>To: gr...@googlegroups.com
>Subject: Re: GReF 1.0.2 Release
>
>
>The new version is excellent (in a Bill and Ted's sort of way)!
>
>Jessica
>-----Original Message-----
>>From: "Aaron D. Steele" <ast...@berkeley.edu>
>>Sent: Jul 28, 2007 2:17 PM
>>To: gr...@googlegroups.com
>>Subject: Re: GReF 1.0.2 Release
>>
>>
>>i just upgraded your account on the gref discussion group to 'manager'.
>>
>>On 7/28/07, Denis Treskunov <denis.t...@gmail.com> wrote:
>>>
>>> After more than a month of no development activity, I spent a day
>>> fixing various outstanding issues with GReF 1.0. I am pleased to
>>> announce that most bugs reported on the Google Code site have been
>>> fixed. Most notable improvements are:
>>>
>>> 1. Saving should take about half a second now (depends on the latency
>>> of your connection). Before this change, it was taking upwards of 20
>>> seconds. It used to be that GReF checked for any stray database
>>> records on each save. Due to complex SQL queries involved, this took
>>> about 20 seconds. What happens now is GReF does this check once every
>>> hour, independent of any user interaction.
>>>
>>> 2. "Collecting event" references now have additional information
>>> available for viewing: "Higher geography," "Specific locality,"
>>> "Latitude/longitude," "Datum," and "Georeferenced by." I was going to
>>> add Google Maps support, but this is going to be less trivial than I
>>> thought: most georeferences have coordinates in NAD27, while GMaps
>>> expects coordinates to be in a format slightly different from WGS84.
>>>
>>> 3. The dialog for editing georeferences now has an "edit" link.
>>> Clicking it would take you to the correct sub-editor for the
>>> georeference type you're editing and would fill in the search
>>> information.
>>>
>>> Those are the user-visible improvements. Behind the scenes, GReF now
>>> has better and more numerous log messages, so I can keep an eye on
>>> potential problems.
>>>
>>> I hope using GReF is a pleasant experience for you.
>>>
>>>
>>> >
>>>
>>
>>>
>
>
>>

Aaron D. Steele

unread,
Jul 30, 2007, 1:08:57 PM7/30/07
to gr...@googlegroups.com
hi jessica,

yes, please submit a new issue and include *as many* details as
possible about how to reproduce the omnipresent refset.

Reply all
Reply to author
Forward
0 new messages