* Jamin W. Collins ([EMAIL PROTECTED]) wrote:
> Not to be picky, but it would appear that you are testing the 0.61.1
> source.  There have been many changes made to Blackbox recently.  Can
> you try reproducing this with the latest 0.62pre release (believe it's
> 0.62pre4).

Yes. Because 0.61.1 is what I use. pre4 has bugs that affect the usage
of other applications. Also, I am pretty certain that the relevant
parts are untouched. I could be more sure if the cvs was more up to
date. It is pretty trivial to check if this bug exists in later
versions if you happen to be running it, as shaleh as already done,
however, I think it is rather unreasonable to expect everyone to use
an unstable prerelease, especially when they are not developers.
 
> Is there any reason to have a workspace this long?  I wonder if maybe we
> should have a more reasonable length limit on the workspace names.

Well, I can imagine one scenario. You have a fairly long workspace
name, but not long enough to obliterate the toolbar, you switch to a
lower resolution and suddenly your toolbar is messed up. Also, the
problem would be magnified if you simply shorten the length without
checking the bounds. The workspace name is an unchecked buffer, and
everyone should be aware, buffer overflows are bad.

> 
> > Also, one can edit the workspace, switch to another
> > workspace, and begin typing. This will produce unexpected
> > results. 
> 
> A check during workspace change should correct this, right Shaleh? 
> Basically just check to see if the workspace was being edited, if so
> ditch the editing and switch workspaces?
> 
> > There are also some minor bugs to do with typing odd
> > characters while inputting the workspace name. eg: control c.
> 
> Not sure on this one.
> 
> Jamin W. Collins

-- 
Scott Moynes

Attachment: msg04952/pgp00000.pgp
Description: PGP signature

Reply via email to