Le 24 nov. 2010 à 22:46, Richard Heck a écrit : On 11/24/2010 04:00 PM, Jean-Marc Lasgouttes wrote: >> Le 24 nov. 2010 à 17:32, Richard Heck a écrit : >>> Certainly part of this would be fairly simple to do. Call it >>> InsetSimpleCommand, and the only thing it does >>> is issue whatever command it is supposed to issue. The command in question >>> can be given in a module: >>> >>> InsetCommand InsertEndnotes >>> guiname "Insert Endnotes Here" >>> label Endnotes >>> command \theendnotes >>> End >>> >> Can't this be part of a normal inset definition with a special inset type >> "Command"? >> > I suppose, and really long-term maybe that'd be even better. My dream---I > seem to have a lot of these---is for Flex insets that take arguments. So you > click on the button and you get a dialog, where you can enter additional > arguments. Now the whole InsetCommand vs InsetCollapsable distinction starts > to vanish. An InsetCommand is just an InsetCollapsable with nothing but > arguments, and the sort of thing we're discussing is just a special case of > that. > > For now, though, given how the code is actually organized, it just seems > wrong that this sort of thing would be an InsetText, and at the moment the > whole InsetLayout business is pretty tied to text insets, if I remember right.
I suspect it is just a matter of creating a InsetWithLayout that derives from Inset, and let InsetText and InsetCommand derive from it. JMarc
