I'm not sure, but maybe the view dialect should just set vars globally, if they're not found locally?
Even if having a ton of global variables isn't viewed as something desirable by many (myself included). I guess, that's why it was changed from R2 to R3?
An alternative could be, that vars set in the dialect could end up in a special context for that purpose, and that this context is searched too, when vars are used in the dialectc.
please don't rebind the blocks manually. if the action uses 'SET its for a purpose. furthermore, using 'SET doesn't mean that the value is set within a "global" space. it means so set that word as it is bound already (which may have been bound manually by the user).
if he uses a set-word, then that could be localized, as per current funct and object creation rules.
I don't like the double colon syntax at first glance.
Has there been any progress on determining this TCP/IP bug #9910 ?
I don't think so or at least I don't know about anyone who picket that up so far. But its a critical one so I believe it will be fixed very soon.
I have a couple questions about how to deal with actors and I think an example will illustrate it best.
Trying to modify use click actions on a text-table to affect filtering on another text-table:
My goal is when i click on tt1 that the ID number on that row will set the filtering on tt2 to show only events with that ID #
Question 1: on-focus only deals with the first click on that whole face, so it's the wrong actor. Do i need to modify the actor of an individual row? or am I just using the wrong actor? If I change on-focus to on-click it results in no print statements.
Question 2: I'm unsure how to set the filter for tt2. If I try (stole this code from probing the facet):