On Thu, Dec 07, 2006 at 04:34:45PM +0100, Enrico Forestieri wrote:
> On Thu, Dec 07, 2006 at 12:39:36PM +0100, Georg Baum wrote:
> > Am Dienstag, 5. Dezember 2006 23:20 schrieb Enrico Forestieri:
>
> > > I think this is what the Qt QString::toLocal8Bit() does.
> >
> > Yes, I think so, too. I wond
Am Donnerstag, 7. Dezember 2006 16:34 schrieb Enrico Forestieri:
> On Thu, Dec 07, 2006 at 12:39:36PM +0100, Georg Baum wrote:
> > Yes, I think so, too. I wonder what the difference to
QFile::encodeName()
> > is?
>
> I think they perform the same task, except that you can use encodeName()
> dire
On Thu, Dec 07, 2006 at 12:39:36PM +0100, Georg Baum wrote:
> Am Dienstag, 5. Dezember 2006 23:20 schrieb Enrico Forestieri:
> > I think this is what the Qt QString::toLocal8Bit() does.
>
> Yes, I think so, too. I wonder what the difference to QFile::encodeName()
> is?
I think they perform the
Am Dienstag, 5. Dezember 2006 23:20 schrieb Enrico Forestieri:
> On Tue, Dec 05, 2006 at 09:41:15PM +0100, Georg Baum wrote:
> > Am Dienstag, 5. Dezember 2006 19:03 schrieb Enrico Forestieri:
> >
> > > I can only speak for Cygwin. I don't know for Windows in general, but
> > > I think that it is a
On Thu, Dec 07, 2006 at 04:58:28PM +, Bo Peng wrote:
> >> ... the button will go "dead" and not respond to
> >> mouse-over anymore. And you see that _only_ the paragraph the text
> >> cursor is in, gets repainted.
> >
> >Good catch. I will have a look.
>
> This is fixed now. ...
Confirmed, t
> ... the button will go "dead" and not respond to
> mouse-over anymore. And you see that _only_ the paragraph the text
> cursor is in, gets repainted.
Good catch. I will have a look.
This is fixed now. I also made the buttonframe the same color as
button background since these two colors do n
Normally when you move the mouse over the button, it will change colour
when moving in / moving out, as intended. At the same time you see
(debug output) how every visible paragraph is repainted.
I intended to use single-paragraph repaint, but this was proved
impossible right now. A lots of repa
Trying out the new button look, I run into the following bug:
Normally when you move the mouse over the button, it will change colour
when moving in / moving out, as intended. At the same time you see
(debug output) how every visible paragraph is repainted.
However, if you do the following: 1) g
Michael Gerz wrote:
Edwin Leuven schrieb:
Georg Baum wrote:
Am Dienstag, 5. Dezember 2006 21:57 schrieb Edwin Leuven:
thanks, the attached solves the crash. is this the correct way to do
it?
Almost. It should be done as early as possible, in this case in
src/support/getcwd.C.
like this?
Edwin Leuven schrieb:
Georg Baum wrote:
Am Dienstag, 5. Dezember 2006 21:57 schrieb Edwin Leuven:
thanks, the attached solves the crash. is this the correct way to do
it?
Almost. It should be done as early as possible, in this case in
src/support/getcwd.C.
like this?
The patch looks reaso
On Tue, Dec 05, 2006 at 09:41:15PM +0100, Georg Baum wrote:
> Am Dienstag, 5. Dezember 2006 19:03 schrieb Enrico Forestieri:
>
> > I can only speak for Cygwin. I don't know for Windows in general, but
> > I think that it is also dependent on the filesystem (FAT32 or NTFS).
>
> I had the hope that
Edwin Leuven wrote:
Index: getcwd.C
===
using boost::scoped_array;
+using os::support::internal_path;
should be
> +using support::os::internal_path;
Georg Baum wrote:
Am Dienstag, 5. Dezember 2006 21:57 schrieb Edwin Leuven:
thanks, the attached solves the crash. is this the correct way to do it?
Almost. It should be done as early as possible, in this case in
src/support/getcwd.C.
like this?
Index: getcwd.C
Am Dienstag, 5. Dezember 2006 21:57 schrieb Edwin Leuven:
> thanks, the attached solves the crash. is this the correct way to do it?
Almost. It should be done as early as possible, in this case in
src/support/getcwd.C.
Georg
Georg Baum wrote:
for example when i inset a citation
lyx: Disabling LyX socket.
Assertion triggered in __thiscall lyx::support::FileName::FileName(const
class s
td::basic_string,class
std::allocator >
&) by failing check "!contains(name_, '\\')" in file
..\..\..\..\src\support\fi
lename.C
Georg Baum wrote:
Am Dienstag, 5. Dezember 2006 18:31 schrieb Edwin Leuven:
georg is picking on me
I am sorry if you read it like that and apologize. My intention was
not to pick on you, but to point at some general tendency.
sure, i share your concern that we need to get 1.5 out of the doo
Am Dienstag, 5. Dezember 2006 19:03 schrieb Enrico Forestieri:
> I can only speak for Cygwin. I don't know for Windows in general, but
> I think that it is also dependent on the filesystem (FAT32 or NTFS).
I had the hope that it was better as on linux, but if this is true it seems
to be even wor
Am Dienstag, 5. Dezember 2006 17:25 schrieb Edwin Leuven:
> sorry, i don't know about this unicode stuff and i intend to keep it
> that way (or am i not allowed to say that?). you don't want the butcher
> to make your bread.
Sure you are allowed. This was just an example for a problem that needs
Am Dienstag, 5. Dezember 2006 18:31 schrieb Edwin Leuven:
> georg is picking on me
I am sorry if you read it like that and apologize. My intention was not to
pick on you, but to point at some general tendency.
> i eat mathematicians for breakfast ;-)
I am glad that I am not a mathematician :-
Am Dienstag, 5. Dezember 2006 18:02 schrieb Jean-Marc Lasgouttes:
> > "Edwin" == Edwin Leuven <[EMAIL PROTECTED]> writes:
>
> Edwin> Georg Baum wrote:
> >>> life after 1.5 ?
> >> Then I'd suggest to start working on that after 1.5.
>
> Edwin> unfortunately you're not my boss...
>
> Gentleme
José Matos wrote:
On Tuesday 05 December 2006 5:31 pm, Edwin Leuven wrote:
PS: of course, in such a case, I'll side with Georg :)
i eat mathematicians for breakfast ;-)
That remembers me when some time ago my students (second year
Economics) told me that all mathematicians are dead by now. :-
On Tue, Dec 05, 2006 at 07:03:09PM +0100, Enrico Forestieri wrote:
> For example, this is what I get when running
> the attached test program:
>
> $ env LC_ALL=it_IT.ISO8859-1 ./test-wctype
> towupper(0xe8) = 0xe8
> toupper(0xe8) = 0xc8
>
> $ env LC_ALL=it_IT.UTF-8 ./test-wctype
> towupper(0xe8)
On Tue, Dec 05, 2006 at 05:11:38PM +0100, Georg Baum wrote:
> And I have something for the windows users: One of the next steps in making
> non-ascii filenames work will be to actually implement
> FileName::toFilesystemEncoding(). I know what to do on linux, but not on
> windows, so it would be ni
Sure, I am using
\set_color "buttonbg" "#dcd2c8"
This color makes the buttons a lot easier to locate, and is less
eye-catching than the orignal buttons. Because there is no way to
reach a consensus, I have made this the default.
Bo
On Tuesday 05 December 2006 5:31 pm, Edwin Leuven wrote:
> > PS: of course, in such a case, I'll side with Georg :)
>
> i eat mathematicians for breakfast ;-)
That remembers me when some time ago my students (second year Economics)
told me that all mathematicians are dead by now. :-D
Since w
On Wed, Dec 06, 2006 at 09:11:04AM +1800, Bo Peng wrote:
> Enrico and others: I understand that you've got used to prominent
> buttons. Please make proper adjustments and be done with this feature.
> I will accept anything but the original fake-3D buttons.
I explained what my only concern was, an
Jean-Marc Lasgouttes wrote:
"Edwin" == Edwin Leuven <[EMAIL PROTECTED]> writes:
Edwin> Georg Baum wrote:
life after 1.5 ?
Then I'd suggest to start working on that after 1.5.
Edwin> unfortunately you're not my boss...
Gentlemen, are we trying to set up a fight of some sort?
georg is pic
On Mon, Dec 04, 2006 at 02:47:14PM -0600, Bo Peng wrote:
> >> Actually, I achieve the desired goal by making a little darker the
> >> button background ;-)
>
> If the button looks fine there, could you send me the color you use?
Sure, I am using
\set_color "buttonbg" "#dcd2c8"
--
Enrico
> "Edwin" == Edwin Leuven <[EMAIL PROTECTED]> writes:
Edwin> Georg Baum wrote:
>>> life after 1.5 ?
>> Then I'd suggest to start working on that after 1.5.
Edwin> unfortunately you're not my boss...
Gentlemen, are we trying to set up a fight of some sort?
Is it really the time to do so?
J
Georg Baum wrote:
life after 1.5 ?
Then I'd suggest to start working on that after 1.5.
unfortunately you're not my boss...
My experience is
that it takes too much time to keep half finished patches in a
working state.
sure
i think everybody is waiting for alpha2 (with binaries) to get
Leuven, E. wrote:
>> edwin leuven wrote:
>>
>> fyi, i am not proposing to put the tabular stuff in. so i don't see why i
>> couldn't tinker a bit with that...
>>
>>Of course you can, but if you don't want to put it in what is the purpose
>> on working on it?
>
> life after 1.5 ?
Then I'd suggest
On Tuesday 05 December 2006 3:11 pm, Bo Peng wrote:
>
> OK, let us wrap this up.
>
> Jose: I apologize for bringing this patch up. Next time, you can stop
> me at my 'pre-patch' (, although there is unlikely a next time).
Good. That is fair and I appreciate you attitude.
> Enrico and others: I
oh, and perhaps someone should go over status.15x again to check which bugs are
still around
I did that yesterday night and found most of them qt-related.
Unfortunately, a qt-novice like me can not fix any of them in a few
hours.
Bo
> edwin leuven wrote:
>
> fyi, i am not proposing to put the tabular stuff in. so i don't see why i
> couldn't tinker a bit with that...
>
>Of course you can, but if you don't want to put it in what is the purpose
> on working on it?
life after 1.5 ?
> It is a fact that such work does delay the r
Of course you can, but if you don't want to put it in what is the
purpose on working on it?
Exactly. I made the buttons prettier when I tried to understand the
mouse/event handling of qt/lyx, and I could not help showing it off,
despite my clear awareness of the feature freeze. And you see what
edwin leuven wrote:
> fyi, i am not proposing to put the tabular stuff in. so i don't see why i
> couldn't tinker a bit with that...
Of course you can, but if you don't want to put it in what is the purpose on
working on it?
It is a fact that such work does delay the relase of 1.5.0. Maybe not
ev
Georg Baum <[EMAIL PROTECTED]> writes:
>
> Edwin Leuven wrote:
>
> > and am playing a bit with the tabular code (merging tabular.h and
> > insettabular) so have no time to figure out how to do this... :-/
>
> That ... means that the freeze is over and 1.5.0 will
> never happen. I agree that tabul
Edwin Leuven wrote:
> and am playing a bit with the tabular code (merging tabular.h and
> insettabular) so have no time to figure out how to do this... :-/
That (and the button stuff) means that the freeze is over and 1.5.0 will
never happen. I agree that tabular and insettabular need to be merge
Edwin Leuven wrote:
> instead of a border i'd like enclosing '<' '>'
That'd go too far for my taste. I'd like the insets to be clearly
distinguished from the main text (and another font/color is not enough for my
taste). Bo's approach is already close to the limits, but I think I might get
use
I think you should have waited for Jose's "OK". After all, we are in a feature
freeze (or at least I thought we are).
Jose was not oppose to the patch and his concerns were mostly
addressed. Committing the patch made testing a lot easier, and I was
ready to improve or reverse the patch.
Anyway
Bo Peng wrote:
http://www.lyx.org>
We are actually quite close to these. The buttons, with a background
identical to text background, look like regular text. And we can tweak
individual insets to what it displays.
>
> If you are unhappy about the label of a certain inset, we can discuss
>
http://www.lyx.org>
We are actually quite close to these. The buttons, with a background
identical to text background, look like regular text. And we can tweak
individual insets to what it displays.
If you are unhappy about the label of a certain inset, we can discuss
and change it.
Cheer
Bo Peng schrieb:
> Actually, I achieve the desired goal by making a little darker the
> button background ;-)
If the button looks fine there, could you send me the color you use?
BTW: Would it be too demanding if I ask for rounded boxes?
It should not be too difficult. You can try to do tha
> Actually, I achieve the desired goal by making a little darker the
> button background ;-)
If the button looks fine there, could you send me the color you use?
BTW: Would it be too demanding if I ask for rounded boxes?
It should not be too difficult. You can try to do that in painter.C,
an
Enrico Forestieri schrieb:
On Mon, Dec 04, 2006 at 12:10:29PM -0600, Bo Peng wrote:
But anyway, the colors are configurable...
Ok, I'll try that.
I guess thicker frame plus a more prominent frame color (purple?) will
fit your need? I am open to such changes to make these bu
On Mon, Dec 04, 2006 at 12:10:29PM -0600, Bo Peng wrote:
> > > But anyway, the colors are configurable...
> >
> > Ok, I'll try that.
>
> I guess thicker frame plus a more prominent frame color (purple?) will
> fit your need? I am open to such changes to make these buttons appeal
> to 80% of the u
i always thought these buttons were really ugly anyway. what i would
like is something like (instead of a button) :
http://www.lyx.org>
etc. and then in the sans font in a different color...
(and perhaps when you hover them they get underlined and the cursor
shape changes)
Bo Peng w
> But anyway, the colors are configurable...
Ok, I'll try that.
I guess thicker frame plus a more prominent frame color (purple?) will
fit your need? I am open to such changes to make these buttons appeal
to 80% of the users (if we are at 50% now, and 100% is not possible).
Bo
On Tue, Dec 05, 2006 at 11:18:09AM +1800, Bo Peng wrote:
> > Bo, I don't like this new look.
>
> I know it is hard to reach a consensus, but these insets (reference,
> footnotes etc) contain auxiliary information, and should not catch
> more attention than the main text. Also, as I have explained
Bo, I don't like this new look.
I know it is hard to reach a consensus, but these insets (reference,
footnotes etc) contain auxiliary information, and should not catch
more attention than the main text. Also, as I have explained, buttons
in a lyx document are not like buttons in a html page. In
Bo, I don't like this new look. I like to be able to easily locate
all the insets and now this is not possible anymore.
The only thing you need to do is change \buttonbg to some other darker
color, from the preference dialog. This color is currently set to text
background color. It is also possi
On Sun, Dec 03, 2006 at 10:37:08PM -0600, Bo Peng wrote:
> An updated patch has just been submitted. Enjoy!
Bo, I don't like this new look. I like to be able to easily locate
all the insets and now this is not possible anymore. I think that
this is one of those features loved by half of the peopl
Bo Peng wrote:
> An updated patch has just been submitted. Enjoy!
I think you should have waited for Jose's "OK". After all, we are in a feature
freeze (or at least I thought we are).
Anyway, the compiler complains about an unused parameter mouse_hover in
insetbase.h:185. Can you get rid of tha
On Mon, Dec 04, 2006 at 12:20:03AM -0500, [EMAIL PROTECTED] wrote:
> On Sun, 3 Dec 2006 22:37:08 -0600
> "Bo Peng" <[EMAIL PROTECTED]> wrote:
> >An updated patch has just been submitted. Enjoy!
> >
> >Bennett: if this patch poses a severe performance
> >problem for mac, I
> >will disable mouse-tr
On Sun, 3 Dec 2006 22:37:08 -0600
"Bo Peng" <[EMAIL PROTECTED]> wrote:
An updated patch has just been submitted. Enjoy!
Bennett: if this patch poses a severe performance
problem for mac, I
will disable mouse-tracking for mac.
I'm not sure what would constitute a severe performance
problem
An updated patch has just been submitted. Enjoy!
Bennett: if this patch poses a severe performance problem for mac, I
will disable mouse-tracking for mac.
How about setMouseHover? setMouseIn(false) sounds funny.
setMouseHover is used.
> 4) The toggling does not work for opened insets, only
Bo Peng wrote:
I don't think this will happen in 1.5 so, as I am sure there would be a
problem with Mac, I'd say that you should either make this new feature
configurable or disabled on Mac.
I still think the number of repaints would be small.
The thing is that the user will 'feel' a resistan
Bo Peng wrote:
Well, in practice, this is the same as most insets are 'clickable'.
'clickable' is a wrong word. The repaint should only happen for
collapsable insets (like footnote) and commands (like toc).
OK, make that a 'button' inset then.
They are
relatively rare compared to text and m
I don't think this will happen in 1.5 so, as I am sure there would be a
problem with Mac, I'd say that you should either make this new feature
configurable or disabled on Mac.
I still think the number of repaints would be small. Let us see what
Bennet's test result is.
.
Bo
Well, in practice, this is the same as most insets are 'clickable'.
'clickable' is a wrong word. The repaint should only happen for
collapsable insets (like footnote) and commands (like toc). They are
relatively rare compared to text and mathed. Also, moving inside an
inset should not trigger an
Martin Vermeer wrote:
On Sun, Dec 03, 2006 at 12:17:59PM +, José Matos wrote:
On Sunday 03 December 2006 11:57 am, Martin Vermeer wrote:
If it really causes a full screen repaint when just moving the mouse
over an inset, it may well be intrusive on the Mac.
I agree with Martin, I am worri
Bo Peng wrote:
2) The cursor needs to be changed into an arrow when over a button.
This is surprisingly difficult and I have not figures out an
non-intrusive way to do this. Since Abdel knows more about cursor
shape, maybe you can help?
Not in the coming weeks I'm afraid...
4) The toggli
Martin Vermeer wrote:
On Sun, Dec 03, 2006 at 12:17:59PM +, José Matos wrote:
On Sunday 03 December 2006 11:57 am, Martin Vermeer wrote:
If it really causes a full screen repaint when just moving the mouse
over an inset, it may well be intrusive on the Mac.
I agree with Martin, I am worri
On Sun, Dec 03, 2006 at 08:39:55AM -0600, Bo Peng wrote:
...
> >If it really causes a full screen repaint when just moving the mouse
> >over an i
>
> Not really. The repaint happens only when the mouse enters and leaves
> an inset *that handles setMouseHover*. The repaint is necessary since
> i
On Sun, Dec 03, 2006 at 12:17:59PM +, José Matos wrote:
> On Sunday 03 December 2006 11:57 am, Martin Vermeer wrote:
> > If it really causes a full screen repaint when just moving the mouse
> > over an inset, it may well be intrusive on the Mac.
>
> I agree with Martin, I am worried with the
IIUC, this is not a signal but a call to process some mouse event so
'dispatchMouseEntered()' or 'processMouseEntered()' or even
mouseEnteredEvent() all seem more meaningful to me.
I will combine the two functions as suggested.
> +bool InsetCollapsable::notifyMouseEnter()
> +bool InsetCollapsa
On Sunday 03 December 2006 11:57 am, Martin Vermeer wrote:
> If it really causes a full screen repaint when just moving the mouse
> over an inset, it may well be intrusive on the Mac.
I agree with Martin, I am worried with the possible implications for Mac. I
would like to see this issue cleare
On Sun, Dec 03, 2006 at 12:51:31PM +0100, Michael Gerz wrote:
> Bo Peng schrieb:
> >Dear all,
> >
> >The attached patch will be applied tomorrow morning if there is no
> >objection. The main design ideas are that
> >1. enable mouse tracking
> >2. get inset under mouse (done by editXY) and pass noti
Bo Peng schrieb:
Dear all,
The attached patch will be applied tomorrow morning if there is no
objection. The main design ideas are that
1. enable mouse tracking
2. get inset under mouse (done by editXY) and pass notifyMouseEnter
and notifyMouseLeave to it.
3. if an inset (currently insetcommand
Abdelrazak Younes wrote:
Bo Peng wrote:
Dear all,
The attached patch will be applied tomorrow morning if there is no
objection. The main design ideas are that
1. enable mouse tracking
2. get inset under mouse (done by editXY) and pass notifyMouseEnter
and notifyMouseLeave to it.
3. if an inset
Abdelrazak Younes wrote:
Abdelrazak Younes wrote:
I've tried it and I like it. Some colors needs adjustment though
(Yellow 'Note' text is not very visible without the grey background).
More importantly there's three problems:
1) The cursor blinking is stopped when the mouse is moved. This is
Abdelrazak Younes wrote:
2) The cursor needs to be changed into an arrow when over a button.
maybe a pointing hand cursor?
Abdelrazak Younes wrote:
I've tried it and I like it. Some colors needs adjustment though (Yellow
'Note' text is not very visible without the grey background).
More importantly there's three problems:
1) The cursor blinking is stopped when the mouse is moved. This is done
in WorkArea::dispatch
Bo Peng wrote:
Dear all,
The attached patch will be applied tomorrow morning if there is no
objection. The main design ideas are that
1. enable mouse tracking
2. get inset under mouse (done by editXY) and pass notifyMouseEnter
and notifyMouseLeave to it.
3. if an inset (currently insetcommand an
Bo Peng wrote:
Dear all,
The attached patch will be applied tomorrow morning if there is no
objection. The main design ideas are that
1. enable mouse tracking
2. get inset under mouse (done by editXY) and pass notifyMouseEnter
and notifyMouseLeave to it.
IIUC, this is not a signal but a call t
Dear all,
The attached patch will be applied tomorrow morning if there is no
objection. The main design ideas are that
1. enable mouse tracking
2. get inset under mouse (done by editXY) and pass notifyMouseEnter
and notifyMouseLeave to it.
3. if an inset (currently insetcommand and insetcollapsab
76 matches
Mail list logo
