On Monday 02 April 2001 16:20, John Levon wrote:
> On Mon, 2 Apr 2001, Angus Leeming wrote:
>
> > No. forms is an xforms concept. That's why Allan and I have been rather
> > bemused in the past that you guys persist in calling your dialog files
> > FormXXX.[Ch]!
>
> ok, you are probably right,
On Mon, 2 Apr 2001, Angus Leeming wrote:
> No. forms is an xforms concept. That's why Allan and I have been rather
> bemused in the past that you guys persist in calling your dialog files
> FormXXX.[Ch]!
ok, you are probably right, but that's *my* meaning of Form ;)
otherwise the difference b
On Monday 02 April 2001 15:29, John Levon wrote:
> On Mon, 2 Apr 2001, Angus Leeming wrote:
>
> > On Monday 02 April 2001 13:52, John Levon wrote:
> > > On Sat, 31 Mar 2001, Angus Leeming wrote:
> > >
> > > > Moreover, I note that the popup has no apply() functionality. That
is,
> > you
> > >
On Mon, 2 Apr 2001, Angus Leeming wrote:
> On Monday 02 April 2001 13:52, John Levon wrote:
> > On Sat, 31 Mar 2001, Angus Leeming wrote:
> >
> > > Moreover, I note that the popup has no apply() functionality. That is,
> you
> >
> > A small request, can we make sure not to use the word "popup
On Monday 02 April 2001 13:52, John Levon wrote:
> On Sat, 31 Mar 2001, Angus Leeming wrote:
>
> > Moreover, I note that the popup has no apply() functionality. That is,
you
>
> A small request, can we make sure not to use the word "popup" in code. It
implies
> things that aren't true of the
On Sat, 31 Mar 2001, Angus Leeming wrote:
> Moreover, I note that the popup has no apply() functionality. That is, you
A small request, can we make sure not to use the word "popup" in code. It implies
things that aren't true of the dialogs. Furthermore we already have the terms "Form"
and "Dial
On Saturday 31 March 2001 13:30, Lars Gullik Bjønnes wrote:
> InsetFloat already exist so it would have to be a InsetFloatList.
>
> I do not think that InsetFloatList should be an InsetCommand, it could
> be but that would be misuse of the InsetCommand (hacking at the
> InsetParams...) (btw. I al
Angus Leeming <[EMAIL PROTECTED]> writes:
| I haven't really been following this float stuff, but I was thinking
| much the same myself. One controller-view to navigate through the
| document using whatever float type the user desired.
mmm
| It would make a lot of sense to define an InsetFloat
I haven't really been following this float stuff, but I was thinking much the
same myself. One controller-view to navigate through the document using
whatever float type the user desired.
It would make a lot of sense to define an InsetFloat to store this info and
to have a daughter class to ou
[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| So... it seems that the inset is storing the wrong value... the latex
| command should at any accord not be visilbe outside the inset.
I also think that we need a new inset for the floats.
InsetFloatList
This will store the float identifier (th
Angus Leeming <[EMAIL PROTECTED]> writes:
| On Saturday 31 March 2001 12:06, Lars Gullik Bjønnes wrote:
| > vector const ControlToc::getTypes() const
| > {
| > vector types;
| >
| > Buffer::Lists const tmp = lv_.view()->buffer()->getLists();
| >
| > Buffer::Lists::cons
On Saturday 31 March 2001 12:06, Lars Gullik Bjønnes wrote:
> vector const ControlToc::getTypes() const
> {
> vector types;
>
> Buffer::Lists const tmp = lv_.view()->buffer()->getLists();
>
> Buffer::Lists::const_iterator cit = tmp.begin();
> Buffer::Lists::cons
Angus Leeming <[EMAIL PROTECTED]> writes:
| On Saturday 31 March 2001 11:34, Lars Gullik Bjønnes wrote:
| > Angus Leeming <[EMAIL PROTECTED]> writes:
| >
| > | I've implemented a controller-view split for the TOC popup. The
| functionality
| > | is that of the original xforms code before Lars
On Saturday 31 March 2001 11:34, Lars Gullik Bjønnes wrote:
> Angus Leeming <[EMAIL PROTECTED]> writes:
>
> | I've implemented a controller-view split for the TOC popup. The
functionality
> | is that of the original xforms code before Lars introduced us to the new
> | buffer labelling scheme.
Angus Leeming <[EMAIL PROTECTED]> writes:
| I've implemented a controller-view split for the TOC popup. The functionality
| is that of the original xforms code before Lars introduced us to the new
| buffer labelling scheme.
?? So it does not work?
If you have hardcoded any of the lists I'll b
I've implemented a controller-view split for the TOC popup. The functionality
is that of the original xforms code before Lars introduced us to the new
buffer labelling scheme.
It isn't particularly pretty though. I'm sure we can do better. No doubt that
means that the API available to the GUI
16 matches
Mail list logo
