After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 409775 - runInterval chronopic strange behaviour on start
runInterval chronopic strange behaviour on start
Status: RESOLVED FIXED
Product: chronojump
Classification: Other
Component: chronojump
05
Other Linux
: Normal minor
: ---
Assigned To: Xavier de Blas
Xavier de Blas
: 407772 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-02-19 21:47 UTC by Xavier de Blas
Modified: 2007-03-09 19:41 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Xavier de Blas 2007-02-19 21:47:59 UTC
on src/execute/event.cs
method: protected Chronopic.Plataforma chronopicInitialValue(Chronopic cp)

do {
    Console.WriteLine("B");
    try {
         ok = cp.Read_platform(out myPlatformState);
    } catch {
         Console.WriteLine("Manage called after finishing constructor, do later");
    }
    Console.WriteLine("C");
    (...)
}

Goes to the catch infinite times. It's stopped at third time, and then it's understood like if the user is always outside, but this is not true.
Comment 1 Xavier de Blas 2007-03-09 19:38:58 UTC
*** Bug 407772 has been marked as a duplicate of this bug. ***
Comment 2 Xavier de Blas 2007-03-09 19:40:50 UTC
Fixed here:
http://svn.gnome.org/viewcvs/chronojump/trunk/src/execute/run.cs?r1=214&r2=216

Seems there sohuld be difference in chronopic being private (event/jump.cs) or protected (event/run.cs), depending on inherition of the "Manage" and the "cp". Probably it's a mono bug.

Now it works!