Thanks Bill, I changed my User Key Definition to mode 1
F6|1|Jig Augmented Display|((1 ; coname '') visual_jig_ 0) and everything works again. I also changed the modes to 1 on the lint and dissect user keys that I had defined and now they work as well. They did not work in mode 0. Is there an option to leave them working in user mode 0 in the future or will we have to instruct users to adjust the configuration of their user keys? Cheers, bob > On Dec 16, 2020, at 08:42, Henry Rich <[email protected]> wrote: > > According to > https://code.jsoftware.com/wiki/Guides/Qt_IDE/Configure/User_Keys those > fields should be set for modes 0 and 1. I know they used to work for me and > I never used mode 1. > > Henry Rich > > On 12/16/2020 11:39 AM, bill lam wrote: >> Ah I remember, those 2 names are available under mode 1, ie, put 1 instead >> of 0 in the configuration for the PFKey. >> Can you try and confirm it can work first? >> >> On Thu, Dec 17, 2020, 12:27 AM 'robert therriault' via Programming < >> [email protected]> wrote: >> >>> Hi Bill, >>> >>> I don't use debug a lot, but my understanding is that if I was in >>> suspension mode then there would be an additional 3 space indent for each >>> new line. If this is true then I was not in suspension mode when I pressed >>> the keys. >>> >>> This is the result that I get when I press the F6 key which is my User >>> Defined Key for the Jig Augmented display >>> >>> |noun result was required: findline_jig_ >>> | (#~-.@:(*./\)@:=&' >>> ')":({.WinSelect_jqtide_)((LF&taketo&.|.)@:{.,LF&taketo@:}.)7 >>> u:WinText_jqtide_ >>> |[-0] >>> >>> When I check the names defined in the jqtide locale using names_jqtide_ '' >>> I don't see either WinSelect or WinText, so my guess is that the >>> interpreter is seeing them as undefined verbs and that is the reason for >>> the lack of a noun result. >>> >>> Thanks for your help in this and let me know if there is anything further >>> that you need me to do. >>> >>> Cheers, bob >>> >>>> On Dec 16, 2020, at 08:10, bill lam <[email protected]> wrote: >>>> >>>> Bob, >>>> >>>> I checked those 2 names should had been set in non suspension mode. >>>> Was your PFkey pressed during suspension mode? >>>> >>>> On Wed, Dec 16, 2020, 12:13 PM 'robert therriault' via Programming < >>>> [email protected]> wrote: >>>> >>>>> Just a follow-up Bill, >>>>> >>>>> Comparing the results of names_jqtide_ '' for the two versions j901 and >>>>> j902, the only differences that I see are WinSelect_jqtide_ and >>>>> WinText_jqtide_ not being in j902 >>>>> >>>>> Cheers, bob >>>>> >>>>>> On Dec 15, 2020, at 18:20, 'robert therriault' via Programming < >>>>> [email protected]> wrote: >>>>>> Hi Bill, >>>>>> >>>>>> WinSelect_jqtide_ and WinText_jqtide_ are the only two names that I >>> have >>>>> used for jig's User Defined Keys. >>>>>> Henry probably has a better sense of whether dissect requires any >>> others >>>>> for its User Defined Keys to activate the application on the line which >>>>> holds the cursor. >>>>>> Cheers, bob >>>>>> >>>>>>> On Dec 14, 2020, at 14:57, bill lam <[email protected]> wrote: >>>>>>> >>>>>>> Are globals WinText_jqtide_ and WinSelect_jqtide_ the only names that >>>>> will >>>>>>> be referenced by addons or other users scripts? >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Tue, Dec 15, 2020, 12:14 AM Henry Rich <[email protected]> >>> wrote: >>>>>>>> The fields used by pfkeys are described in >>>>>>>> >>>>>>>> https://code.jsoftware.com/wiki/Guides/Qt_IDE/Configure/User_Keys >>>>>>>> >>>>>>>> Henry Rich >>>>>>>> >>>>>>>> On 12/14/2020 10:56 AM, 'robert therriault' via Programming wrote: >>>>>>>>> Thanks Bill, >>>>>>>>> >>>>>>>>> This is the verb that I modified from Henry's invocation of dissect. >>>>>>>>> >>>>>>>>> findline =: 3 : 0 NB. WinSelect is a character index; WinText is >>>>>>>> entire window; if window contains non-ASCII, convert to unicode >>>>>>>>> if. y do. ; }. ;:(#~ -.@:(*./\)@:=&' ') ": > {: < ;. _2 (wd'sm get >>>>>>>> inputlog'), LF NB. pull the last line only for the monadic case >>>>>>>> Programmatic version strip off first word which would be invoking >>> verb >>>>>>>>> else. (#~ -.@:(*./\)@:=&' ') ": ({. WinSelect_jqtide_) >>>>>>>> ((LF&taketo&.|.)@:{. , LF&taketo @:}.) 7 u: WinText_jqtide_ end.NB. >>>>> The >>>>>>>> line that the cursor is on if 0 - Function key version >>>>>>>>> ) >>>>>>>>> >>>>>>>>> I believe that WinSelect_jqtide_ is the other name that is used that >>>>> may >>>>>>>> be affected. >>>>>>>>> Cheers, bob >>>>>>>>> >>>>>>>>>> On Dec 13, 2020, at 23:50, bill lam <[email protected]> wrote: >>>>>>>>>> >>>>>>>>>> understood. There are some undocumented names or that I failed to >>>>> notice >>>>>>>>>> inside the source of qtide frontend. Those names are not refernced >>>>>>>> insude >>>>>>>>>> the frontend itself so I didn't handle them. Are there any other >>>>>>>> special >>>>>>>>>> names that you are using? >>>>>>>>>> >>>>>>>>>> On Mon, Dec 14, 2020, 3:36 PM 'robert therriault' via Programming < >>>>>>>>>> [email protected]> wrote: >>>>>>>>>> >>>>>>>>>>> Thanks Bill, >>>>>>>>>>> >>>>>>>>>>> In jig, coname '' returns the locale that you are in when when you >>>>>>>> invoked >>>>>>>>>>> jig. >>>>>>>>>>> >>>>>>>>>>> I have tested it in both the jig 901 and jig 902 versions and the >>>>>>>> result >>>>>>>>>>> of coname '' confirms this. >>>>>>>>>>> >>>>>>>>>>> I have also noticed that WinText_qtide_ is no longer defined >>>>>>>>>>> >>>>>>>>>>> WinText_jqtide_ >>>>>>>>>>> |value error: WinText_jqtide_ >>>>>>>>>>> >>>>>>>>>>> Since I use that to select the information from the line that the >>>>>>>> cursor >>>>>>>>>>> is on, it is quite possible that this is the source of the >>> problem. >>>>> Is >>>>>>>>>>> there a reason that WinText_jqtide_ would not be defined? >>>>>>>>>>> >>>>>>>>>>> JVERSION >>>>>>>>>>> Engine: j902/j64avx2/darwin >>>>>>>>>>> Release-a: commercial/2020-12-05T12:43:38 >>>>>>>>>>> Library: 9.02.08 >>>>>>>>>>> Qt IDE: 1.9.1/5.12.10(5.12.10) >>>>>>>>>>> Platform: Darwin 64 >>>>>>>>>>> Installer: J902 install >>>>>>>>>>> InstallPath: /users/bobtherriault/j902 >>>>>>>>>>> Contact: www.jsoftware.com >>>>>>>>>>> >>>>>>>>>>> Cheers, bob >>>>>>>>>>> >>>>>>>>>>>> On Dec 13, 2020, at 22:12, bill lam <[email protected]> wrote: >>>>>>>>>>>> >>>>>>>>>>>> I'm unfamiliar with dissect and PFkey. >>>>>>>>>>>> PFkey behaves differently under suspension mode or not. >>>>>>>>>>>> >>>>>>>>>>>> Your syntax seems correct. IIRC when running under non suspension >>>>>>>> mode, >>>>>>>>>>>> commands are executed as a script with empty stack. Can you check >>>>>>>> what is >>>>>>>>>>>> the value of coname'' when calling PFKey? >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Mon, Dec 14, 2020, 1:38 PM 'robert therriault' via >>> Programming < >>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> J902 is up and running on my system. Thank you to the team for >>>>> all of >>>>>>>>>>> the >>>>>>>>>>>>> work that goes into this process. I hope that you all have a >>>>> relaxed >>>>>>>>>>>>> holiday season after so much work. >>>>>>>>>>>>> >>>>>>>>>>>>> One question. Now that the issue with PF keys has been fixed, >>>>> what is >>>>>>>>>>> the >>>>>>>>>>>>> process for assigning applications like dissect to PF keys. The >>>>>>>> previous >>>>>>>>>>>>> approach described in the wiki results in >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> |noun result was required: finddissectline_dissect_ >>>>>>>>>>>>> | 1<#~.fs >>>>>>>>>>>>> |[-0] >>>>>>>>>>>>> >>>>>>>>>>>>> The wiki suggests using >>>>>>>>>>>>> F2;0;Dissect Line;dissect&.finddissectline_dissect_ 0 >>>>>>>>>>>>> >>>>>>>>>>>>> I use this for my jig augmented display >>>>>>>>>>>>> F6|0|Jig Augmented Display|((1 ; coname '') visual_jig_ 0) >>>>>>>>>>>>> and it returns a similar result. >>>>>>>>>>>>> >>>>>>>>>>>>> Any suggestions that you have would be welcome. >>>>>>>>>>>>> >>>>>>>>>>>>> Cheers, bob >>>>>>>>>>>>> >>>>>>>>>>>>>> On Dec 13, 2020, at 15:36, Henry Rich <[email protected]> >>>>> wrote: >>>>>>>>>>>>>> The new version of JQt does not require the ugly workaround for >>>>>>>> PFkeys >>>>>>>>>>>>> in debug that the previous version required. >>>>>>>>>>>>>> Henry Rich >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> This email has been checked for viruses by AVG. >>>>>>>>>>>>>> https://www.avg.com >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>> ---------------------------------------------------------------------- >>>>>>>>>>>>>> For information about J forums see >>>>>>>> http://www.jsoftware.com/forums.htm >>> ---------------------------------------------------------------------- >>>>>>>>>>>>> For information about J forums see >>>>>>>> http://www.jsoftware.com/forums.htm >>>>> ---------------------------------------------------------------------- >>>>>>>>>>>> For information about J forums see >>>>>>>> http://www.jsoftware.com/forums.htm >>>>> ---------------------------------------------------------------------- >>>>>>>>>>> For information about J forums see >>>>> http://www.jsoftware.com/forums.htm >>>>> ---------------------------------------------------------------------- >>>>>>>>>> For information about J forums see >>>>> http://www.jsoftware.com/forums.htm >>> ---------------------------------------------------------------------- >>>>>>>>> For information about J forums see >>>>> http://www.jsoftware.com/forums.htm >>>>>>>> >>>>>>>> -- >>>>>>>> This email has been checked for viruses by AVG. >>>>>>>> https://www.avg.com >>>>>>>> >>>>>>>> >>> ---------------------------------------------------------------------- >>>>>>>> For information about J forums see >>> http://www.jsoftware.com/forums.htm >>>>>>> ---------------------------------------------------------------------- >>>>>>> For information about J forums see >>> http://www.jsoftware.com/forums.htm >>>>>> ---------------------------------------------------------------------- >>>>>> For information about J forums see http://www.jsoftware.com/forums.htm >>>>> ---------------------------------------------------------------------- >>>>> For information about J forums see http://www.jsoftware.com/forums.htm >>>>> >>>> ---------------------------------------------------------------------- >>>> For information about J forums see http://www.jsoftware.com/forums.htm >>> ---------------------------------------------------------------------- >>> For information about J forums see http://www.jsoftware.com/forums.htm >>> >> ---------------------------------------------------------------------- >> For information about J forums see http://www.jsoftware.com/forums.htm > > > -- > This email has been checked for viruses by AVG. > https://www.avg.com > > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
