> > Agreed, the message is a runtime exception of the underlying
> > OS. Did you
> > ever check your free memory on those occasions?
>
> I don't recall if I check at that exact moment.
Maybe you could increase the amount of memory allocated to cygwin -
http://www.cygwin.com/cygwin-ug-net/setup
> > JSUnit relies on exceptions for problem reporting but if
> > everything goes through OK it just returns. I'm not sure why the
> > same technique can't be used by the Selenium test layer so that
> > any failure exceptions are caught and documented as failures in
> > the return information.
>
>
On Wed, May 7, 2008 at 7:39 PM, Bill Adams <[EMAIL PROTECTED]> wrote:
> This seems to fix the issue:
>
> var row = e.getRow();
> var col = e.getColumn();
> tree.startEditing();
> dataModel.setValue(col, row, '');
>
> Setting the model to '' gets rid of the shadow. The previously existing
> value
This seems to fix the issue:
var row = e.getRow();
var col = e.getColumn();
tree.startEditing();
dataModel.setValue(col, row, '');
Setting the model to '' gets rid of the shadow. The previously existing
value is still editable. Let me know of any better techniques.
Thanks,
Bill
-Original
So editing works correctly on my TreeVirtual, using startEditing(),
after using setColumnEditable() on the model.
However, when a cell is editing, its text has a white "shadow". It looks
like the ghost on an old TV.
I'm using 0.7.2. Would upgrading help? Is there another remedy?
Thanks,
Bill
> JSUnit relies on exceptions for problem reporting but if everything goes
> through OK it just returns. I'm not sure why the same technique can't be
> used by the Selenium test layer so that any failure exceptions are caught
> and documented as failures in the return information.
Oh yes, that's
[EMAIL PROTECTED] wrote:
> Hee hee hee. You said you wanted to be by my side to see it. :-)
>
> As I said before, lots of times it happens after some part of cygwin displays
> a message "unable to allocate heap". Other times, it might not have a clear
> reason. Either way, if I *immediately*
> > You might try something like this to force focus where you want
> > it to be:
> >
> > contextmenu.addEventListener("appear", function() {
> > table.setFocus(); }, this);
>
> The trouble with that is that when the menu appears, the up and down
> arrow will work in the table rather than i
Hi!
> > Could it use an alternate source loader (not filesystem, but say python
> > package resources or so)?
>
> Could you describe more clearly what you mean? In general, with the
> sorted include list and all the dependencies resolved you are free to
> implement an alternative source loader (n
Howdy!
> Could current 0.7 generator produce something like list of used classes
> including all dependencies (qx.* in particular)?
There are several options to the generator to produce such (debug)
output. Do a "generator.py --help" for a list of options. In your case,
you could try "--print-inc
Hee hee hee. You said you wanted to be by my side to see it. :-)
As I said before, lots of times it happens after some part of cygwin displays a
message "unable to allocate heap". Other times, it might not have a clear
reason. Either way, if I *immediately* replace the qooxdoo directory with
> Hm, as we already stated this is significantly different from the
> JSUnit protocol for tests, which relies on exceptions. Which means
> you cannot immedately use the TestLoader.js et al. code from the
> Testrunner for the test wrapper layer (although it would make for a
> good starting point).
Hi Andreas,
Thank you very much for the explanation. That --package-id parameter
seems to be what I was looking for. But I got a couple of other
questions:
Could current 0.7 generator produce something like list of used classes
including all dependencies (qx.* in particular)?
Could it use an alt
> SOURCE LOADER:
>
> * Indexing class paths...
> - Indexing:
> ../../qooxdoo-0.7.3/qooxdoo-0.7.3-sdk/frontend/framework/source/class
> - ID mismatch: CONTENT=qx.locale.data.C != PATH=locale.data.C
> make: **
Hello Derrell,
Derrell Lipman wrote:
>
> In the future, you'd make life MUCH easier for me, when submitting
> changes,
> if you'd submit a standard diff.
>
Thank you for your suggestion. I will submit a standard diff next time.
Derrell Lipman wrote:
>
> Thanks for sending the patch. Plea
15 matches
Mail list logo