Hi Aaron, Yes thank you. That’s great. Best regards Dave Sent from my iPhone
> On 2 Jul 2021, at 18:23, Aaron Sloman <[email protected]> wrote: > > Hi Dave, > >> While working through the teach file "vision4" and playing >> with Hough transforms I have noticed that the call "rc_context" is not >> defined i.e. "undef". >> >> A typical call to save the window context and coord. System should be >> "rc_context(false) -> xy_context" say, according to the teach file. >> >> Does anyone know of this? Has the function been replicated? And if so, >> replaced by what? > > This is part of a complicated story about how Poplog allows many facilities to > be set up in ways that suit the needs of different individuals. > > With my set up I was able to check out this point by running poplog setting up > popvision, going to teach vision4 (which includes "uses rc_context") and when > I > got to > > vars xy_context; ;;; save the present window > rc_context(false) -> xy_context; ;;; and its coord system > false -> rc_window; > rc_new_window(300, 300, 550, 400, true); > [0 100 0 360] -> rcg_usr_reg; ;;; bounds of parameter space > rc_graphplot([], 'r', [], 'theta') -> ; ;;; draw axes > > Everything worked (using poplog in fedora: kernel 5.11.22-100.fc32.x86_6). > > There's more to be said about the layers of functionality provided by > different > options in different phases of poplog startup (e.g. some concerned with > editing > preferences, and options to load user preferences of various kinds at various > stages). > > But I have to finish off another unrelated task before getting back to poplog. > > I hope that helps. > > Aaron > http://www.cs.bham.ac.uk/~axs > > PS > > One of the related issues is the fact that Brian Logan's libemacs provides a > sophisticated mechanism for ved-hating emacs-lovers to do their editing in > emacs > and making emacs tell the poplog process what has been changed and what the > user > wants to do next, and then read the results back into Emacs. > > I don't know if anyone on this list, apart from Brian, has used that facility, > but I am sure that in principle it should be included as an optional extra in > any future re-location of poplog. > > I have no idea whether such "team-work" would be possible if poplog were > ported > to windows 10 (to get far more users than a linux version could hope for). > > Or perhaps windows users will have to be satisfied with running poplog in the > new linux extension to windows (about which I know nothing except that it > exists). > > === >
