Lars == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
Lars Dekel Tsur [EMAIL PROTECTED] writes:
Lars | On Mon, Oct 14, 2002 at 07:47:59PM +0200, Lars Gullik Bj?nnes wrote:
Lars |
Lars | A lot better than the hardcoded 95.
Lars |
Lars | Let's try it.
Lars |
Lars | Any objection to my
Dekel == Dekel Tsur [EMAIL PROTECTED] writes:
Dekel On Mon, Oct 14, 2002 at 06:22:57PM +0200, Dekel Tsur wrote:
I think that the font size problem is due to the fact that
qt2/lyx_gui.C does not read the DPI from the screen but assumes
instead that dpi = 95.
Dekel BTW, why are we
On Tue, Oct 15, 2002 at 09:45:42AM +0200, Lars Gullik Bj?nnes wrote:
Dekel Tsur [EMAIL PROTECTED] writes:
| On Mon, Oct 14, 2002 at 11:44:36PM +0200, Lars Gullik Bj?nnes wrote:
| |
| | http://marc.theaimsgroup.com/?l=lyx-develm=103445154004355w=2
|
| That was not exactly what I
Dekel Tsur [EMAIL PROTECTED] writes:
| On Tue, Oct 15, 2002 at 09:45:42AM +0200, Lars Gullik Bj?nnes wrote:
Dekel Tsur [EMAIL PROTECTED] writes:
| On Mon, Oct 14, 2002 at 11:44:36PM +0200, Lars Gullik Bj?nnes wrote:
| |
| | http://marc.theaimsgroup.com/?l=lyx-develm=103445154004355w=2
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> Dekel Tsur <[EMAIL PROTECTED]> writes:
Lars> | On Mon, Oct 14, 2002 at 07:47:59PM +0200, Lars Gullik Bj?nnes wrote:
Lars> | >
Lars> | > A lot better than the hardcoded 95.
Lars> | >
Lars> | > Let's try it.
Lars> |
Lars> |
> "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes:
Dekel> On Mon, Oct 14, 2002 at 06:22:57PM +0200, Dekel Tsur wrote:
>> I think that the font size problem is due to the fact that
>> qt2/lyx_gui.C does not read the DPI from the screen but assumes
>> instead that dpi = 95.
Dekel> BTW, why
On Tue, Oct 15, 2002 at 09:45:42AM +0200, Lars Gullik Bj?nnes wrote:
> Dekel Tsur <[EMAIL PROTECTED]> writes:
>
> | On Mon, Oct 14, 2002 at 11:44:36PM +0200, Lars Gullik Bj?nnes wrote:
> | > |
> | > | http://marc.theaimsgroup.com/?l=lyx-devel=103445154004355=2
> | >
> | > That was not exactly
Dekel Tsur <[EMAIL PROTECTED]> writes:
| On Tue, Oct 15, 2002 at 09:45:42AM +0200, Lars Gullik Bj?nnes wrote:
>> Dekel Tsur <[EMAIL PROTECTED]> writes:
>>
>> | On Mon, Oct 14, 2002 at 11:44:36PM +0200, Lars Gullik Bj?nnes wrote:
>> | > |
>> | > |
Kornel Benko wrote:
-BEGIN PGP SIGNED MESSAGE-
On Sunday 13 October 2002 19:58, John Levon wrote:
I don't understand why it fails for you, but Mode_switch can give me
ä perfectly in LyX Qt
I see. Maybe, because you are using QT2 while I am on QT3.
Bad luck for me. I cannot
Kornel Benko wrote:
Sorry for making trouble.
On a further thought IMO that the problems you have a connected to
the fact that you use latin15. IMO John has a lot of font-latin1()
in his code which not always is appropriate (just hit me if I'm wrong
John ;) John and myself still use latin1,
-BEGIN PGP SIGNED MESSAGE-
On Monday 14 October 2002 08:47, Juergen Vigna wrote:
Kornel Benko wrote:
Sorry for making trouble.
On a further thought IMO that the problems you have a connected to
the fact that you use latin15. IMO John has a lot of font-latin1()
in his code which
-BEGIN PGP SIGNED MESSAGE-
On Monday 14 October 2002 08:42, Juergen Vigna wrote:
Multi_key--a:
Press key 4128 text none, ascii 0
getSymbolName() - Shift_L
KeySym is Shift_L
Press key 196 text ä, ascii 228
getSymbolName() - Adiaeresis
KeySym is Adiaeresis
action first set to [89]
-BEGIN PGP SIGNED MESSAGE-
On Monday 14 October 2002 10:16, Kornel Benko wrote:
This is confusing ... I get here
getSymbolName() - ä
but there is no action for it (like self_insert() for Adiaeresis)
I do not know, what is going wrong with the QKeyEvent.
But changing the code
Dekel == Dekel Tsur [EMAIL PROTECTED] writes:
Dekel On Sun, Oct 13, 2002 at 12:02:44PM +0100, Kornel Benko wrote:
On Saturday 12 October 2002 20:38, Dekel Tsur wrote: Since, QT
uses unicode internally, we should use that. This patch allow
displaying of non iso8859-1 chars. Please test.
-BEGIN PGP SIGNED MESSAGE-
On Monday 14 October 2002 13:10, John Levon wrote:
I dunno. Let's try it. key_ == 0 is impossible, after all, despite the
fact that it happens.
So I am not supposed to patch the code each time I use new cvs?
Despite the fonts-size-problem (and missing
On Monday 14 October 2002 13:24, Kornel Benko wrote:
So I am not supposed to patch the code each time I use new cvs?
Despite the fonts-size-problem (and missing preferences) is this a very
agreeable version.
I have been able to have an working version only with redhat 8.0. And yes I
also
On Mon, Oct 14, 2002 at 01:10:25PM +0100, John Levon wrote:
On Mon, Oct 14, 2002 at 11:37:57AM +0100, Kornel Benko wrote:
But changing the code makes it working. Does it break anything? (Not here)
I dunno. Let's try it. key_ == 0 is impossible, after all, despite the
fact that it
On Mon, Oct 14, 2002 at 01:54:29PM +0100, Jos? Ab?lio Oliveira Matos wrote:
On Monday 14 October 2002 13:24, Kornel Benko wrote:
So I am not supposed to patch the code each time I use new cvs?
Despite the fonts-size-problem (and missing preferences) is this a very
agreeable version.
On Mon, Oct 14, 2002 at 06:22:57PM +0200, Dekel Tsur wrote:
I think that the font size problem is due to the fact that
qt2/lyx_gui.C does not read the DPI from the screen but assumes instead
that dpi = 95.
The following patch fixes this.
I'm not sure that I'm using the correct method to
On Mon, Oct 14, 2002 at 06:22:57PM +0200, Dekel Tsur wrote:
I'm not sure that I'm using the correct method to read the DPI, but it works.
Comments ?
If valgrind is happy with the QWidget on the stack, this is fine, I
think. Isn't Qt dumb ? :)
regards
john
--
That's just kitten-eating
Dekel Tsur [EMAIL PROTECTED] writes:
| On Mon, Oct 14, 2002 at 01:54:29PM +0100, Jos? Ab?lio Oliveira Matos wrote:
| On Monday 14 October 2002 13:24, Kornel Benko wrote:
|
| So I am not supposed to patch the code each time I use new cvs?
| Despite the fonts-size-problem (and missing
On Mon, Oct 14, 2002 at 07:47:59PM +0200, Lars Gullik Bj?nnes wrote:
A lot better than the hardcoded 95.
Let's try it.
Any objection to my other patches:
- Fix automatic reconfiguration
- Using unicode in QT painter
Dekel Tsur [EMAIL PROTECTED] writes:
| On Mon, Oct 14, 2002 at 07:47:59PM +0200, Lars Gullik Bj?nnes wrote:
|
| A lot better than the hardcoded 95.
|
| Let's try it.
|
| Any objection to my other patches:
| - Fix automatic reconfiguration
I belive that should be ok, but since J-M did
On Mon, Oct 14, 2002 at 11:23:24PM +0200, Lars Gullik Bj?nnes wrote:
| - Using unicode in QT painter
Can you resend the patch on this one?
http://marc.theaimsgroup.com/?l=lyx-develm=103445154004355w=2
Dekel Tsur [EMAIL PROTECTED] writes:
| On Mon, Oct 14, 2002 at 11:23:24PM +0200, Lars Gullik Bj?nnes wrote:
|
| | - Using unicode in QT painter
|
| Can you resend the patch on this one?
|
| http://marc.theaimsgroup.com/?l=lyx-develm=103445154004355w=2
That was not exactly what I asked
On Mon, Oct 14, 2002 at 02:10:38PM +0200, Jean-Marc Lasgouttes wrote:
Dekel PS: Should we replace all occurrences of iso8859-1 by
Dekel iso8859-15 ?
Are we sure that all systems able to support lyx do have support for
this encoding? Would it be difficult to propose several encodings for
a
On Mon, Oct 14, 2002 at 06:22:57PM +0200, Dekel Tsur wrote:
I think that the font size problem is due to the fact that
qt2/lyx_gui.C does not read the DPI from the screen but assumes instead
that dpi = 95.
BTW, why are we considering the dpi when computing the size of the font on
screen ?
Kornel Benko wrote:
> -BEGIN PGP SIGNED MESSAGE-
>
> On Sunday 13 October 2002 19:58, John Levon wrote:
>
>>I don't understand why it fails for you, but Mode_switch can give me
>>ä perfectly in LyX Qt
>
>
> I see. Maybe, because you are using QT2 while I am on QT3.
> Bad luck for
Kornel Benko wrote:
> Sorry for making trouble.
On a further thought IMO that the problems you have a connected to
the fact that you use latin15. IMO John has a lot of font->latin1()
in his code which not always is appropriate (just hit me if I'm wrong
John ;) John and myself still use latin1,
-BEGIN PGP SIGNED MESSAGE-
On Monday 14 October 2002 08:47, Juergen Vigna wrote:
> Kornel Benko wrote:
> > Sorry for making trouble.
>
> On a further thought IMO that the problems you have a connected to
> the fact that you use latin15. IMO John has a lot of font->latin1()
> in his code
-BEGIN PGP SIGNED MESSAGE-
On Monday 14 October 2002 08:42, Juergen Vigna wrote:
> Multi_key-"-a:
>
> Press key 4128 text "none", ascii "0"
> getSymbolName() -> Shift_L
> KeySym is Shift_L
> Press key 196 text "ä", ascii "228"
> getSymbolName() -> Adiaeresis
> KeySym is Adiaeresis
>
-BEGIN PGP SIGNED MESSAGE-
On Monday 14 October 2002 10:16, Kornel Benko wrote:
> This is confusing ... I get here
> getSymbolName() -> ä
> but there is no action for it (like self_insert() for Adiaeresis)
I do not know, what is going wrong with the "QKeyEvent".
But changing the
> "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes:
Dekel> On Sun, Oct 13, 2002 at 12:02:44PM +0100, Kornel Benko wrote:
>> On Saturday 12 October 2002 20:38, Dekel Tsur wrote: > Since, QT
>> uses unicode internally, we should use that. > This patch allow
>> displaying of non iso8859-1
-BEGIN PGP SIGNED MESSAGE-
On Monday 14 October 2002 13:10, John Levon wrote:
> I dunno. Let's try it. key_ == 0 is impossible, after all, despite the
> fact that it happens.
So I am not supposed to patch the code each time I use new cvs?
Despite the fonts-size-problem (and missing
On Monday 14 October 2002 13:24, Kornel Benko wrote:
>
> So I am not supposed to patch the code each time I use new cvs?
> Despite the fonts-size-problem (and missing preferences) is this a very
> agreeable version.
I have been able to have an working version only with redhat 8.0. And yes I
On Mon, Oct 14, 2002 at 01:10:25PM +0100, John Levon wrote:
> On Mon, Oct 14, 2002 at 11:37:57AM +0100, Kornel Benko wrote:
>
> > But changing the code makes it working. Does it break anything? (Not here)
>
> I dunno. Let's try it. key_ == 0 is impossible, after all, despite the
> fact that it
On Mon, Oct 14, 2002 at 01:54:29PM +0100, Jos? Ab?lio Oliveira Matos wrote:
> On Monday 14 October 2002 13:24, Kornel Benko wrote:
> >
> > So I am not supposed to patch the code each time I use new cvs?
> > Despite the fonts-size-problem (and missing preferences) is this a very
> > agreeable
On Mon, Oct 14, 2002 at 06:22:57PM +0200, Dekel Tsur wrote:
> I think that the font size problem is due to the fact that
> qt2/lyx_gui.C does not read the DPI from the screen but assumes instead
> that dpi = 95.
> The following patch fixes this.
> I'm not sure that I'm using the correct method
On Mon, Oct 14, 2002 at 06:22:57PM +0200, Dekel Tsur wrote:
> I'm not sure that I'm using the correct method to read the DPI, but it works.
> Comments ?
If valgrind is happy with the QWidget on the stack, this is fine, I
think. Isn't Qt dumb ? :)
regards
john
--
"That's just kitten-eating
Dekel Tsur <[EMAIL PROTECTED]> writes:
| On Mon, Oct 14, 2002 at 01:54:29PM +0100, Jos? Ab?lio Oliveira Matos wrote:
| > On Monday 14 October 2002 13:24, Kornel Benko wrote:
| > >
| > > So I am not supposed to patch the code each time I use new cvs?
| > > Despite the fonts-size-problem (and
On Mon, Oct 14, 2002 at 07:47:59PM +0200, Lars Gullik Bj?nnes wrote:
>
> A lot better than the hardcoded 95.
>
> Let's try it.
Any objection to my other patches:
- Fix automatic reconfiguration
- Using unicode in QT painter
Dekel Tsur <[EMAIL PROTECTED]> writes:
| On Mon, Oct 14, 2002 at 07:47:59PM +0200, Lars Gullik Bj?nnes wrote:
| >
| > A lot better than the hardcoded 95.
| >
| > Let's try it.
|
| Any objection to my other patches:
| - Fix automatic reconfiguration
I belive that should be ok, but since J-M
On Mon, Oct 14, 2002 at 11:23:24PM +0200, Lars Gullik Bj?nnes wrote:
>
> | - Using unicode in QT painter
>
> Can you resend the patch on this one?
http://marc.theaimsgroup.com/?l=lyx-devel=103445154004355=2
Dekel Tsur <[EMAIL PROTECTED]> writes:
| On Mon, Oct 14, 2002 at 11:23:24PM +0200, Lars Gullik Bj?nnes wrote:
| >
| > | - Using unicode in QT painter
| >
| > Can you resend the patch on this one?
|
| http://marc.theaimsgroup.com/?l=lyx-devel=103445154004355=2
That was not exactly what I
On Mon, Oct 14, 2002 at 02:10:38PM +0200, Jean-Marc Lasgouttes wrote:
> Dekel> PS: Should we replace all occurrences of iso8859-1 by
> Dekel> iso8859-15 ?
>
> Are we sure that all systems able to support lyx do have support for
> this encoding? Would it be difficult to propose several encodings
On Mon, Oct 14, 2002 at 06:22:57PM +0200, Dekel Tsur wrote:
>
> I think that the font size problem is due to the fact that
> qt2/lyx_gui.C does not read the DPI from the screen but assumes instead
> that dpi = 95.
BTW, why are we considering the dpi when computing the size of the font on
-BEGIN PGP SIGNED MESSAGE-
On Saturday 12 October 2002 20:38, Dekel Tsur wrote:
Since, QT uses unicode internally, we should use that.
This patch allow displaying of non iso8859-1 chars.
Please test.
I am unable to display the euro symbols (with or without this patch)
with the
-BEGIN PGP SIGNED MESSAGE-
On Sunday 13 October 2002 12:52, Dekel Tsur wrote:
This is because the lib/languages file does not instruct to use the
iso8859-15 encoding for your language.
Just edit the file, and replace the current encoding for your language
by iso8859-15.
This helped.
-BEGIN PGP SIGNED MESSAGE-
On Sunday 13 October 2002 12:49, Philipp Reichmuth wrote:
DT Since, QT uses unicode internally, we should use that.
Unicode support in Qt 2.1 is *bad*, and even 3 has some problems. I'm
not sure about RTL scripts, for example. At least for Qt 2.1 and Qt
DT Since, QT uses unicode internally, we should use that.
Unicode support in Qt 2.1 is *bad*, and even 3 has some problems. I'm
not sure about RTL scripts, for example. At least for Qt 2.1 and Qt
for Windows, this could mean some serious working around trouble for
Hebrew and Arabic.
Philipp
On Sun, Oct 13, 2002 at 12:02:44PM +0100, Kornel Benko wrote:
On Saturday 12 October 2002 20:38, Dekel Tsur wrote:
Since, QT uses unicode internally, we should use that.
This patch allow displaying of non iso8859-1 chars.
Please test.
I am unable to display the euro symbols (with or
Since, QT uses unicode internally, we should use that.
This patch allow displaying of non iso8859-1 chars.
Please test.
patch.gz
Description: Binary data
On Sun, Oct 13, 2002 at 01:49:12PM +0200, Philipp Reichmuth wrote:
DT Since, QT uses unicode internally, we should use that.
Unicode support in Qt 2.1 is *bad*, and even 3 has some problems. I'm
not sure about RTL scripts, for example. At least for Qt 2.1 and Qt
for Windows, this could
On Sun, Oct 13, 2002 at 01:15:54PM +0100, Kornel Benko wrote:
as soon, as i press the modify-key (e.g. to enter ä on a us-keyboard) lyx blows
away.
The relevant backtrace:
Run xev and tell us the output when you press your modify key
regards
john
-BEGIN PGP SIGNED MESSAGE-
On Sunday 13 October 2002 17:11, John Levon wrote:
On Sun, Oct 13, 2002 at 01:15:54PM +0100, Kornel Benko wrote:
as soon, as i press the modify-key (e.g. to enter ä on a us-keyboard)
lyx blows away. The relevant backtrace:
Run xev and tell us the output
On Sun, Oct 13, 2002 at 06:02:46PM +0100, Kornel Benko wrote:
state 0x10, keycode 113 (keysym 0xff7e, Mode_switch), same_screen YES,
Eh, are you running current CVS ? I fixed this problem some time ago
afaik
Can you find out what Qt::Key_blah type gets generated by pressing it ?
john
--
On Sun, Oct 13, 2002 at 06:16:17PM +0100, John Levon wrote:
Can you find out what Qt::Key_blah type gets generated by pressing it ?
Or can you try changing
if (sym.empty()) {
lyxerr[Debug::KEY] sym empty in getSymbolName() endl;
sym = text_.latin1();
-BEGIN PGP SIGNED MESSAGE-
On Sunday 13 October 2002 18:16, John Levon wrote:
On Sun, Oct 13, 2002 at 06:02:46PM +0100, Kornel Benko wrote:
state 0x10, keycode 113 (keysym 0xff7e, Mode_switch), same_screen
YES,
Eh, are you running current CVS ? I fixed this problem some time
On Sun, Oct 13, 2002 at 06:13:34PM +0100, Kornel Benko wrote:
How?
(I could do some debugging if I were pointed in the correct direction.)
see if this fixes it
john
Index: QLyXKeySym.C
===
RCS file:
-BEGIN PGP SIGNED MESSAGE-
On Sunday 13 October 2002 18:19, John Levon wrote:
On Sun, Oct 13, 2002 at 06:16:17PM +0100, John Levon wrote:
Can you find out what Qt::Key_blah type gets generated by pressing it ?
Or can you try changing
if (sym.empty()) {
-BEGIN PGP SIGNED MESSAGE-
On Sunday 13 October 2002 18:36, John Levon wrote:
see if this fixes it
Unfortunately not so, that I could insert ä
Log:
sym empty in getSymbolName() for key 65535
getSymbolName() - none
KeySym is none
repainting 147,472 1,20
...
Press key 0 text ä, ascii
On Sun, Oct 13, 2002 at 06:41:57PM +0100, Kornel Benko wrote:
Unfortunately not so, that I could insert ä
Winging it here, but try this.
Index: QLyXKeySym.C
===
RCS file:
-BEGIN PGP SIGNED MESSAGE-
On Sunday 13 October 2002 19:10, John Levon wrote:
Winging it here, but try this.
Its becomming better ... but still no insert.
Log:
Press key 65535 text none, ascii 0
sym empty in getSymbolName() for key 65535
getSymbolName() - none
KeySym is none
-BEGIN PGP SIGNED MESSAGE-
On Sunday 13 October 2002 19:13, Kornel Benko wrote:
Its becomming better ... but still no insert.
Log:
Press key 65535 text none, ascii 0
sym empty in getSymbolName() for key 65535
getSymbolName() - none
KeySym is none
repainting ...
Press key 0 text
On Sun, Oct 13, 2002 at 07:13:20PM +0100, Kornel Benko wrote:
Press key 0 text ä, ascii 228
Qt is so broken. Key 0 is an impossible condition by their own fscking
headers.
Try changing QLyXKeySym :: isOK to always return true.
john
--
That's just kitten-eating wrong.
- Richard
-BEGIN PGP SIGNED MESSAGE-
On Sunday 13 October 2002 19:32, John Levon wrote:
Try changing QLyXKeySym :: isOK to always return true.
Looks better, but not inserted.
Log:
Press key 65535 text none, ascii 0
sym empty in getSymbolName() for key 65535
getSymbolName() - none
KeySym is none
On Sun, Oct 13, 2002 at 07:40:54PM +0100, Kornel Benko wrote:
getSymbolName() - ä
Key [action=-1][ä]
Removing modifiers...
Action now set to [-1]
repainting 110,554 1,20
The same is valid for other (dead-)X-modifiers.
I don't understand why it fails for you, but Mode_switch can give me
-BEGIN PGP SIGNED MESSAGE-
On Sunday 13 October 2002 19:58, John Levon wrote:
I don't understand why it fails for you, but Mode_switch can give me
ä perfectly in LyX Qt
I see. Maybe, because you are using QT2 while I am on QT3.
Bad luck for me. I cannot even insert the euro-sign.
-BEGIN PGP SIGNED MESSAGE-
On Saturday 12 October 2002 20:38, Dekel Tsur wrote:
> Since, QT uses unicode internally, we should use that.
> This patch allow displaying of non iso8859-1 chars.
> Please test.
I am unable to display the euro symbols (with or without this patch)
with the
-BEGIN PGP SIGNED MESSAGE-
On Sunday 13 October 2002 12:52, Dekel Tsur wrote:
> This is because the lib/languages file does not instruct to use the
> iso8859-15 encoding for your language.
> Just edit the file, and replace the current encoding for your language
> by iso8859-15.
This
-BEGIN PGP SIGNED MESSAGE-
On Sunday 13 October 2002 12:49, Philipp Reichmuth wrote:
> DT> Since, QT uses unicode internally, we should use that.
>
> Unicode support in Qt 2.1 is *bad*, and even 3 has some problems. I'm
> not sure about RTL scripts, for example. At least for Qt 2.1 and
DT> Since, QT uses unicode internally, we should use that.
Unicode support in Qt 2.1 is *bad*, and even 3 has some problems. I'm
not sure about RTL scripts, for example. At least for Qt 2.1 and Qt
for Windows, this could mean some serious working around trouble for
Hebrew and Arabic.
Philipp
On Sun, Oct 13, 2002 at 12:02:44PM +0100, Kornel Benko wrote:
> On Saturday 12 October 2002 20:38, Dekel Tsur wrote:
> > Since, QT uses unicode internally, we should use that.
> > This patch allow displaying of non iso8859-1 chars.
> > Please test.
>
> I am unable to display the euro symbols
Since, QT uses unicode internally, we should use that.
This patch allow displaying of non iso8859-1 chars.
Please test.
patch.gz
Description: Binary data
On Sun, Oct 13, 2002 at 01:49:12PM +0200, Philipp Reichmuth wrote:
>
> DT> Since, QT uses unicode internally, we should use that.
>
> Unicode support in Qt 2.1 is *bad*, and even 3 has some problems. I'm
> not sure about RTL scripts, for example. At least for Qt 2.1 and Qt
> for Windows, this
On Sun, Oct 13, 2002 at 01:15:54PM +0100, Kornel Benko wrote:
> as soon, as i press the modify-key (e.g. to enter "ä" on a us-keyboard) lyx blows
>away.
> The relevant backtrace:
Run "xev" and tell us the output when you press your modify key
regards
john
-BEGIN PGP SIGNED MESSAGE-
On Sunday 13 October 2002 17:11, John Levon wrote:
> On Sun, Oct 13, 2002 at 01:15:54PM +0100, Kornel Benko wrote:
> > as soon, as i press the modify-key (e.g. to enter "ä" on a us-keyboard)
> > lyx blows away. The relevant backtrace:
>
> Run "xev" and tell us
On Sun, Oct 13, 2002 at 06:02:46PM +0100, Kornel Benko wrote:
> state 0x10, keycode 113 (keysym 0xff7e, Mode_switch), same_screen YES,
Eh, are you running current CVS ? I fixed this problem some time ago
afaik
Can you find out what Qt::Key_blah type gets generated by pressing it ?
john
On Sun, Oct 13, 2002 at 06:16:17PM +0100, John Levon wrote:
> Can you find out what Qt::Key_blah type gets generated by pressing it ?
Or can you try changing
if (sym.empty()) {
lyxerr[Debug::KEY] << "sym empty in getSymbolName()" << endl;
sym =
-BEGIN PGP SIGNED MESSAGE-
On Sunday 13 October 2002 18:16, John Levon wrote:
> On Sun, Oct 13, 2002 at 06:02:46PM +0100, Kornel Benko wrote:
> > state 0x10, keycode 113 (keysym 0xff7e, Mode_switch), same_screen
> > YES,
>
> Eh, are you running current CVS ? I fixed this problem some
On Sun, Oct 13, 2002 at 06:13:34PM +0100, Kornel Benko wrote:
> How?
> (I could do some debugging if I were pointed in the correct direction.)
see if this fixes it
john
Index: QLyXKeySym.C
===
RCS file:
-BEGIN PGP SIGNED MESSAGE-
On Sunday 13 October 2002 18:19, John Levon wrote:
> On Sun, Oct 13, 2002 at 06:16:17PM +0100, John Levon wrote:
> > Can you find out what Qt::Key_blah type gets generated by pressing it ?
>
> Or can you try changing
>
> if (sym.empty()) {
>
-BEGIN PGP SIGNED MESSAGE-
On Sunday 13 October 2002 18:36, John Levon wrote:
> see if this fixes it
Unfortunately not so, that I could insert "ä"
Log:
sym empty in getSymbolName() for key 65535
getSymbolName() -> none
KeySym is none
repainting 147,472 1,20
...
Press key 0 text "ä",
On Sun, Oct 13, 2002 at 06:41:57PM +0100, Kornel Benko wrote:
>
> Unfortunately not so, that I could insert "ä"
Winging it here, but try this.
Index: QLyXKeySym.C
===
RCS file:
-BEGIN PGP SIGNED MESSAGE-
On Sunday 13 October 2002 19:10, John Levon wrote:
> Winging it here, but try this.
Its becomming better ... but still no insert.
Log:
Press key 65535 text "none", ascii "0"
sym empty in getSymbolName() for key 65535
getSymbolName() -> none
KeySym is none
-BEGIN PGP SIGNED MESSAGE-
On Sunday 13 October 2002 19:13, Kornel Benko wrote:
> Its becomming better ... but still no insert.
>
> Log:
> Press key 65535 text "none", ascii "0"
> sym empty in getSymbolName() for key 65535
> getSymbolName() -> none
> KeySym is none
> repainting ...
>
On Sun, Oct 13, 2002 at 07:13:20PM +0100, Kornel Benko wrote:
> Press key 0 text "ä", ascii "228"
Qt is so broken. Key 0 is an impossible condition by their own fscking
headers.
Try changing QLyXKeySym :: isOK to always return true.
john
--
"That's just kitten-eating wrong."
-
-BEGIN PGP SIGNED MESSAGE-
On Sunday 13 October 2002 19:32, John Levon wrote:
> Try changing QLyXKeySym :: isOK to always return true.
Looks better, but not inserted.
Log:
Press key 65535 text "none", ascii "0"
sym empty in getSymbolName() for key 65535
getSymbolName() -> none
KeySym is
On Sun, Oct 13, 2002 at 07:40:54PM +0100, Kornel Benko wrote:
> getSymbolName() -> ä
> Key [action=-1][ä]
> Removing modifiers...
> Action now set to [-1]
> repainting 110,554 1,20
>
> The same is valid for other (dead-)X-modifiers.
I don't understand why it fails for you, but Mode_switch can
-BEGIN PGP SIGNED MESSAGE-
On Sunday 13 October 2002 19:58, John Levon wrote:
> I don't understand why it fails for you, but Mode_switch can give me
> ä perfectly in LyX Qt
I see. Maybe, because you are using QT2 while I am on QT3.
Bad luck for me. I cannot even insert the
90 matches
Mail list logo
