I'm using version 2.5.61 and have noticed two very strange occurrence.
I usually run the the "Show Only New Messages" option turned on. That way I can read only the new messages that have been posted. I also have the "Mark messages as read after x sec" set to 1.
What is strange is that as I read the messages, if I use the arrow keys to move through the messages the messages don't get marked as read no matter how long I view the message, but if I use the mouse and click on the message is changes to read after a short period.
The problem that really annoys me is that when I use the mouse select the messages, not only is that message marked as read, but the last message in the list ( i.e. last received) is marked as read as well.
Anyone else seen these issues?
==
Michael Crowder
Another update....
The the problem of
Quotewhen I use the mouse to select the messages, not only is that message marked as read, but the last message in the list ( i.e. last received) is marked as read as well.
If the new messages span more then one screen worth, the one that gets marked is the last one displayed, not necessarily the last one in the list.
--
Michael Crowder
Try 2.5.063 ?
http://www.personalgroupware.com/groupmanager/PGOffline-2-5-063.exe
Cheers,
Wilson.
Wilson,
Just tried the new version....same problem
(http://i.pbase.com/o2/31/493831/1/98180661.5Nq65SsY.Clipboard02.jpg)
Notice that I'm on message # 22607 but it and message #22610 are marked as read.
Really weird.
--
Michael
Hi Michael,
Can you repost your screenshot. It didn't seem to work (I can't see it at any rate).
Cheers,
Wilson.
http://www.pbase.com/sonex293/image/98180661/original (http://www.pbase.com/sonex293/image/98180661/original)
Try going to the above link...
--
Michael
Any luck reproducing this problem? Still happens all the time. :(
--
Michael
Hi Michael,
Yes, I have been able to re-create this. I'll pass it on to the developer. Sorry for the delay.
Cheers,
Wilson.
No problem on the delay. Just wanted to make sure I wasn't the only one seeing it ;D .
Thanks for looking into it!
--
Michael
This is fixed in version 3.
http://www.personalgroupware.com/groupmanager/PGOffline-3-0-045.exe
Cheers,
Wilson.
Quote from: Wilson Logan on September 24, 2008, 09:19:30 PM
This is fixed in version 3.
But unfortunately as it seems only if you have the view with only new messages active. In the view with all messages, the same problem still occurs on my machine here.
Edit: And I just noticed that it re-starts doing this even in the new messages view if you changed anything in the msg-list-view (sort-order, window-size etc.). I have to quit and re-load the program to stop the problem again.
bye
Wolfgang
OK, it *was* fixed.
Maybe the fix has been left out of the latest build.
I will check it out & send my findings to Matti (the developer).
Cheers,
Wilson.
Hi Wolfgang,
I've just checked my copy and its working fine. What version do you have? I have 3.0.45 on Vista.
Cheers,
Wilson.
Quote from: Wilson Logan on September 27, 2008, 11:32:43 PMI've just checked my copy and its working fine. What version do you have? I have 3.0.45 on Vista.
I am using 3.0.45 on XP SP3.
I can reproduce the problem on my big machine as well as on my notebook.
bye
Wolfgang
I don't want to be pedantic or anything but can you check the "About" menu option to verify the version number?
When we went from 2-5-xxx to 3-0-xxx we changed the install location. It's possible your shortcut still points to the old version.
That notwithstanding, I will check this on an XP system ASAP.
Cheers,
Wilson.
Yes I did check the "About"-Box for the version number. Several times... Always says 3.0.45. On both machines.
I can reproduce it like this:
open PG Offline (3.0.45 :),
displaying only unread msgs,
mark msgs as read after 1 sec,
choose group to read,
choose first msg,
resize the msg list window,
press cursor down to next msg and voila,
the last msg in the list window looses it's "New!" tag together with the msg that just got selected.
bye
Wolfgang
Hi Wolfgang,
I see it too.
I'll ask Matti to look at it right now.
Actually we're making a couple of small improvements so we may wait to roll out the fix for this with the coming update.
Cheers,
Wilson.