[developers] Re: Macintosh version of LKB now publicly available
sweagles at stanford.edu
Thu Jun 16 20:45:59 CEST 2005
I can confirm similar behavior. An additional clue: running "shrink"
or "expand" on a node inside an AVM also takes a surprisingly long time
on big ones, and seems to be correlated to the size of the AVM.
I also noticed that occasionally dragging the scrollbars seem
ignored... I parsed "the dog chased the cat" (under the ERG), opened up
the top level AVM, scrolled all the way to the bottom, and then tried
to scroll all the way to the top and found I was still looking at the
bottom of the AVM (although the scrollbar indicated the top). Nodes
were not clickable in this situation, though. If I shrink the window
and make it bigger while in this strange state, the exposed portions
get updated with the correct data, leaving orphaned data from the
bottom of the AVM still sitting around in the other parts of the
On Jun 16, 2005, at 10:13 AM, Emily M. Bender wrote:
>>> --- Occasionally, clicking on a node in a parse tree and
>>> clicking on "Feature Structure --- Edge NN" can take a long
>>> time to execute, pretty much taking over the whole computer
>>> in the process.
>> If you wiggle the cursor, does it change to a watch image? Or is it a
>> pointer the whole time? It sometimes seems a little slow to me, but
>> perhaps I've got used to it. I'll see if I can make this more
> It stays the pointer (though I have seen the spinning color wheel a
> couple of times), but everything becomes unresponsive. For example,
> I tried requesting "feature structure" for three edges in quick
> It let me do the first two, but then the pop up menu wouldn't come
> for the third. I also couldn't click on a window from another app
> to move to it, or bring another LKB window to the front, or alt-tab
> between apps. The length of time it takes to display an edge seems
> to be correlated with the amount of information in hte edge.
More information about the developers