I've tracked down the reason why I can't use:
string const arg = lcolor.getLyXName(lc) + string(" black");
LyXFunC::Dispatch(LFUN_SET_COLOR, arg);
when I'm editing the colors in FormPreferences and LyX has no document open.
About line 488 of Dispatch, there is the code:
"Angus" == Angus Leeming [EMAIL PROTECTED] writes:
Angus Clearly, it would be better to allow the colors to be editted
Angus without a buffer present.
This is probably an oversight. You can probably change in LyXAction.C
{ LFUN_SET_COLOR, "set-color", "", Noop },
to
Will do.
A
On Friday 17 November 2000 14:21, Jean-Marc Lasgouttes wrote:
"Angus" == Angus Leeming [EMAIL PROTECTED] writes:
Angus Clearly, it would be better to allow the colors to be editted
Angus without a buffer present.
This is probably an oversight. You can probably change in
On Wed, Nov 15, 2000 at 05:39:12PM +0100, Lars Gullik Bjønnes wrote:
Note also, that a writeable file need not yet exist but the directory
should be writeable. Allan wrote them because he wanted the feedback
for the "idiot user". I
We don't have idiot users.
But we may in the
I've tracked down the reason why I can't use:
string const arg = lcolor.getLyXName(lc) + string(" black");
LyXFunC::Dispatch(LFUN_SET_COLOR, arg);
when I'm editing the colors in FormPreferences and LyX has no document open.
About line 488 of Dispatch, there is the code:
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Clearly, it would be better to allow the colors to be editted
Angus> without a buffer present.
This is probably an oversight. You can probably change in LyXAction.C
{ LFUN_SET_COLOR, "set-color", "", Noop },
to
Will do.
A
On Friday 17 November 2000 14:21, Jean-Marc Lasgouttes wrote:
> > "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
>
> Angus> Clearly, it would be better to allow the colors to be editted
> Angus> without a buffer present.
>
> This is probably an oversight. You can probably
On Wed, Nov 15, 2000 at 05:39:12PM +0100, Lars Gullik Bjønnes wrote:
>
> > Note also, that a writeable file need not yet exist but the directory
> > should be writeable. Allan wrote them because he wanted the feedback
> > for the "idiot > user". I
>
> We don't have idiot users.
But we may in
Two patches attached.
patch1 is very small. Just a couple of tiny things.
patch2 continues the FormPreferences clean up, but
it also allows you to change the LyX LColors.
A couple of bugs remain, but I'd be grateful of some help/advice. See the
ChangeLog entry.
Finally, a useability
Angus Leeming [EMAIL PROTECTED] writes:
| browser. Not a straight alphabetical sort, but into a "rainbow" sort so that
| all names containing "red" ane grouped together, then those containing
| "orange" etc. What do people think?
Why not sort on rgb numbers? and also remove "indian red" if
"Lars" == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
Lars Why not sort on rgb numbers? and also remove "indian red" if
Lars "IndianRed" exists and have the same rgb value.
How do you know which one should be removed?
JMarc
On Wed, 15 Nov 2000, Angus Leeming wrote:
Two patches attached.
patch1 is very small. Just a couple of tiny things.
patch2 continues the FormPreferences clean up, but
it also allows you to change the LyX LColors.
A couple of bugs remain, but I'd be grateful of some help/advice.
Angus Leeming [EMAIL PROTECTED] writes:
| patch2 continues the FormPreferences clean up, but
Why do we want to have:
int IsDirWriteable (string const path);
bool IsFileReadable (string const path);
int IsFileWriteable (string const path);
_and_
(WriteableDir, ReadableDir,
good question!
Note that the new functions are more sophisticated than the old ones. In
particular, they can tell you WHY the dir/file isn't read/writeable.
Note also, that a writeable file need not yet exist but the directory should
be writeable.
Allan wrote them because he wanted the
Angus Leeming [EMAIL PROTECTED] writes:
| Note that the new functions are more sophisticated than the old ones. In
| particular, they can tell you WHY the dir/file isn't read/writeable.
I feel that this is a bit too much of hand holding. And they are not
core support functions... I'd say move
On Wednesday 15 November 2000 16:39, Lars Gullik Bjønnes wrote:
Angus Leeming [EMAIL PROTECTED] writes:
| Note that the new functions are more sophisticated than the old ones. In
| particular, they can tell you WHY the dir/file isn't read/writeable.
I feel that this is a bit too much of hand
Angus Leeming [EMAIL PROTECTED] writes:
| if( !ReadWriteInfo::ReadableFile(file) )
| std::cerr ReadWriteInfo::ErrorMessage() std::endl;
|
| I'll do this anyway and put it into xform_helpers.[Ch]. If you like it, we
| can always move it into support.
|
| Does this mean that you aren't
Two patches attached.
patch1 is very small. Just a couple of tiny things.
patch2 continues the FormPreferences clean up, but
it also allows you to change the LyX LColors.
A couple of bugs remain, but I'd be grateful of some help/advice. See the
ChangeLog entry.
Finally, a useability
Angus Leeming <[EMAIL PROTECTED]> writes:
| browser. Not a straight alphabetical sort, but into a "rainbow" sort so that
| all names containing "red" ane grouped together, then those containing
| "orange" etc. What do people think?
Why not sort on rgb numbers? and also remove "indian red" if
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> Why not sort on rgb numbers? and also remove "indian red" if
Lars> "IndianRed" exists and have the same rgb value.
How do you know which one should be removed?
JMarc
On Wed, 15 Nov 2000, Angus Leeming wrote:
> Two patches attached.
>
> patch1 is very small. Just a couple of tiny things.
>
> patch2 continues the FormPreferences clean up, but
> it also allows you to change the LyX LColors.
>
> A couple of bugs remain, but I'd be grateful of some
Angus Leeming <[EMAIL PROTECTED]> writes:
| patch2 continues the FormPreferences clean up, but
Why do we want to have:
int IsDirWriteable (string const & path);
bool IsFileReadable (string const & path);
int IsFileWriteable (string const & path);
_and_
(WriteableDir, ReadableDir,
good question!
Note that the new functions are more sophisticated than the old ones. In
particular, they can tell you WHY the dir/file isn't read/writeable.
Note also, that a writeable file need not yet exist but the directory should
be writeable.
Allan wrote them because he wanted the
Angus Leeming <[EMAIL PROTECTED]> writes:
| Note that the new functions are more sophisticated than the old ones. In
| particular, they can tell you WHY the dir/file isn't read/writeable.
I feel that this is a bit too much of hand holding. And they are not
core support functions... I'd say
On Wednesday 15 November 2000 16:39, Lars Gullik Bjønnes wrote:
> Angus Leeming <[EMAIL PROTECTED]> writes:
> | Note that the new functions are more sophisticated than the old ones. In
> | particular, they can tell you WHY the dir/file isn't read/writeable.
>
> I feel that this is a bit too much
Angus Leeming <[EMAIL PROTECTED]> writes:
| if( !ReadWriteInfo::ReadableFile(file) )
| std::cerr << ReadWriteInfo::ErrorMessage() << std::endl;
|
| I'll do this anyway and put it into xform_helpers.[Ch]. If you like it, we
| can always move it into support.
|
| Does this mean that you
"Angus" == Angus Leeming [EMAIL PROTECTED] writes:
Angus Attached is a clean-up of FormPreferences. Each tab folder is
Angus now encapsulated in its own class.
Angus The patch also activates the various "Browse" buttons, although
Angus LyXFileDlg still needs to be modified to make it
Angus
On Tuesday 14 November 2000 13:58, Jean-Marc Lasgouttes wrote:
"Angus" == Angus Leeming [EMAIL PROTECTED] writes:
Angus Attached is a clean-up of FormPreferences. Each tab folder is
Angus now encapsulated in its own class.
Angus The patch also activates the various "Browse" buttons,
"Angus" == Angus Leeming [EMAIL PROTECTED] writes:
Angus I think Lars would reply "Nada, nada, nada...", but since I've
Angus no idea what this means I'll just say, "So sue me"!
Well, "xform" is a noce name too actually :)
JMarc
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Attached is a clean-up of FormPreferences. Each tab folder is
Angus> now encapsulated in its own class.
Angus> The patch also activates the various "Browse" buttons, although
Angus> LyXFileDlg still needs to be modified to make
On Tuesday 14 November 2000 13:58, Jean-Marc Lasgouttes wrote:
> > "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
>
> Angus> Attached is a clean-up of FormPreferences. Each tab folder is
> Angus> now encapsulated in its own class.
>
> Angus> The patch also activates the various "Browse"
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> I think Lars would reply "Nada, nada, nada...", but since I've
Angus> no idea what this means I'll just say, "So sue me"!
Well, "xform" is a noce name too actually :)
JMarc
"Angus" == Angus Leeming [EMAIL PROTECTED] writes:
Angus Here is that patch.
Angus I've simply commented out FL_LIGHTER_COL1. It's not yet used
Angus anyway. If you can work out how to highlight the active folder,
Angus it won't be.
Fine. I applied the patch.
Angus The patch also adds the
Attached is a clean-up of FormPreferences. Each tab folder is now
encapsulated in its own class.
The patch also activates the various "Browse" buttons, although LyXFileDlg
still needs to be modified to make it straightforward to return a directory
if that is what is desired.
Angus
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Here is that patch.
Angus> I've simply commented out FL_LIGHTER_COL1. It's not yet used
Angus> anyway. If you can work out how to highlight the active folder,
Angus> it won't be.
Fine. I applied the patch.
Angus> The patch also
Attached is a clean-up of FormPreferences. Each tab folder is now
encapsulated in its own class.
The patch also activates the various "Browse" buttons, although LyXFileDlg
still needs to be modified to make it straightforward to return a directory
if that is what is desired.
Angus
Here is that patch.
I've simply commented out FL_LIGHTER_COL1. It's not yet used anyway. If you
can work out how to highlight the active folder, it won't be.
The patch also adds the ability to write any changes to the xforms GUI to
file and to then read them back in next time. LyXLex is very
Here is that patch.
I've simply commented out FL_LIGHTER_COL1. It's not yet used anyway. If you
can work out how to highlight the active folder, it won't be.
The patch also adds the ability to write any changes to the xforms GUI to
file and to then read them back in next time. LyXLex is very
"Angus" == Angus Leeming [EMAIL PROTECTED] writes:
Angus The Colors tab is now working and, to show you all the fun you
Angus can have with it, I've given it the ability to modify the
Angus colors of the xforms GUI. In fact, this is ALL you can do with
Angus it at the moment; modifying the
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> The Colors tab is now working and, to show you all the fun you
Angus> can have with it, I've given it the ability to modify the
Angus> colors of the xforms GUI. In fact, this is ALL you can do with
Angus> it at the moment;
"Angus" == Angus Leeming [EMAIL PROTECTED] writes:
Angus Attached is a patch that gets rid of the timer. Feedback now
Angus uses the Preemptive handler instead. Much simpler. The patch
Angus also finishes off the Converters and Formats tabs. ALMOST. I
Angus need a little help to finish off,
Attached is yet another patch to FormPreferences.
I think you'll like this one...
The Colors tab is now working and, to show you all the fun you can have with
it, I've given it the ability to modify the colors of the xforms GUI. In
fact, this is ALL you can do with it at the moment; modifying
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Attached is a patch that gets rid of the timer. Feedback now
Angus> uses the Preemptive handler instead. Much simpler. The patch
Angus> also finishes off the Converters and Formats tabs. ALMOST. I
Angus> need a little help to
Attached is yet another patch to FormPreferences.
I think you'll like this one...
The Colors tab is now working and, to show you all the fun you can have with
it, I've given it the ability to modify the colors of the xforms GUI. In
fact, this is ALL you can do with it at the moment; modifying
On 07-Nov-2000 Dekel Tsur wrote:
I guess you only use Latin languages, in which case a single keymap suffices.
But if you want, for example, Hebrew/Russian/English, then you need 3
different maps!.
Well I understood that you have other keymap problems then me and I want
to resolve them
Attached is a patch that gets rid of the timer. Feedback now uses the
Preemptive handler instead. Much simpler. The patch also finishes off the
Converters and Formats tabs. ALMOST. I need a little help to finish off, so...
I haven't made use of a functor; if anyone is desperately worried, then
On Tue, Nov 07, 2000 at 10:23:47PM +0100, Lars Gullik Bjnnes wrote:
Dekel Tsur [EMAIL PROTECTED] writes:
| Use
| struct compare_formats {
| bool operator()(Format const a, Format const b) {
| return a.name b.name;
| }
| }
|
| and then
|
On Wed, Nov 08, 2000 at 06:43:08PM +, Angus Leeming wrote:
Can't yet Apply the Converters because I didn't have time to make Converter a
"real" class. Ie, it's still static. Perhaps you'd do this, Dekel, as you
know the code best. (Everything in FormPreferences should be ready; all
On 07-Nov-2000 Dekel Tsur wrote:
>
> I guess you only use Latin languages, in which case a single keymap suffices.
> But if you want, for example, Hebrew/Russian/English, then you need 3
> different maps!.
>
Well I understood that you have other keymap problems then me and I want
to resolve
Attached is a patch that gets rid of the timer. Feedback now uses the
Preemptive handler instead. Much simpler. The patch also finishes off the
Converters and Formats tabs. ALMOST. I need a little help to finish off, so...
I haven't made use of a functor; if anyone is desperately worried, then
On Tue, Nov 07, 2000 at 10:23:47PM +0100, Lars Gullik Bjnnes wrote:
> Dekel Tsur <[EMAIL PROTECTED]> writes:
>
> | Use
> | struct compare_formats {
> | bool operator()(Format const & a, Format const & b) {
> | return a.name < b.name;
> | }
> | }
> |
> | and then
> |
On Wed, Nov 08, 2000 at 06:43:08PM +, Angus Leeming wrote:
> Can't yet Apply the Converters because I didn't have time to make Converter a
> "real" class. Ie, it's still static. Perhaps you'd do this, Dekel, as you
> know the code best. (Everything in FormPreferences should be ready; all
"Dekel" == Dekel Tsur [EMAIL PROTECTED] writes:
Dekel I want to add a keymap entry to the languages file, so that the
Dekel keymap can automatically change when the language is changed
Dekel (esp. useful for multilingual files).
Except that french users with a qwerty keyboard (all non-pc unix
On 06-Nov-2000 Dekel Tsur wrote:
I want to add a keymap entry to the languages file, so that the keymap
can automatically change when the language is changed (esp. useful for
multilingual files).
I surely don't want this! I have only one keyboard and I want my
keys as they are. If I like
On Mon, 06 Nov 2000, Dekel Tsur wrote:
The items in the combox shouldn't have the full path and the kmap
extension, namely, it should be
american-2
american
instead of
.../lyx-devel/lib/kbd/american-2.kmap
/lyx-devel/lib/kbd/american.kmap
Sure. I just wanted to get something working
"Angus" == Angus Leeming [EMAIL PROTECTED] writes:
Angus Because I sort the list of names (which I store). If I could
Angus sort the list of formats by name, then I'd do that instead.
Angus Note that the STL is largely unknown to me and whilst I do have
Angus reference literature, I find that I
On Tue, 07 Nov 2000, Jean-Marc Lasgouttes wrote:
"Angus" == Angus Leeming [EMAIL PROTECTED] writes:
Angus Because I sort the list of names (which I store). If I could
Angus sort the list of formats by name, then I'd do that instead.
Angus Note that the STL is largely unknown to me and
"Angus" == Angus Leeming [EMAIL PROTECTED] writes:
Angus sigh... Jean-Marc, I've worked flat out on this stuff for two
Angus weeks. If anybody feels the need to clean up the code base,
Angus then they won't find me stopping them. This isn't meant to be a
Angus flame, just exhaustion!
That was
On Tue, Nov 07, 2000 at 09:39:22AM +, Angus Leeming wrote:
why aren't you doing it the way I originally did ? namely
int i = fl_get_browser(formats_-browser_formats);
if (i 0) {
Format const f = formats_vec[i-1];
fl_set_input(formats_-input_format,
On Tue, Nov 07, 2000 at 10:19:19AM +0100, Juergen Vigna wrote:
On 06-Nov-2000 Dekel Tsur wrote:
I want to add a keymap entry to the languages file, so that the keymap
can automatically change when the language is changed (esp. useful for
multilingual files).
I surely don't want
Well now. I defined
bool FormatsCompare( Format const a, Format const b )
{
return( a.name b.name );
}
and then
sort( formats_vec.begin(), formats_vec.end(), FormatsCompare );
And something similar for sorting Commands:
bool CommandCompare( Command const a, Command const b
On Tue, Nov 07, 2000 at 06:42:27PM +, Angus Leeming wrote:
Well now. I defined
bool FormatsCompare( Format const a, Format const b )
{
return( a.name b.name );
}
and then
sort( formats_vec.begin(), formats_vec.end(), FormatsCompare );
And something similar for
Dekel Tsur [EMAIL PROTECTED] writes:
| Use
| struct compare_formats {
| bool operator()(Format const a, Format const b) {
| return a.name b.name;
| }
| }
|
| and then
| sort(formats_vec.begin(), formats_vec.end(), compare_formats());
|
| PS Is there a template for
Dekel Tsur [EMAIL PROTECTED] writes:
IMHO the default keymap for any given keymap should be the default
keymap for the system, if _nything_ else is wanted it should be
configured and decided by the user. i.e. we should not add a keymap
field to languages.
Lgb
| On Tue, Nov 07, 2000
On 06-Nov-2000 Dekel Tsur wrote:
I want to add a keymap entry to the languages file, so that the keymap
can automatically change when the language is changed (esp. useful for
multilingual files).
I surely don't want this! I have only one keyboard and I want my
keys as they
bool FormatsCompare( Format const a, Format const b )
{
return( a.name b.name );
}
and then
sort( formats_vec.begin(), formats_vec.end(), FormatsCompare );
And something similar for sorting Commands:
bool CommandCompare( Command const a, Command const b )
{
> "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes:
Dekel> I want to add a keymap entry to the languages file, so that the
Dekel> keymap can automatically change when the language is changed
Dekel> (esp. useful for multilingual files).
Except that french users with a qwerty keyboard (all
On 06-Nov-2000 Dekel Tsur wrote:
>
> I want to add a keymap entry to the languages file, so that the keymap
> can automatically change when the language is changed (esp. useful for
> multilingual files).
I surely don't want this! I have only one keyboard and I want my
keys as they are. If I
On Mon, 06 Nov 2000, Dekel Tsur wrote:
> The items in the combox shouldn't have the full path and the kmap
> extension, namely, it should be
> american-2
> american
> instead of
> .../lyx-devel/lib/kbd/american-2.kmap
> /lyx-devel/lib/kbd/american.kmap
Sure. I just wanted to get something
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Because I sort the list of names (which I store). If I could
Angus> sort the list of formats by name, then I'd do that instead.
Angus> Note that the STL is largely unknown to me and whilst I do have
Angus> reference literature, I
On Tue, 07 Nov 2000, Jean-Marc Lasgouttes wrote:
> > "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
>
> Angus> Because I sort the list of names (which I store). If I could
> Angus> sort the list of formats by name, then I'd do that instead.
> Angus> Note that the STL is largely unknown
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> sigh... Jean-Marc, I've worked flat out on this stuff for two
Angus> weeks. If anybody feels the need to clean up the code base,
Angus> then they won't find me stopping them. This isn't meant to be a
Angus> flame, just exhaustion!
On Tue, Nov 07, 2000 at 09:39:22AM +, Angus Leeming wrote:
> > why aren't you doing it the way I originally did ? namely
> >
> > int i = fl_get_browser(formats_->browser_formats);
> > if (i > 0) {
> > Format const & f = formats_vec[i-1];
> >
On Tue, Nov 07, 2000 at 10:19:19AM +0100, Juergen Vigna wrote:
>
> On 06-Nov-2000 Dekel Tsur wrote:
> >
> > I want to add a keymap entry to the languages file, so that the keymap
> > can automatically change when the language is changed (esp. useful for
> > multilingual files).
>
> I surely
Well now. I defined
bool FormatsCompare( Format const & a, Format const & b )
{
return( a.name < b.name );
}
and then
sort( formats_vec.begin(), formats_vec.end(), );
And something similar for sorting Commands:
bool CommandCompare( Command const & a, Command const & b )
{
On Tue, Nov 07, 2000 at 06:42:27PM +, Angus Leeming wrote:
> Well now. I defined
>
> bool FormatsCompare( Format const & a, Format const & b )
> {
> return( a.name < b.name );
> }
> and then
> sort( formats_vec.begin(), formats_vec.end(), );
>
> And something similar for
Dekel Tsur <[EMAIL PROTECTED]> writes:
| Use
| struct compare_formats {
| bool operator()(Format const & a, Format const & b) {
| return a.name < b.name;
| }
| }
|
| and then
| sort(formats_vec.begin(), formats_vec.end(), compare_formats());
|
| PS Is there a template for
Dekel Tsur <[EMAIL PROTECTED]> writes:
IMHO the default keymap for any given keymap should be the default
keymap for the system, if _nything_ else is wanted it should be
configured and decided by the user. i.e. we should not add a keymap
field to languages.
Lgb
| On Tue, Nov 07, 2000
> > On 06-Nov-2000 Dekel Tsur wrote:
> > >
> > > I want to add a keymap entry to the languages file, so that the keymap
> > > can automatically change when the language is changed (esp. useful for
> > > multilingual files).
> >
> > I surely don't want this! I have only one keyboard and I want
> bool FormatsCompare( Format const & a, Format const & b )
> {
> return( a.name < b.name );
> }
> and then
> sort( formats_vec.begin(), formats_vec.end(), );
>
> And something similar for sorting Commands:
>
> bool CommandCompare( Command const & a, Command const & b )
> {
>
I think that you should list all (and only) .kmap files.
(But you can just replace the keymap comboxes by simple text input buttons,
as I am going to remove the kbmap_primary/kbmap_secondary variables from
lyxrc.)
Ok. We're to leave it up to the user to get things right here?. But why are
"Dekel" == Dekel Tsur [EMAIL PROTECTED] writes:
Dekel I think that you should list all (and only) .kmap files. (But
Dekel you can just replace the keymap comboxes by simple text input
Dekel buttons, as I am going to remove the
Dekel kbmap_primary/kbmap_secondary variables from lyxrc.)
What are
On Mon, 06 Nov 2000, Jean-Marc Lasgouttes wrote:
"Dekel" == Dekel Tsur [EMAIL PROTECTED] writes:
Dekel I think that you should list all (and only) .kmap files. (But
Dekel you can just replace the keymap comboxes by simple text input
Dekel buttons, as I am going to remove the
Dekel
Patch attached.
Any answers to the questions below?
Angus
2000-11-06 Angus Leeming [EMAIL PROTECTED]
* src/frontends/xforms/forms/form_preferences.fd: Inactive tab folders
are no longer dark. Haven't yet worked out how to lighten the colour of
the active tabfolder. Any
(LanguagesXXX): the kbmap choices now contain the files
sytem_lyxdir/kbd/*.kmap. I think that these choices should eventually
be replaced by an input with a file browse button, but since the browse
buttons don'y yet work, this'll do for the moment.
The items in the
On Mon, Nov 06, 2000 at 11:12:08AM +0100, Jean-Marc Lasgouttes wrote:
"Dekel" == Dekel Tsur [EMAIL PROTECTED] writes:
Dekel I think that you should list all (and only) .kmap files. (But
Dekel you can just replace the keymap comboxes by simple text input
Dekel buttons, as I am going to
> I think that you should list all (and only) .kmap files.
> (But you can just replace the keymap comboxes by simple text input buttons,
> as I am going to remove the kbmap_primary/kbmap_secondary variables from
> lyxrc.)
Ok. We're to leave it up to the user to get things right here?. But why
> "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes:
Dekel> I think that you should list all (and only) .kmap files. (But
Dekel> you can just replace the keymap comboxes by simple text input
Dekel> buttons, as I am going to remove the
Dekel> kbmap_primary/kbmap_secondary variables from
On Mon, 06 Nov 2000, Jean-Marc Lasgouttes wrote:
> > "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes:
>
> Dekel> I think that you should list all (and only) .kmap files. (But
> Dekel> you can just replace the keymap comboxes by simple text input
> Dekel> buttons, as I am going to remove the
Patch attached.
Any answers to the questions below?
Angus
2000-11-06 Angus Leeming <[EMAIL PROTECTED]>
* src/frontends/xforms/forms/form_preferences.fd: Inactive tab folders
are no longer dark. Haven't yet worked out how to lighten the colour of
the active tabfolder.
> (LanguagesXXX): the kbmap choices now contain the files
> sytem_lyxdir/kbd/*.kmap. I think that these choices should eventually
> be replaced by an input with a file browse button, but since the browse
> buttons don'y yet work, this'll do for the moment.
The items in
On Mon, Nov 06, 2000 at 11:12:08AM +0100, Jean-Marc Lasgouttes wrote:
> > "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes:
>
> Dekel> I think that you should list all (and only) .kmap files. (But
> Dekel> you can just replace the keymap comboxes by simple text input
> Dekel> buttons, as I
On Sat, Nov 04, 2000 at 12:48:29AM +0200, Dekel Tsur wrote:
Few more remarks:
The converters tab doesn't have a flags field.
The formats tab is doesn't have a shortcut field.
One more:
The Add button in converters/formats tabs should be named add/change
I do have a question on the behavior
On Sat, Nov 04, 2000 at 12:48:29AM +0200, Dekel Tsur wrote:
> Few more remarks:
> The converters tab doesn't have a flags field.
> The formats tab is doesn't have a shortcut field.
One more:
The Add button in converters/formats tabs should be named add/change
I do have a question on the
"Angus" == Angus Leeming [EMAIL PROTECTED] writes:
Angus oh yes, and I THINK I've fixed the crash problem when closing
Angus LyX after opening FormPreferences. Could someone check, as I
Angus can't reproduce the problem here...
Angus, a question: would it be possible to change the font of the
"Angus" == Angus Leeming [EMAIL PROTECTED] writes:
Angus Attached is a patch implementing Colours and Formats tabs. You
Angus can't actually DO anything with them yet, but I'd like some
Angus feedback.
Angus, I'll apply your patch. Note however that it contains lines
like
if( name ==
"Angus" == Angus Leeming [EMAIL PROTECTED] writes:
Angus The colours tab is a shameless copy of an xforms demo. I've
Angus tried to write it in C++, but I'm a bit of a novice still. All
Angus feedback welcome.
A few remarks:
- the field showing the resulting color is not visible enough (the
On Fri, 03 Nov 2000, Jean-Marc Lasgouttes wrote:
Angus, I'll apply your patch. Note however that it contains lines
like
if( name == "gray0" ) name = "black"
if( name == "gray100" ) name = "white"
which probably do not compile better on your machine than it does on
mine :) You
On Thu, Nov 02, 2000 at 10:22:35PM +, Angus Leeming wrote:
Esp. with the Formats (Outputs-Formats). This is the first point: where
should it go. Formats are for input AND output. Suggestions for the name of a
new top level tab?
Second point. I shoved in the "Viewers" field with this
Angus Leeming [EMAIL PROTECTED] writes:
| I don't thing the LColor entries need know about the colour name at all. Why
| not just have LColour::color containing a list of coloured elements
| (background, foreground, latex etc) and change LColour::ColorEntry to
|
| struct ColorEntry {
|
1 - 100 of 168 matches
Mail list logo
