October 2006 - cells-devel - mailman3.common-lisp.net

[cells-devel] Anyone remember how we fixed keystrokes not getting picked up in Tk text fields?
by Ken Tilton 18 Oct '06

18 Oct '06

Not sure if the problem got served here -- just checked the archives and do not see anything -- but in the past year I went back and forth with someone for a few days before we finally got text fields in the ltktest-ci demo to reliably notice keystrokes. I notice that ltktest-ci does not now reliably capture keystrokes. Possibly because the fix was an adjustment to the *event-loop-delay* (var name?). I actually do not remember the fix either. Can anyone remind me? Thx, kt

2 1

[cells-devel] Interesting changes to Cells
by Ken Tilton 17 Oct '06

17 Oct '06

No, it ain't Cells4. One is a bug fix to ruled-then-input cells: "ensure current" used to be satisfied by a cell being flagged as input. Of course a ruled-then-input will not be valid initially, so the test is now that something is c-validp as well as inputp. The more exciting change (no, i did not run the Cells regression test, but my hairy application seems to work) is one I have seen coming for a while: Supose have something like: (make-kid 'ct-button :enabled (c? (some #'non-empty (kids (fm-other :thing))))) This button is part of a fixed application GUI and it keeps an eye on the kids of :thing. Now thing happens to be a component inside a little workspace, and other user controls allow them to switch the target being worked on in the workspace. A change to the target pretty much rebuilds the entire contents of the little workspace pane, including making a new widget with the name :thing. Well, this used to work without skulduggery because fm-other used to record dependencies everywhere it went in searching for :thing. Maybe that is something I should reinstate (I just realized). Anyway, the fix I came up with today seems Deeply Sensible, so let's see how it pans out: If :thing itself goes away (going back to the above example) at some point c-quiesce will disconnect the kids cell as a dependency of the button enabled cell. The fix is to flag any caller (dependent, such as enabled) as ":uncurrent", a new state between :unevaluated and :valid. I don't like dirty words or variable names, cll notwithstanding. And dirty is vague where uncurrent says what it means and means what it says. What we are saying is that a dependency on cell X of instance Y implies a dependency on the existence of Y. That just seems like a very safe thing to say, so let's see if this works as well as a kazillion kids dependency that would arise from a dependent modelspace search. kt

1 0

[cells-devel] New Unpaid Item Message from tany70 : #294653688662
by eBay＠common-lisp.net 14 Oct '06

14 Oct '06

1 0