It turns out that the multiple calls are due to the fact that updateToolbars(), which is called at the end of the dipatch() routine, also calls update() which calls update_contents(). Since update() also gets called in, say, the INSET_APPLY routine, you get multiple calls. Is it worth looking into whether there's some way to set a flag that will prevent the multiple calls when we know they're not needed?
rh Angus Leeming wrote: > Abdelrazak Younes <[EMAIL PROTECTED]> writes: > >>> By the way, running several of these dialogs through the debugger, I've >>> noticed that this is generally true: if you go through update_contents() >>> once, you'll go through it two or three times. This does not seem like a >>> good thing, but I don't know enough about how this code works to have >>> any sense why it happens. >>> >> Welcome to the beautiful world of the GUII framework >> > > Richard, > > if you start out in frontend\controllers\Dialog.C, you should be able to > follow the logic of these dialogs quite easily. I imagine that > update_contents > is called from the Dialog as view().update(). I'd also imagine that the Qt > frontend has some signal or other connected to update_contents() which is why > it's being called multiple times. > > Angus > > -- ================================================================== Richard G Heck, Jr Professor of Philosophy Brown University http://frege.brown.edu/heck/ ================================================================== Get my public key from http://sks.keyserver.penguin.de Hash: 0x1DE91F1E66FFBDEC Learn how to sign your email using Thunderbird and GnuPG at: http://dudu.dyn.2-h.org/nist/gpg-enigmail-howto
