Delicious Bookmark on Delicious

Ticket #169 (closed defect: fixed)

Opened 4 years ago

Last modified 4 years ago

Client refresh doesn't work anymore with deactivated client(s)

Reported by: Gerby19 Assigned to: uncle_fungus
Priority: major Milestone: 2.4.0
Component: Monitoring system Keywords:
Cc:

Description

Hi Andrew!

Although I know it's an preliminary implementation of the feature (came with r334), I report the following issue here:

Disabling entries in the client list prevents the whole client list from refreshing its status (neither automatically nor by pressing F5). This occurs, when at least one client has been disabled, even if all clients are enabled again afterwards. A program restart is needed.

Greetings Mark

Change History

10/02/08 07:35:56 changed by Gerby19

(Sorry, forgot to select the right "Component" for this ticket.)

10/02/08 08:13:19 changed by uncle_fungus

  • component changed from Documentation to Monitoring system.
  • milestone changed from 2.4.0 to 2.3.3.

Hmm, that sounds odd. I take it you're compiling on Windows? I haven't tried the latest svn revision in Windows, but it definitely works in Linux.

10/02/08 09:33:25 changed by Gerby19

Right. Compiled under Win XP Pro with - Visual C++ 2008 Express SP1 - WxWidgets? 2.8.9 - Windows SDK v6.1 for Win Server 2008 and .Net 3.5

10/02/08 10:01:12 changed by uncle_fungus

I'll take a look at this later.

10/03/08 04:55:33 changed by Gerby19

Well, on another computer it works just fine. Both run with the same OS (Win XP Pro SP3) and the same FahMon? binary. Unfortunately I cannot check the computer with the problem again until next Wednesday.

10/12/08 16:26:42 changed by uncle_fungus

  • milestone changed from 2.3.3 to 2.4.0.

I can't replicate this, so I'll push this back to 2.4.0.

10/13/08 14:01:02 changed by Gerby19

Sorry for the late follow-up: I couldn't reproduce this error either, at least not with the current build (here: r339).

Just one interesting observation: If several clients are disabled in the list and you press F5, their order changes. I had the idea that there could be a relation to the error I observed earlier as described above (provoking the error by pressing F5 several times), but as already said it doesn't appear anymore.

10/14/08 08:20:14 changed by uncle_fungus

The sorting algorithm for a number of columns in the client list isn't yet optimal and causes strange effects when clients are disabled etc. It is largely dependent on what column is used for sorting, but I'll be fixing it soon enough. (I'm just cleaning up things for the next release now).

11/02/08 14:02:14 changed by Gerby19

It seems that the described issue is related to a discussion started by osgorth in the Folding Forum (after releasing FahMon? 2.3.3):

http://foldingforum.org/viewtopic.php?f=14&t=40&st=0&sk=t&sd=a&start=405#p65817

11/03/08 05:45:53 changed by uncle_fungus

Indeed. I think the system to prevent unnecessary refreshes is being too aggressive and is preventing legitimate refreshes.

11/04/08 10:56:46 changed by uncle_fungus

  • status changed from new to closed.
  • resolution set to fixed.

I've determined that this is actually the same bug as in #178, thus it was fixed in r361.