I also think that the GW toolkit, or perhaps it's the homer library, has a routine for getting the contents of a text file into a string variable, which you could then put into the editbox.
Chip ------------------------------ Chip Orange Database Administrator Florida Public Service Commission chip.ora...@psc.state.fl.us (850) 413-6314 (Any opinions expressed are solely those of the author and do not necessarily reflect those of the Florida Public Service Commission.) > -----Original Message----- > From: Jeff Bishop [mailto:j...@jeffbishop.com] > Sent: Friday, July 10, 2009 10:54 AM > To: gw-scripting@gwmicro.com > Subject: Re: creating an edit box > > Sure. > > You could loop through the keys in the INI file and parse it > out yourself, > or you could use the hotkey manager to get at that data. You > then build the > string and assign it to the text property of the editbox > control and show > the dialog. > > ----- Original Message ----- > From: "Kevin Huber" <kevin.hub...@gmail.com> > To: "gw-scripting" <gw-scripting@gwmicro.com> > Sent: Friday, July 10, 2009 7:51 AM > Subject: creating an edit box > > > > Hi: > > Is there any way of showing the contents of an Ini file in > a read-only > > edit box? > > I would like to put a key into my Proofreading Script, that > will list > > all the names of the hotkeys and what they do, similar to > alt-shift-h, > > except that the information would be shown on the screen instead of > > just spoken. > > I am thinking of creating a dialog box with two controls. One would > > be a read-only edit box, containing a list of the hotkeys and their > > names, and a Close button, similar to the dialog that comes > up on the > > screen in the Weather-Or-Not script, when you press Insert-Alt-w. > > > >
