On Wed, Feb 04, 2004 at 11:53:04AM +0100, Jean-Marc Lasgouttes wrote:
> > "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
>
> Andre> This always returns 'true', so we can have 'void' instead and
> Andre> remove some never executed code...
>
> How come insetAllowed does not enter into the
> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
Andre> This always returns 'true', so we can have 'void' instead and
Andre> remove some never executed code...
How come insetAllowed does not enter into the picture? At which place
do we decide that an inset is allowed or not?
Actually,
On Wed, Feb 04, 2004 at 09:47:31AM +, Angus Leeming wrote:
> Andre Poenitz wrote:
> > This always returns 'true', so we can have 'void' instead and remove
> > some never executed code...
>
> Hold on! These lfuns can be called from outside can't they? So it's
> possible for a user to try and i
On Wed, Feb 04, 2004 at 09:47:31AM +, Angus Leeming wrote:
> Andre Poenitz wrote:
> > This always returns 'true', so we can have 'void' instead and remove
> > some never executed code...
>
> Hold on! These lfuns can be called from outside can't they? So it's
> possible for a user to try and i
Andre Poenitz wrote:
> This always returns 'true', so we can have 'void' instead and remove
> some never executed code...
Hold on! These lfuns can be called from outside can't they? So it's
possible for a user to try and insert an inset in a layout that
doesn't allow it. Isn't this the reason fo
This always returns 'true', so we can have 'void' instead and remove
some never executed code...
Andre'
--
Those who desire to give up Freedom in order to gain Security, will not have,
nor do they deserve, either one. (T. Jefferson or B. Franklin or both...)
Index: BufferView.C
