Bernhard == Bernhard Roider [EMAIL PROTECTED] writes:
Bernhard The math background color is not used at all.
Yes, this has been true for some time.
JMarc
Jean-Marc Lasgouttes wrote:
Bernhard == Bernhard Roider [EMAIL PROTECTED] writes:
Bernhard The math background color is not used at all.
Yes, this has been true for some time.
I think this has always been the case but it is fixable now: math insets
do now have the backgroundColor(), it
> "Bernhard" == Bernhard Roider <[EMAIL PROTECTED]> writes:
Bernhard> The math background color is not used at all.
Yes, this has been true for some time.
JMarc
Jean-Marc Lasgouttes wrote:
"Bernhard" == Bernhard Roider <[EMAIL PROTECTED]> writes:
Bernhard> The math background color is not used at all.
Yes, this has been true for some time.
I think this has always been the case but it is fixable now: math insets
do now have the backgroundColor(),
Hello all,
found some time for lyx today... and some bugs in the colors dialog. The
attached patch fixes
1. a crash when no color is selected and the alter button is pressed
2. when canceling the color selection dialog the color of the selected item is
changed to black
3. when canceling the
Another issue on Windows:
At work i installed beta2 with interface language german and everything
is german except for the color selection dialog. At home when starting
LyX from MSVC the interface language is english except for the color
selection dialog which is in german!
Yet another
Hello all,
found some time for lyx today... and some bugs in the colors dialog. The
attached patch fixes
1. a crash when no color is selected and the "alter" button is pressed
2. when canceling the color selection dialog the color of the selected item is
changed to black
3. when canceling the
Another issue on Windows:
At work i installed beta2 with interface language german and everything
is german except for the color selection dialog. At home when starting
LyX from MSVC the interface language is english except for the color
selection dialog which is in german!
Yet another
On Thu, Feb 22, 2001 at 12:41:28AM +1000, Allan Rae wrote:
On Wed, 13 Dec 2000, Amir Karger wrote:
On Tue, Dec 12, 2000 at 03:44:46PM +1000, Allan Rae wrote:
On Sat, 2 Dec 2000, Angus Leeming wrote:
P.S. We should probably try to lower the nested tabfolder so that it might
be
On Wed, 13 Dec 2000, Amir Karger wrote:
On Tue, Dec 12, 2000 at 03:44:46PM +1000, Allan Rae wrote:
On Sat, 2 Dec 2000, Angus Leeming wrote:
P.S. We should probably try to lower the nested tabfolder so that it might
be more obvious that they in fact tabbed rather than MS-style
On Thu, Feb 22, 2001 at 12:41:28AM +1000, Allan Rae wrote:
> On Wed, 13 Dec 2000, Amir Karger wrote:
>
> > On Tue, Dec 12, 2000 at 03:44:46PM +1000, Allan Rae wrote:
> > > On Sat, 2 Dec 2000, Angus Leeming wrote:
> > >
> > > P.S. We should probably try to lower the nested tabfolder so that it
On Wed, 13 Dec 2000, Amir Karger wrote:
> On Tue, Dec 12, 2000 at 03:44:46PM +1000, Allan Rae wrote:
> > On Sat, 2 Dec 2000, Angus Leeming wrote:
> >
> > P.S. We should probably try to lower the nested tabfolder so that it might
> > be more obvious that they in fact tabbed rather than MS-style
On Tue, Dec 12, 2000 at 03:44:46PM +1000, Allan Rae wrote:
On Sat, 2 Dec 2000, Angus Leeming wrote:
P.S. We should probably try to lower the nested tabfolder so that it might
be more obvious that they in fact tabbed rather than MS-style multi-rowed
folders. Maybe lowering a few pixels and
On Tue, Dec 12, 2000 at 03:44:46PM +1000, Allan Rae wrote:
> On Sat, 2 Dec 2000, Angus Leeming wrote:
>
> P.S. We should probably try to lower the nested tabfolder so that it might
> be more obvious that they in fact tabbed rather than MS-style multi-rowed
> folders. Maybe lowering a few pixels
On Sat, 2 Dec 2000, Angus Leeming wrote:
On Friday 01 December 2000 15:03, Duncan Simpson wrote:
use anyway---a place to tpye a colour name is good for me (and helps me
find a decent gold in any case).
Well, I've just added RGB sliders too. That should help.
Angus, you know how you
On Sat, 2 Dec 2000, Angus Leeming wrote:
> On Friday 01 December 2000 15:03, Duncan Simpson wrote:
> > use anyway---a place to tpye a colour name is good for me (and helps me
> > find a decent gold in any case).
>
> Well, I've just added RGB sliders too. That should help.
Angus, you know how
"Angus" == Angus Leeming [EMAIL PROTECTED] writes:
Angus I appear to have corrupted my repository somehow. I can do a
Angus "cvs diff" from src/frontends/xforms but not from the root
Angus Here, then, is the patch. Note that it was created from within
Angus src/frontends/xforms, so should be
Angus I appear to have corrupted my repository somehow. I can do a
Angus "cvs diff" from src/frontends/xforms but not from the root
Angus Here, then, is the patch. Note that it was created from within
Angus src/frontends/xforms, so should be applied from there. The
Angus ChangeLog should
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> I appear to have corrupted my repository somehow. I can do a
Angus> "cvs diff" from src/frontends/xforms but not from the root
Angus> Here, then, is the patch. Note that it was created from within
Angus> src/frontends/xforms, so
> Angus> I appear to have corrupted my repository somehow. I can do a
> Angus> "cvs diff" from src/frontends/xforms but not from the root
> Angus> Here, then, is the patch. Note that it was created from within
> Angus> src/frontends/xforms, so should be applied from there. The
> Angus> ChangeLog
On Friday 01 December 2000 15:03, Duncan Simpson wrote:
If the code quoted is typical then it could all be replaced by
XlookupColorn which returns the closest and exact colour
'Fraid not. X11 uses short ints r,g,b in the range 0 r,g,b 63000ish
Xforms uses chars in the range 0 r,g,b 255
My
On Friday 01 December 2000 15:03, Duncan Simpson wrote:
> If the code quoted is typical then it could all be replaced by
> XlookupColorn which returns the closest and exact colour
'Fraid not. X11 uses short ints r,g,b in the range 0 < r,g,b < 63000ish
Xforms uses chars in the range 0 < r,g,b <
Many thanks, Ducan and Jean-Marc, about the X11 name info.
Using the following in FormPreferences::Colors::apply() to apply changes to
the LColors works like a dream. This leaves the way clear to ditch the
problematic X11 namebase browser in the colors tab and allow users to choose
any color
I appear to have corrupted my repository somehow. I can do a "cvs diff" from
src/frontends/xforms but not from the root directory:
aleem@pneumon:devel- cvs update
[EMAIL PROTECTED]'s password:
Received disconnect: Corrupted check bytes on input.
cvs [update aborted]: received broken pipe signal
On Fri, 1 Dec 2000, Angus Leeming wrote:
I appear to have corrupted my repository somehow. I can do a "cvs diff" from
src/frontends/xforms but not from the root directory:
aleem@pneumon:devel- cvs update
[EMAIL PROTECTED]'s password:
Received disconnect: Corrupted check bytes on input.
If the code quoted is typical then it could all be replaced by XlookupColorn
which returns the closest and exact colour
XLookupColor(dipslay, colour map, colorname, exact_ef_retrurn,
scrren_def_retrun)
Returns: 0 on mailure, non zero on success .Possible errors are BadName
(invalid colour)
Many thanks, Ducan and Jean-Marc, about the X11 name info.
Using the following in FormPreferences::Colors::apply() to apply changes to
the LColors works like a dream. This leaves the way clear to ditch the
problematic X11 namebase browser in the colors tab and allow users to choose
any color
I appear to have corrupted my repository somehow. I can do a "cvs diff" from
src/frontends/xforms but not from the root directory:
aleem@pneumon:devel-> cvs update
[EMAIL PROTECTED]'s password:
Received disconnect: Corrupted check bytes on input.
cvs [update aborted]: received broken pipe
On Fri, 1 Dec 2000, Angus Leeming wrote:
> I appear to have corrupted my repository somehow. I can do a "cvs diff" from
> src/frontends/xforms but not from the root directory:
>
> aleem@pneumon:devel-> cvs update
> [EMAIL PROTECTED]'s password:
> Received disconnect: Corrupted check bytes on
If the code quoted is typical then it could all be replaced by XlookupColorn
which returns the closest and exact colour
XLookupColor(dipslay, colour map, colorname, exact_ef_retrurn,
scrren_def_retrun)
Returns: 0 on mailure, non zero on success .Possible errors are BadName
(invalid colour)
On Thursday 30 November 2000 02:34, Allan Rae wrote:
Consider TF Message Read.
Sorry. I got a bit overexcited.
When your cursor goes over amy object in FormPreferences you get a little
bit of text. Read it. Act upon it!
You already set the X11 name by some search method. Why not set the
"Angus" == Angus Leeming [EMAIL PROTECTED] writes:
Angus The ONLY reason we have the X11 name browser is because LColor
Angus currently stores colours by name, not by RGB value. This will
Angus have to change in the future if we're to have a native windows
Angus port etc, but, for the time
The problem is that LyXColorHandler::getGCForeground() uses
XLookupColor(display, colormap, x11colorname, xcol, ccol);
to find xcol and ccol, the "exact" and "closest available on this display"
RGB colours to the input x11colorname. Till this changes LColor has to store
the X11 name.
"Angus" == Angus Leeming [EMAIL PROTECTED] writes:
Angus The problem is that LyXColorHandler::getGCForeground() uses
Angus XLookupColor(display, colormap, x11colorname, xcol, ccol);
Angus to find xcol and ccol, the "exact" and "closest available on
Angus this display" RGB colours to the input
Thanks for the info. I'll leave things as they are for 1.1.6 but thereafter
will have a play.
A
On Thursday 30 November 2000 10:27, Jean-Marc Lasgouttes wrote:
"Angus" == Angus Leeming [EMAIL PROTECTED] writes:
Angus The problem is that LyXColorHandler::getGCForeground() uses
Angus
To paraphrase from Vchapter 7 of Xlib programming (page 193) it says
Whe XAllocNamedColor, XlookupColor, XparseColor and XStoreNamedColor (or their
device indepent analogues) and pased a colour string thyey attempt the
following thins (and take the first that works)
1. Attempt to parse is as
On Thursday 30 November 2000 02:34, Allan Rae wrote:
> Consider TF Message Read.
Sorry. I got a bit overexcited.
> > When your cursor goes over amy object in FormPreferences you get a little
> > bit of text. Read it. Act upon it!
> You already set the X11 name by some search method. Why not set
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> The ONLY reason we have the X11 name browser is because LColor
Angus> currently stores colours by name, not by RGB value. This will
Angus> have to change in the future if we're to have a native windows
Angus> port etc, but, for
The problem is that LyXColorHandler::getGCForeground() uses
XLookupColor(display, colormap, x11colorname, , );
to find xcol and ccol, the "exact" and "closest available on this display"
RGB colours to the input x11colorname. Till this changes LColor has to store
the X11 name. Unless
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> The problem is that LyXColorHandler::getGCForeground() uses
Angus> XLookupColor(display, colormap, x11colorname, , );
Angus> to find xcol and ccol, the "exact" and "closest available on
Angus> this display" RGB colours to the
Thanks for the info. I'll leave things as they are for 1.1.6 but thereafter
will have a play.
A
On Thursday 30 November 2000 10:27, Jean-Marc Lasgouttes wrote:
> > "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
>
> Angus> The problem is that LyXColorHandler::getGCForeground() uses
>
To paraphrase from Vchapter 7 of Xlib programming (page 193) it says
Whe XAllocNamedColor, XlookupColor, XparseColor and XStoreNamedColor (or their
device indepent analogues) and pased a colour string thyey attempt the
following thins (and take the first that works)
1. Attempt to parse is as
On Tue, 28 Nov 2000, Angus Leeming wrote:
On Tuesday 28 November 2000 07:17, Allan Rae wrote:
1. In English, colours is spelled colours ;-)
And everywhere else in LyX it's spelled colors. I simply acknowledged the
de-facto colonization of the english-speaking world by that imperialist
On Tue, 28 Nov 2000, Angus Leeming wrote:
> On Tuesday 28 November 2000 07:17, Allan Rae wrote:
> > 1. In English, colours is spelled colours ;-)
>
> And everywhere else in LyX it's spelled colors. I simply acknowledged the
> de-facto colonization of the english-speaking world by that
1. In English, colours is spelled colours ;-)
2. It doesn't work. I took a quick look at the input processing in
Colors::input() et al and it seems that the Modify button is disabled
almost everywhere unless V=0 or 1 and S=0.
Hopefully you are already aware of this, Angus,
1. In English, colours is spelled colours ;-)
2. It doesn't work. I took a quick look at the input processing in
Colors::input() et al and it seems that the Modify button is disabled
almost everywhere unless V=0 or 1 and S=0.
Hopefully you are already aware of this, Angus,
46 matches
Mail list logo
