On Wed, Nov 01, 2006 at 08:43:19AM +1800, Bo Peng wrote:
I've just enabled it.
Then, it makes sense to save toolbar position in session. Could you
please tell me the functions to get/set toolbar position? Note that
the interface has to be done independent of frontend.
Why don't you simply
On Tue, Oct 31, 2006 at 03:30:43PM +, John Levon wrote:
On Tue, Oct 31, 2006 at 03:22:34PM +, José Matos wrote:
On Tuesday 31 October 2006 2:43 pm, John Levon wrote:
On Tue, Oct 31, 2006 at 03:42:32PM +0100, Peter Kümmel wrote:
I've just enabled it.
Nice :(
Could
On Tue, Oct 31, 2006 at 03:51:44PM +0100, Peter Kümmel wrote:
José Matos wrote:
GuiView.C:78: error: ISO C++ forbids declaration of 'QTabBar' with no type
I've added the include of QTabBar.
Does this help?
Maybe I should remove the Qt headers from the precompiled msvc-headers.
Why?
The
On Wed, Nov 01, 2006 at 08:43:19AM +1800, Bo Peng wrote:
> >I've just enabled it.
> >
>
> Then, it makes sense to save toolbar position in session. Could you
> please tell me the functions to get/set toolbar position? Note that
> the interface has to be done independent of frontend.
Why don't
On Tue, Oct 31, 2006 at 03:30:43PM +, John Levon wrote:
> On Tue, Oct 31, 2006 at 03:22:34PM +, José Matos wrote:
>
> > On Tuesday 31 October 2006 2:43 pm, John Levon wrote:
> > > On Tue, Oct 31, 2006 at 03:42:32PM +0100, Peter Kümmel wrote:
> > > > I've just enabled it.
> > >
> > > Nice
On Tue, Oct 31, 2006 at 03:51:44PM +0100, Peter Kümmel wrote:
> José Matos wrote:
> > GuiView.C:78: error: ISO C++ forbids declaration of 'QTabBar' with no type
>
> I've added the include of QTabBar.
> Does this help?
>
> Maybe I should remove the Qt headers from the precompiled msvc-headers.
On Tue, Oct 31, 2006 at 04:46:07PM +0100, Abdelrazak Younes wrote:
Peter Kümmel wrote:
Because
- it costs us nothing
- it's a nice feature for the user
- I don't see any reason way we should disable it
- we are releasing only a alpha version
- I don't want to start a
On Tue, Oct 31, 2006 at 04:46:07PM +0100, Abdelrazak Younes wrote:
> Peter Kümmel wrote:
> > Because
> > - it costs us nothing
> > - it's a nice feature for the user
> > - I don't see any reason way we should disable it
> > - we are releasing only a alpha version
> > - I don't want to
John Levon wrote:
On Tue, Oct 31, 2006 at 07:46:04PM +0100, Peter Kümmel wrote:
As I understand it, your main reason against 'setMovable(true)'
is the the 'tearing off' (comment in the code) or the
'popping out'. But this is not possible also not with my
So I discovered when I finished
John Levon wrote:
On Tue, Oct 31, 2006 at 08:12:26PM +0100, Michael Gerz wrote:
Why does the Review toolbar have to have the review flag? You can
BTW, one comment about the Review toolbar. It's very neat functionality
to have, but it's severely hampered by the lack of any icons.
On Wed, Nov 01, 2006 at 09:48:49AM +0100, Peter Kümmel wrote:
3. Disable it again when the Toolbars dialog is done: only show the
grippies when the dialog is active, like Firefox etc. do
Why not. The session stuff is on the why.
Does the 3. point mean to completely disable the context
John Levon wrote:
> On Tue, Oct 31, 2006 at 07:46:04PM +0100, Peter Kümmel wrote:
>
>> As I understand it, your main reason against 'setMovable(true)'
>> is the the 'tearing off' (comment in the code) or the
>> 'popping out'. But this is not possible also not with my
>
> So I discovered when I
John Levon wrote:
On Tue, Oct 31, 2006 at 08:12:26PM +0100, Michael Gerz wrote:
Why does the "Review" toolbar have to have the "review" flag? You can
BTW, one comment about the Review toolbar. It's very neat functionality
to have, but it's severely hampered by the lack of any icons.
On Wed, Nov 01, 2006 at 09:48:49AM +0100, Peter Kümmel wrote:
> > 3. Disable it again when the Toolbars dialog is done: only show the
> > grippies when the dialog is active, like Firefox etc. do
>
> Why not. The session stuff is on the why.
>
> Does the 3. point mean to completely disable the
Bo Peng wrote:
OK, I disable the default precompilng of Qt headers.
I guess you VC guys can turn it on during development, and turn it off
and test before commit?
I don't know if there is a way of disabling it without a complete recompile.
Maybe it will work only with two build trees.
--
José Matos wrote:
On Tuesday 31 October 2006 2:51 pm, Peter Kümmel wrote:
José Matos wrote:
GuiView.C:78: error: ISO C++ forbids declaration of 'QTabBar' with no
type
I've added the include of QTabBar.
Does this help?
It helps but it is not enough:
...
GuiView.C:83: error:
OK, I disable the default precompilng of Qt headers.
I guess you VC guys can turn it on during development, and turn it off
and test before commit?
Bo
On Tuesday 31 October 2006 2:42 pm, Peter Kümmel wrote:
Because
- it costs us nothing
- it's a nice feature for the user
- I don't see any reason way we should disable it
- we are releasing only a alpha version
- I don't want to start a endless discussion
I've just enabled it.
Abdelrazak Younes wrote:
Peter Kümmel wrote:
Because
- it costs us nothing
- it's a nice feature for the user
- I don't see any reason way we should disable it
- we are releasing only a alpha version
- I don't want to start a endless discussion
I've just enabled it.
No
Abdelrazak Younes wrote:
José Matos wrote:
On Tuesday 31 October 2006 2:42 pm, Peter Kümmel wrote:
Because
- it costs us nothing
- it's a nice feature for the user
- I don't see any reason way we should disable it
- we are releasing only a alpha version
- I don't want to start a
I've just enabled it.
Then, it makes sense to save toolbar position in session. Could you
please tell me the functions to get/set toolbar position? Note that
the interface has to be done independent of frontend.
Bo
Because
- it costs us nothing
- it's a nice feature for the user
- I don't see any reason way we should disable it
- we are releasing only a alpha version
- I don't want to start a endless discussion
I've just enabled it.
Peter
The diff:
Index: frontends/qt4/QLToolbar.C
Peter Kümmel wrote:
Abdelrazak Younes wrote:
Peter Kümmel wrote:
Because
- it costs us nothing
- it's a nice feature for the user
- I don't see any reason way we should disable it
- we are releasing only a alpha version
- I don't want to start a endless discussion
I've just enabled
Peter Kümmel wrote:
Abdelrazak Younes wrote:
José Matos wrote:
On Tuesday 31 October 2006 2:42 pm, Peter Kümmel wrote:
Because
- it costs us nothing
- it's a nice feature for the user
- I don't see any reason way we should disable it
- we are releasing only a alpha version
- I don't
On Tue, Oct 31, 2006 at 03:42:32PM +0100, Peter Kümmel wrote:
I've just enabled it.
Nice :(
john
Bo Peng wrote:
I've just enabled it.
Then, it makes sense to save toolbar position in session. Could you
please tell me the functions to get/set toolbar position? Note that
the interface has to be done independent of frontend.
Bo
Yes, I also think this should be added, see the
José Matos wrote:
GuiView.C:78: error: ISO C++ forbids declaration of 'QTabBar' with no type
I've added the include of QTabBar.
Does this help?
Maybe I should remove the Qt headers from the precompiled msvc-headers.
Peter
On Tuesday 31 October 2006 2:51 pm, Peter Kümmel wrote:
José Matos wrote:
GuiView.C:78: error: ISO C++ forbids declaration of 'QTabBar' with no
type
I've added the include of QTabBar.
Does this help?
It helps but it is not enough:
if /bin/sh ../../../libtool --tag=CXX --mode=compile
On Tuesday 31 October 2006 3:30 pm, John Levon wrote:
That it just happened without discussion of whether it makes sense,
unlike when I disabled it, when I actually asked people?
John time passes and my memory is not improving. :-)
Do you remember the arguments at that time?
I have
On Tuesday 31 October 2006 2:43 pm, John Levon wrote:
On Tue, Oct 31, 2006 at 03:42:32PM +0100, Peter Kümmel wrote:
I've just enabled it.
Nice :(
Could you elaborate, please?
The switch is simple, and we can change it at any time. :-)
john
--
José Abílio
John Levon wrote:
On Tue, Oct 31, 2006 at 03:42:32PM +0100, Peter Kümmel wrote:
I've just enabled it.
Nice :(
Maybe we could add a settings somewhere to disable it for people like you.
Abdel.
Abdelrazak Younes wrote:
Peter Kümmel wrote:
Abdelrazak Younes wrote:
José Matos wrote:
On Tuesday 31 October 2006 2:42 pm, Peter Kümmel wrote:
Because
- it costs us nothing
- it's a nice feature for the user
- I don't see any reason way we should disable it
- we are releasing
John == John Levon [EMAIL PROTECTED] writes:
John Besides us not having any support for remembering it in a
John session, it's far too easy to pop out toolbars. I've also never
John understood why it's preferable to have toolbars that occlude
John other windows (and indeed UI design experts
On Tue, Oct 31, 2006 at 04:00:21PM +, José Matos wrote:
That it just happened without discussion of whether it makes sense,
unlike when I disabled it, when I actually asked people?
John time passes and my memory is not improving. :-)
Do you remember the arguments at that time?
Peter Kümmel wrote:
Because
- it costs us nothing
- it's a nice feature for the user
- I don't see any reason way we should disable it
- we are releasing only a alpha version
- I don't want to start a endless discussion
I've just enabled it.
I think we should make a distinction
Peter Kümmel wrote:
Because
- it costs us nothing
- it's a nice feature for the user
- I don't see any reason way we should disable it
- we are releasing only a alpha version
- I don't want to start a endless discussion
I've just enabled it.
No problem with it but how does this work
José Matos wrote:
On Tuesday 31 October 2006 2:42 pm, Peter Kümmel wrote:
Because
- it costs us nothing
- it's a nice feature for the user
- I don't see any reason way we should disable it
- we are releasing only a alpha version
- I don't want to start a endless discussion
I've just
Peter Kümmel wrote:
José Matos wrote:
On Tuesday 31 October 2006 2:51 pm, Peter Kümmel wrote:
José Matos wrote:
GuiView.C:78: error: ISO C++ forbids declaration of 'QTabBar' with no
type
I've added the include of QTabBar.
Does this help?
It helps but it is not enough:
...
GuiView.C:83:
On Tue, Oct 31, 2006 at 03:22:34PM +, José Matos wrote:
On Tuesday 31 October 2006 2:43 pm, John Levon wrote:
On Tue, Oct 31, 2006 at 03:42:32PM +0100, Peter Kümmel wrote:
I've just enabled it.
Nice :(
Could you elaborate, please?
The switch is simple, and we can change it
Hi John,
sorry if I've annoyed you. At least we have now a active
discussion about it and I know the author of the code which
I've changed. ;)
As I understand it, your main reason against 'setMovable(true)'
is the the 'tearing off' (comment in the code) or the
'popping out'. But this is not
Because of this I haven't seen a reason not to enable 'movable'.
I like movable toolbars but I share JMarc's concerns about math/table
toolbars and session. I will add session/toolbar very soon and I would
appreciate it if you can show me how to get/restore toolbar position.
Bo
John Levon wrote:
That it just happened without discussion of whether it makes sense,
unlike when I disabled it, when I actually asked people?
Anyway, seems I've been overruled by the current devs, so it doesn't
really matter.
Peter, to tell the truth I am also not happy about your change
Michael Gerz wrote:
John Levon wrote:
That it just happened without discussion of whether it makes sense,
unlike when I disabled it, when I actually asked people?
Anyway, seems I've been overruled by the current devs, so it doesn't
really matter.
Peter, to tell the truth I am also not
Bo Peng wrote:
Because of this I haven't seen a reason not to enable 'movable'.
I like movable toolbars but I share JMarc's concerns about math/table
toolbars and session. I will add session/toolbar very soon and I would
appreciate it if you can show me how to get/restore toolbar position
Peter Kümmel wrote:
Anyway, all the toolbar stuff is a moving target so lets not argue
about it.
Yes. And I am not going to touch your code.
Michael
Michael Gerz wrote:
Peter Kümmel wrote:
Anyway, all the toolbar stuff is a moving target so lets not argue
about it.
Yes. And I am not going to touch your code.
Thanks, Michael, and sorry for my brutal committing.
Hope I'm now not in your ignore list. ;)
Peter
On Tuesday 31 October 2006 8:57 pm, Peter Kümmel wrote:
Michael Gerz wrote:
Peter Kümmel wrote:
Anyway, all the toolbar stuff is a moving target so lets not argue
about it.
Yes. And I am not going to touch your code.
Thanks, Michael, and sorry for my brutal committing.
Hope I'm now
José Matos wrote:
On Tuesday 31 October 2006 8:57 pm, Peter Kümmel wrote:
Michael Gerz wrote:
Peter Kümmel wrote:
Anyway, all the toolbar stuff is a moving target so lets not argue
about it.
Yes. And I am not going to touch your code.
Thanks, Michael, and sorry for my brutal committing.
On Tue, Oct 31, 2006 at 07:46:04PM +0100, Peter Kümmel wrote:
As I understand it, your main reason against 'setMovable(true)'
is the the 'tearing off' (comment in the code) or the
'popping out'. But this is not possible also not with my
So I discovered when I finished the build. My apologies
On Tue, Oct 31, 2006 at 08:12:26PM +0100, Michael Gerz wrote:
Why does the Review toolbar have to have the review flag? You can
BTW, one comment about the Review toolbar. It's very neat functionality
to have, but it's severely hampered by the lack of any icons. It's not
fun work if you're not
Bo Peng wrote:
>> OK, I disable the default precompilng of Qt headers.
>
> I guess you VC guys can turn it on during development, and turn it off
> and test before commit?
I don't know if there is a way of disabling it without a complete recompile.
Maybe it will work only with two build trees.
José Matos wrote:
> On Tuesday 31 October 2006 2:51 pm, Peter Kümmel wrote:
>> José Matos wrote:
>>> GuiView.C:78: error: ISO C++ forbids declaration of 'QTabBar' with no
>>> type
>> I've added the include of QTabBar.
>> Does this help?
>
> It helps but it is not enough:
...
> GuiView.C:83:
OK, I disable the default precompilng of Qt headers.
I guess you VC guys can turn it on during development, and turn it off
and test before commit?
Bo
On Tuesday 31 October 2006 2:42 pm, Peter Kümmel wrote:
> Because
> - it costs us nothing
> - it's a nice feature for the user
> - I don't see any reason way we should disable it
> - we are releasing only a alpha version
> - I don't want to start a endless discussion
>
> I've just
Abdelrazak Younes wrote:
> Peter Kümmel wrote:
>> Because
>> - it costs us nothing
>> - it's a nice feature for the user
>> - I don't see any reason way we should disable it
>> - we are releasing only a alpha version
>> - I don't want to start a endless discussion
>>
>> I've just enabled
Abdelrazak Younes wrote:
> José Matos wrote:
>> On Tuesday 31 October 2006 2:42 pm, Peter Kümmel wrote:
>>> Because
>>> - it costs us nothing
>>> - it's a nice feature for the user
>>> - I don't see any reason way we should disable it
>>> - we are releasing only a alpha version
>>> - I
I've just enabled it.
Then, it makes sense to save toolbar position in session. Could you
please tell me the functions to get/set toolbar position? Note that
the interface has to be done independent of frontend.
Bo
Because
- it costs us nothing
- it's a nice feature for the user
- I don't see any reason way we should disable it
- we are releasing only a alpha version
- I don't want to start a endless discussion
I've just enabled it.
Peter
The diff:
Index: frontends/qt4/QLToolbar.C
Peter Kümmel wrote:
Abdelrazak Younes wrote:
Peter Kümmel wrote:
Because
- it costs us nothing
- it's a nice feature for the user
- I don't see any reason way we should disable it
- we are releasing only a alpha version
- I don't want to start a endless discussion
I've just enabled
Peter Kümmel wrote:
Abdelrazak Younes wrote:
José Matos wrote:
On Tuesday 31 October 2006 2:42 pm, Peter Kümmel wrote:
Because
- it costs us nothing
- it's a nice feature for the user
- I don't see any reason way we should disable it
- we are releasing only a alpha version
- I don't
On Tue, Oct 31, 2006 at 03:42:32PM +0100, Peter Kümmel wrote:
> I've just enabled it.
Nice :(
john
Bo Peng wrote:
>> I've just enabled it.
>>
>
> Then, it makes sense to save toolbar position in session. Could you
> please tell me the functions to get/set toolbar position? Note that
> the interface has to be done independent of frontend.
>
> Bo
>
>
Yes, I also think this should be added,
José Matos wrote:
> GuiView.C:78: error: ISO C++ forbids declaration of 'QTabBar' with no type
I've added the include of QTabBar.
Does this help?
Maybe I should remove the Qt headers from the precompiled msvc-headers.
Peter
On Tuesday 31 October 2006 2:51 pm, Peter Kümmel wrote:
> José Matos wrote:
> > GuiView.C:78: error: ISO C++ forbids declaration of 'QTabBar' with no
> > type
>
> I've added the include of QTabBar.
> Does this help?
It helps but it is not enough:
if /bin/sh ../../../libtool --tag=CXX
On Tuesday 31 October 2006 3:30 pm, John Levon wrote:
>
> That it just happened without discussion of whether it makes sense,
> unlike when I disabled it, when I actually asked people?
John time passes and my memory is not improving. :-)
Do you remember the arguments at that time?
I have
On Tuesday 31 October 2006 2:43 pm, John Levon wrote:
> On Tue, Oct 31, 2006 at 03:42:32PM +0100, Peter Kümmel wrote:
> > I've just enabled it.
>
> Nice :(
Could you elaborate, please?
The switch is simple, and we can change it at any time. :-)
> john
--
José Abílio
John Levon wrote:
On Tue, Oct 31, 2006 at 03:42:32PM +0100, Peter Kümmel wrote:
I've just enabled it.
Nice :(
Maybe we could add a settings somewhere to disable it for people like you.
Abdel.
Abdelrazak Younes wrote:
> Peter Kümmel wrote:
>> Abdelrazak Younes wrote:
>>> José Matos wrote:
On Tuesday 31 October 2006 2:42 pm, Peter Kümmel wrote:
> Because
> - it costs us nothing
> - it's a nice feature for the user
> - I don't see any reason way we should
> "John" == John Levon <[EMAIL PROTECTED]> writes:
John> Besides us not having any support for remembering it in a
John> session, it's far too easy to pop out toolbars. I've also never
John> understood why it's preferable to have toolbars that occlude
John> other windows (and indeed UI design
On Tue, Oct 31, 2006 at 04:00:21PM +, José Matos wrote:
> > That it just happened without discussion of whether it makes sense,
> > unlike when I disabled it, when I actually asked people?
>
> John time passes and my memory is not improving. :-)
>
> Do you remember the arguments at that
Peter Kümmel wrote:
Because
- it costs us nothing
- it's a nice feature for the user
- I don't see any reason way we should disable it
- we are releasing only a alpha version
- I don't want to start a endless discussion
I've just enabled it.
I think we should make a distinction
Peter Kümmel wrote:
Because
- it costs us nothing
- it's a nice feature for the user
- I don't see any reason way we should disable it
- we are releasing only a alpha version
- I don't want to start a endless discussion
I've just enabled it.
No problem with it but how does this work
José Matos wrote:
On Tuesday 31 October 2006 2:42 pm, Peter Kümmel wrote:
Because
- it costs us nothing
- it's a nice feature for the user
- I don't see any reason way we should disable it
- we are releasing only a alpha version
- I don't want to start a endless discussion
I've just
Peter Kümmel wrote:
José Matos wrote:
On Tuesday 31 October 2006 2:51 pm, Peter Kümmel wrote:
José Matos wrote:
GuiView.C:78: error: ISO C++ forbids declaration of 'QTabBar' with no
type
I've added the include of QTabBar.
Does this help?
It helps but it is not enough:
...
GuiView.C:83:
On Tue, Oct 31, 2006 at 03:22:34PM +, José Matos wrote:
> On Tuesday 31 October 2006 2:43 pm, John Levon wrote:
> > On Tue, Oct 31, 2006 at 03:42:32PM +0100, Peter Kümmel wrote:
> > > I've just enabled it.
> >
> > Nice :(
>
> Could you elaborate, please?
>
> The switch is simple, and we
Hi John,
sorry if I've annoyed you. At least we have now a active
discussion about it and I know the author of the code which
I've changed. ;)
As I understand it, your main reason against 'setMovable(true)'
is the the 'tearing off' (comment in the code) or the
'popping out'. But this is not
Because of this I haven't seen a reason not to enable 'movable'.
I like movable toolbars but I share JMarc's concerns about math/table
toolbars and session. I will add session/toolbar very soon and I would
appreciate it if you can show me how to get/restore toolbar position.
Bo
John Levon wrote:
That it just happened without discussion of whether it makes sense,
unlike when I disabled it, when I actually asked people?
Anyway, seems I've been overruled by the current devs, so it doesn't
really matter.
Peter, to tell the truth I am also not happy about your change
Michael Gerz wrote:
> John Levon wrote:
>
>> That it just happened without discussion of whether it makes sense,
>> unlike when I disabled it, when I actually asked people?
>>
>> Anyway, seems I've been overruled by the current devs, so it doesn't
>> really matter.
>>
>>
> Peter, to tell the
Bo Peng wrote:
>> Because of this I haven't seen a reason not to enable 'movable'.
>
> I like movable toolbars but I share JMarc's concerns about math/table
> toolbars and session. I will add session/toolbar very soon and I would
> appreciate it if you can show me how to g
Peter Kümmel wrote:
Anyway, all the toolbar stuff is a moving target so lets not argue
about it.
Yes. And I am not going to touch your code.
Michael
Michael Gerz wrote:
> Peter Kümmel wrote:
>
>> Anyway, all the toolbar stuff is a moving target so lets not argue
>> about it.
>>
>>
> Yes. And I am not going to touch your code.
Thanks, Michael, and sorry for my brutal committing.
Hope I'm now not in your ignore list. ;)
Peter
On Tuesday 31 October 2006 8:57 pm, Peter Kümmel wrote:
> Michael Gerz wrote:
> > Peter Kümmel wrote:
> >> Anyway, all the toolbar stuff is a moving target so lets not argue
> >> about it.
> >
> > Yes. And I am not going to touch your code.
>
> Thanks, Michael, and sorry for my brutal committing.
José Matos wrote:
> On Tuesday 31 October 2006 8:57 pm, Peter Kümmel wrote:
>> Michael Gerz wrote:
>>> Peter Kümmel wrote:
Anyway, all the toolbar stuff is a moving target so lets not argue
about it.
>>> Yes. And I am not going to touch your code.
>> Thanks, Michael, and sorry for my
On Tue, Oct 31, 2006 at 07:46:04PM +0100, Peter Kümmel wrote:
> As I understand it, your main reason against 'setMovable(true)'
> is the the 'tearing off' (comment in the code) or the
> 'popping out'. But this is not possible also not with my
So I discovered when I finished the build. My
On Tue, Oct 31, 2006 at 08:12:26PM +0100, Michael Gerz wrote:
> Why does the "Review" toolbar have to have the "review" flag? You can
BTW, one comment about the Review toolbar. It's very neat functionality
to have, but it's severely hampered by the lack of any icons. It's not
fun work if you're
86 matches
Mail list logo
