Edited by Teitelman on May 10, 1983 3:07 pm
BBVForUserExec is designed to allow client not to have These are procedures analagous to those in BBVForUserExec. Hopefully someday there will be a reunion.
DIRECTORY
BBAction USING [Action],
BBBreak USING [BreakIndex],
BBContext USING [Context],
BBVForUserExec USING [ReportProc],
IO USING [STREAM],
RTBasic USING [TV],
ViewerClasses USING [Viewer],
WorldVM USING [World]
;
BBVExtras: CEDAR DEFINITIONS =
BEGIN
ReportProc: TYPE = BBVForUserExec.ReportProc;
ShowBreakPoint: PROCEDURE [break: BBBreak.BreakIndex, report: BBVForUserExec.ReportProc];
ClearActionBreakPoint:
PROC [action: BBAction.Action, report: BBVForUserExec.ReportProc]
;
clears breakpoint of action. would be nice, since implementation involves doing things like BBAction.PeekData.
WalkContext:
PROC [action: BBAction.Action, context: BBContext.Context, target: RTBasic.
TV ←
NIL, delta:
INT, report: ReportProc]
RETURNS [lf: RTBasic.
TV];
no such procedure in BBVforUserExec. Would be nice, since implementation requires delving into BBContext, BBFocus, etc.
DisplayLocalFrame:
PROC [out:
IO.
STREAM, lf: RTBasic
.TV, report: BBVForUserExec.ReportProc, args, vars, allVars, globals, lfAndPc:
BOOL ←
FALSE];
main difference with BBVForUserExec is takes globals and lfAndPC argument. This one takes an STREAM and BBVForUserExec takes a PutClosure but that's a minor detail.
SetBreakFromPosition:
PROC[report: BBVForUserExec.ReportProc, viewer: ViewerClasses.Viewer, position:
INT, world: WorldVM.World ←
NIL, entry, exit:
BOOL ←
FALSE]
RETURNS [break: BBBreak.BreakIndex];
BBForUserExec sets a breakpoint at the current selection. This allows program to capture current selection information and then allow SetBreak to take its time without having to worry about the user having to wait.
END. -- BBVExtras