On Wed, Apr 10, 2002 at 04:46:07PM +0200, Andre Poenitz wrote: > > On Wed, Apr 10, 2002 at 05:38:10PM +0300, Martin Vermeer wrote: > > case MM_SUPER: > > - lv_->getLyXFunc()->dispatch(LFUN_MATH_MODE); > > + //lv_->getLyXFunc()->dispatch(LFUN_MATH_MODE); > > lv_->getLyXFunc()->dispatch(LFUN_SUPERSCRIPT); > > break; > > > > case MM_SUB: > > - lv_->getLyXFunc()->dispatch(LFUN_MATH_MODE); > > + //lv_->getLyXFunc()->dispatch(LFUN_MATH_MODE); > > lv_->getLyXFunc()->dispatch(LFUN_SUBSCRIPT); > > break; > > > > > > I don't recommend it though as these statements were put there > > for a reason. André do you have a better idea? > > Not really. > > But if this cures the symtoms, it is fine with me for 1.2. > > Andre'
Actually the reason those statements are there is to go into mathed mode when pressing the super- or subscript button on the math panel while in text mode. Without these statements, circumflex or underscore get inserted into text. Unpleasant, but more clearly visible the user as a "misfeature" and therefore IMO preferable. So please apply -- perhaps with a comment added for the edification of future generations of developers. A proper fix would mean executing these statements only if not already in mathed mode. But how to test for that? Martin
msg36454/pgp00000.pgp
Description: PGP signature
