That's what I use to create the ijx window when I get an error in a run-only
application. Then it is easy to display the error information in that window
and start debugging. Beats the heck out of having to restart the application
in development mode and trying to recreate the problem.
On Jan 26, 2008 4:57 PM, Henry Rich <[EMAIL PROTECTED]> wrote:
> The code in boot.ijs is:
>
> if. IFCONSOLE do.
> boot 'main\conlib.ijs'
> boot 'extras\util\jadecon.ijs'
> boxdraw_j_ 1 2 0 {~ ('Darwin';'Win') i. <UNAME
> startupconsole''
> else.
> boot 'main\winlib.ijs'
> boot 'extras\util\jadefull.ijs'
> boot 'extras\util\jijs.ijs'
> boot 'extras\util\cfgread.ijs'
> configure_jcfg_ 0
> if. -. IFJIJX_j_ do. newijx_jijs_ 0 end.
> end.
>
> I think that newijx_jijs_ is what creates the .ijx window.
> configure_jcfg_ runs the configuration, including the startup
> file, so you are correct that startup runs before the .ijx.
>
> Henry Rich
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf Of Don Guinn
> > Sent: Saturday, January 26, 2008 6:52 PM
> > To: Beta forum
> > Subject: Re: [Jbeta] Locale of ijx
> >
> > I found my problem and fixed it.
> >
> > However, I created a very simple startup.ijs which showed that the ijx
> > locale is not created before startup.ijs is run. If the ijx
> > locale has to be
> > <'0' then one cannot create any numbered locales in startup.ijs .
> >
> > The startup.ijs script:
> > locales_base_=:conl''
> >
> > When J completes initialization:
> > names''
> > locales
> > locales
> > +----+-+----+----+-+
> > |base|j|jcfg|jijs|z|
> > +----+-+----+----+-+
> >
> > Does the <'0' locale for the ijx window get created even for
> > run-time only
> > applications?
> >
> > In J601 I changed error handling for run-time applications to
> > bring up a ijx
> > window on an error instead of just displaying an error message and
> > terminating J. I have found this to be most useful in debugging an
> > unexpected error. Sometimes the errors are hard to duplicate
> > and it is nice
> > to be able to look at the problem as it occurs. If with this
> > modification
> > and the application uses numbered locales then the ijx locale
> > may not be
> > <'0' .
> >
> > But I'm really glad to see that wcsize_z_ really works now
> > and is no longer
> > a dummy.
> >
> > On Jan 25, 2008 6:54 PM, Chris Burke <[EMAIL PROTECTED]> wrote:
> >
> > > Don Guinn wrote:
> > > > I'm not sure what my initialization code is doing yet,
> > but for some
> > > reason
> > > > it causes the ijx locale to come up as <'1' instead of <'0' . This
> > > causes
> > > > wcsize_z_ to fail as it looks for SMHWNDP_0_ , which is
> > not there as
> > > that
> > > > locale is for something else. Don't know what yet. That's
> > my fault. It
> > > is
> > > > <'0' if I start up J without my initialization.
> > > >
> > > > What concerns me is the assumption that the ijx locale is
> > always <'0' .
> > > Is
> > > > this a valid assumption? Should there be a name placed in
> > the z locale
> > > > containing the name of the ijx locale allowing a
> > reference to it like
> > > > SMHWNDP__ijxlocale in case the ijx locale moves?
> > >
> > > The boot sequence does create the ijx window first, and
> > since there is
> > > only one such window, I think it is reasonable to assume
> > that this is in
> > > locale 0.
> > >
> > > Your own initialization code should be run at the end of
> > boot - this is
> > > best done by putting it in the startup script.
> > >
> > >
> > ----------------------------------------------------------------------
> > > 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
