The function "signalevent" in wd/form.cpp generates the events for J. So look for anything that calls this function.
Button clicks are unusual in that the call to signalevent is made in form.cpp, not button.cpp (the connection being made via a signalMapper). On Thu, Nov 6, 2014 at 3:33 PM, Henry Rich <[email protected]> wrote: > But some ARE signaled to the J session, no? Like button, for example. > What indicates the ones that get through to the J session? > > Henry Rich > > > On 11/6/2014 6:30 PM, chris burke wrote: > >> connect() and SIGNAL() are internal to JQt, and not necessarily signalled >> to the J session. You can ignore all these. >> >> On Thu, Nov 6, 2014 at 3:23 PM, Henry Rich <[email protected]> wrote: >> >> Good, thanks. I'm following along right behind you, and there seem to be >>> some other events that are generated by something other than >>> signalevent(). Something in connect() and SIGNAL() but I don't >>> understand >>> it yet. >>> >>> In your list, the button control doesn't have any events noted, but >>> surely >>> it creates "button"! But I don't see just how. >>> >>> The isigraph control has many more events, whose names seem to be >>> calculated on the fly. >>> >>> I think module-by-module analysis will be needed, but it doesn't look too >>> hard. If someone can explain how the button event for a button control >>> is >>> mapped, I'd be obliged. >>> >>> Henry Rich >>> >>> >>> On 11/6/2014 6:15 PM, Raul Miller wrote: >>> >>> Here's a mechanically generated list of what I think are the events >>>> (three columns here, separated by : filename, line number (1 is first >>>> line) and text of that line): >>>> >>>> checkbox.cpp:46: event="button"; >>>> combobox.cpp:31: event="select"; >>>> dateedit.cpp:100: event="changed"; >>>> dspinbox.cpp:55: event="changed"; >>>> edit.cpp:40: event="button"; >>>> form.cpp:163: child->event="button"; >>>> form.cpp:183: event="close"; >>>> form.cpp:261: event="close"; >>>> form.cpp:267: event="cancel"; >>>> form.cpp:273: event="fkey"; >>>> form.cpp:277: event="fkey"; >>>> form.cpp:298: event="close"; >>>> form.cpp:448: event="timer"; >>>> isigraph2.cpp:78: pchild->event="paint"; >>>> isigraph2.cpp:114: pchild->event="resize"; >>>> isigraph2.cpp:222: pchild->event="focus"; >>>> isigraph2.cpp:232: pchild->event="focuslost"; >>>> listbox.cpp:76: event="button"; >>>> listbox.cpp:83: event="select"; >>>> menus.cpp:85: event="button"; >>>> opengl2.cpp:55: pchild->event="initialize"; >>>> opengl2.cpp:65: pchild->event="paint"; >>>> opengl2.cpp:86: pchild->event="resize"; >>>> opengl2.cpp:200: pchild->event="focus"; >>>> opengl2.cpp:210: pchild->event="focuslost"; >>>> radiobutton.cpp:61: event="button"; >>>> slider.cpp:65: event="changed"; >>>> spinbox.cpp:50: event="changed"; >>>> table.cpp:1174: event="change"; >>>> table.cpp:1188: event="mb" + lmr + "down"; >>>> table.cpp:1197: event="clicked"; >>>> table.cpp:1212: event="mb" + lmr + "dbl"; >>>> table.cpp:1221: event="mark"; >>>> table.cpp:1246: event="change"; >>>> tabs.cpp:57: event="select"; >>>> tabs.cpp:65: event="tabclose"; >>>> timeedit.cpp:58: event="changed"; >>>> toolbar.cpp:51: event="button"; >>>> >>>> FYI, >>>> >>>> ------------------------------------------------------------ >>>> ---------- >>>> >>> 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
