Re: Spindle 1.1.3 available

Dave,

>
> I just upgraded using Eclipse update. The SWT bug regarding tool tips
> remains, and is worse, in fact (the bug forced Eclipse to exit, which it
> hasn't done previously under 1.1.1 or 1.1.2). I also upgraded on my
Windows
> 2000 box and that seems to work fine (always did before, too, just wanted
to
> tell you that certainly nothing broke there).

Argh, I use windows (where they work of course) and so I couldn't test the
change.

>
> One the subject of the bug, did I do something wrong when I filed it? It's
> in the database on SourceForge (648231), but it's marked as being in the
> "Pending" state, and assigned to "Nobody/Anonymous." Was it me who set the
> state wrong? Can I even do that? Anyway, it's there. Do you want me to
> reopen it?

I normally set the bug state to pending when I make the fix, then close the
bug once the release is out.
This time I forgot to check the pendings before I wrote the release notes. I
will re-open the bug.

** You did nothing wrong! ** :-)

>
> Also, is there any more info that you want me to collect from Linux? There
> are two things that I can think to try in addition to any debugging info
you
> want me to try to collect on the RH8/GTK Eclipse setup I have running.
>

I'm free today, so I will add more logging information to the TooltipManager
and send you
a tweaked version fo the plugin. That way the log will produce messages
specific to the problem.

> 1. I can try to run the Motif version of Eclipse on RH8.0. I tried that a
> while ago and was having some trouble with that. I switched to the GTK
> version since it looked better anyway (nicer widgets, etc.).

Give it a shot on Motif.

> 2. We could try to get more feedback from people using Spindle on Linux,
> like under RH 7.3 or something, to see if it's a RH8.0-specific issue.
Given
> that I have my system all set up with RH8.0, I'm not eager to downgrade
just
> to debug this issue. It's simply too painful.

I'm open to any feedback!

>
> I'm also noticing some strange behavior with 1.1.3 in editing component
> bindings. Llike I edit things and they don't seem to "take," even though I
> save the page file, or even one just now where I kept editing the
> "Expression" of the binding, and after I saved and opened up the page
again,
> it had set the binding "Name" to what I had input for the "Expression,"
and
> the "Expression" was "fill in value." Thoughts here? I'll open a bug if
you
> want. I can reproduce it fairly easily, but it doesn't seem regular. That
> is, sometimes it happens, sometimes not. I can't tell what behavior I use
> that causes it to happen and what not.
>

I'll look at while I'm tweaking...

Its almost 7am here now. I should have something you can test in a couple of
hours.
Sorry for the incovenience.

Geoff



-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/