On Fri, Feb 22, 2008 at 09:44:47AM +0200, Martin Vermeer wrote:
> The X system should have a routine for doing that...
Yes, but that's not available on Windows.
Using QColor::setNamedColor() might be an option,
void QColor::setNamedColor ( const QString & name )
Sets the RGB valu
Martin Vermeer <[EMAIL PROTECTED]> writes:
> Sounds like a plan. And it seems that these SVG colours actually include
> the X colours.
Looks good indeed.
JMarc
On Fri, 22 Feb 2008 10:04:33 +0100
Abdelrazak Younes <[EMAIL PROTECTED]> wrote:
> Jean-Marc Lasgouttes wrote:
> > Martin Vermeer <[EMAIL PROTECTED]> writes:
> >
> >>> or we
> >>> need ColorSet::ColorSet() to include the hex values directly. Or else we
> >>> need to hardcode the hex values wher
Jean-Marc Lasgouttes wrote:
Martin Vermeer <[EMAIL PROTECTED]> writes:
or we
need ColorSet::ColorSet() to include the hex values directly. Or else we
need to hardcode the hex values where they're wanted.
Rather not. The ColorSet list should be able to contain official X11 names
at that posit
Martin Vermeer <[EMAIL PROTECTED]> writes:
>> or we
>> need ColorSet::ColorSet() to include the hex values directly. Or else we
>> need to hardcode the hex values where they're wanted.
>
> Rather not. The ColorSet list should be able to contain official X11 names
> at that position.
I am not
On Thu, 21 Feb 2008 14:49:12 -0500
rgheck <[EMAIL PROTECTED]> wrote:
> Abdelrazak Younes wrote:
> > Richard Heck wrote:
> >> Richard Heck wrote:
> >>> José Matos wrote:
> After Richard fix I get an assertion.
>
>
> >>> The problem is that lcolor.getX11Name(Color_shadedbg), on
>
rgheck wrote:
Jean-Marc Lasgouttes wrote:
Andre Poenitz
<[EMAIL PROTECTED]>
writes:
I personally don't have a problem with hex numbers for colors. But I
have no strong opinion on the whole subject.
That would not be a bad solution.
Is there some easy way to tell in svn who put th
Jean-Marc Lasgouttes wrote:
Andre Poenitz <[EMAIL PROTECTED]> writes:
I personally don't have a problem with hex numbers for colors. But I
have no strong opinion on the whole subject.
That would not be a bad solution.
Is there some easy way to tell in svn who put this code there?
Andre Poenitz <[EMAIL PROTECTED]> writes:
> I personally don't have a problem with hex numbers for colors. But I
> have no strong opinion on the whole subject.
That would not be a bad solution.
JMarc
On Thu, Feb 21, 2008 at 02:49:12PM -0500, rgheck wrote:
> Abdelrazak Younes wrote:
>> Richard Heck wrote:
>>> Richard Heck wrote:
José Matos wrote:
> After Richard fix I get an assertion.
>
>
The problem is that lcolor.getX11Name(Color_shadedbg), on LaTeXFeatures
line
Abdelrazak Younes wrote:
Richard Heck wrote:
Richard Heck wrote:
José Matos wrote:
After Richard fix I get an assertion.
The problem is that lcolor.getX11Name(Color_shadedbg), on
LaTeXFeatures line 636, is returning "red". I'll look to see why
this is, but maybe someone else knows?
Th
Richard Heck wrote:
Richard Heck wrote:
José Matos wrote:
After Richard fix I get an assertion.
The problem is that lcolor.getX11Name(Color_shadedbg), on
LaTeXFeatures line 636, is returning "red". I'll look to see why this
is, but maybe someone else knows?
This just looks like bad cod
Richard Heck wrote:
José Matos wrote:
After Richard fix I get an assertion.
The problem is that lcolor.getX11Name(Color_shadedbg), on
LaTeXFeatures line 636, is returning "red". I'll look to see why this
is, but maybe someone else knows?
This just looks like bad code:
LaTeXFeatures.c
José Matos wrote:
After Richard fix I get an assertion.
The problem is that lcolor.getX11Name(Color_shadedbg), on LaTeXFeatures
line 636, is returning "red". I'll look to see why this is, but maybe
someone else knows?
rh
After Richard fix I get an assertion.
Assertion triggered in lyx::RGBColor lyx::rgbFromHexName(const std::string&)
by failing check "x11hexname.size() == 7 && x11hexname[0] == '#'" infile
Color.cpp:80
Program received signal SIGABRT, Aborted.
[Switching to Thread 0xb7fd3940 (LWP 9744)]
0x001104
15 matches
Mail list logo
