From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keith Seitz To: Paul Breed Cc: insight@sourceware.cygnus.com Subject: Re: results insight script init... Date: Mon, 17 Jul 2000 05:30:00 -0000 Message-id: <3972FC64.ADE256EF@firetalk.com> References: <20000715143607.18927.qmail@web3505.mail.yahoo.com> X-SW-Source: 2000-q3/msg00072.html Paul Breed wrote: > > My Goal was to have Insight automatically connect > to a specific target on startup and to prevent > the attach dialog when you hit run. > > I have it all working my gdb.ini file: > > symbol-file DBdebugdemo.elf > set remotebaud 57600 > set remotedevice COM1 > target remote COM1 > tk set ::gdb_target_name remote > tk gdbtk_update > tk gdbtk_next > tk gdbtk_update > tk gdbtk_idle > > The only problem remaining is that the cursor in > the code window is an hourglass, and not a pointer. > This normally occurs as part of the idle callbacks (invoked with gdbtk_idle). Perhaps you simply need to add gdbtk_idle call to an "after idle" or something. (I dunno, actually. I am working on a similar problem myself...) > I believe that this can be fixed with > SrcWin::enable_ui { on } > or > SrcWin::no_inferior > > But how do I get an instance of the source window? > One question first: can you type into the console window? If so, then you've probably found a bug in one of the idle or update callbacks. Using "gdbtk_idle" will cause all windows to go "idle", ready for user input. Now onto the real question. You can use the proc "ManagedWin::find className" to find a window of the given classname. So you would use "ManagedWin::find Src". This will return a list of all the objects of class "Src". It could be one, it could be many. Keith