I was indeed trying to save mouse usage. In some locales there are so many verbs that scrolling and locating the right one is very annoying. (Also think of people with limited motor capabilities, who might find J's terseness attractive). I discovered I could type in the field and it would even complete the name (very useful!).
Accidentally selecting the wrong locale and typing in the name of a verb in a different locale, hitting enter without looking made me encounter the crash. So it was not intentional and I can't see a reason why to do this intentionally. I did not type in both locale and verb name. Actually the behavior of the two fields seems different: if typing an existing locale name, and clicking on an other field, the name list gets updated. If that locale does not exist, nothing happens on changing focus elsewhere, and when pressing enter, an empty verb name list appears. So this does not to do anything strange. As name completion works, I assume there is already a list of verbs in the selected locale against which verb names might be validated. As such a fix for this bug which does not lead to loss of the type-and-complete functionality could be checking whether a verb exists with the typed in prefix, if not turn the typed text red and refuse the confirming enter. Thanks for looking into this. Jan-Pieter 2015-05-26 3:57 GMT+02:00 Henry Rich <[email protected]>: > The easiest fix for this is to change the combobox to a combolist; that > will make it impossible to type any name, thus impossible to type a wrong > name. > > That seems OK to me, so I wonder: why were you typing a name at all rather > than selecting? Was it necessary to type a name not in the menu? > > If you were just trying to save mouse clicks, that's reasonable, and I > could accommodate that by looking up the name you typed in the list of > options for the control. I guess I really want to know if you had a need > to type a name that was not in the list. > > The code would really not be happy if you typed into BOTH the name and > locale fields and then pressed ENTER. Did you do that? > > After this rambling "analysis", I'm leaning toward using combolist, unless > there's a strong counterargument. > > Henry Rich > > > > > On 5/25/2015 8:12 AM, Jan-Pieter Jacobs wrote: > >> Thank you for your quick reply, Henry. >> >> on 1. : that is exactly what I am seeing. Thank you for the explanation. >> >> Jan-Pieter >> >> 2015-05-25 13:36 GMT+02:00 Henry Rich <[email protected]>: >> >> I have been working on the debugger & will look into these. >>> >>> 0. I'll check. >>> >>> 1. When you debug a verb with a "header", like >>> >>> dverb =: 3 : 0"1 >>> ... >>> ) >>> >>> the debugger treats it as a tacit verb and doesn't let you look inside. >>> It displays like a tacit verb (which in fact it is!), all on one line, >>> with >>> the LFs replaced by (1{a.). Is this what you are seeing? >>> >>> To debug it you have to split it into >>> >>> dverb =: dverbbody"1 >>> dverbbody =: 3 : 0 >>> ... >>> ) >>> >>> In the next release the debugger will do this automatically for you. If >>> you select dverb for a stop, it will create the body and replace dverb >>> with >>> a verb that points to the body. Stops will be placed into the body. >>> >>> Henry Rich >>> >>> >>> >>> On 5/25/2015 5:31 AM, Jan-Pieter Jacobs wrote: >>> >>> Writing a cover verb for dsygv in the Lapack addon, I noticed 2 bugs >>>> with >>>> the debugger: >>>> >>>> 0. When you enter a non-existing verb in the "name" field and press >>>> enter, >>>> the debugger crashes J. This does not happen for the locale field. >>>> >>>> 1. The debugger seems to have issues with some types of line endings, >>>> making newlines show up as what the console shows for (1{a.) (gmail >>>> seems >>>> to refuse this character here). This seriously hampers debugging, as the >>>> debugger shows all code in one single line when an error occurs or when >>>> setting a "stop Line" in the stop manager. >>>> An example of this can be seen taking a look at >>>> ~/addons/math/lapack/geev.ijs. >>>> I presume it's an Unix/Windows line ending issue (I'm on Windows 8.1, 64 >>>> bit, most recent J, all addons up to date). >>>> >>>> >>>> Best regards, >>>> >>>> Jan-Pieter >>>> ---------------------------------------------------------------------- >>>> 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
