Pavel Sanda wrote:
I have encountered a couple other problems that seem directly related to
fullscreen mode:
1. When coming out of fullscreen mode, the normal window returns, but it
does not automatically take focus as it should.
hmm, it does here. i guess that will be some qt thing on mac.
On Feb 19, 2008, at 9:14 PM, Pavel Sanda wrote:
It's not a focus problem (and screen-recenter and mouse selection
doesn't
affect it). Playing around a little more, I find that the arrow
keys are
recognized and the insertion point changes accordingly, but the
cursor does
not move on screen.
> It's not a focus problem (and screen-recenter and mouse selection doesn't
> affect it). Playing around a little more, I find that the arrow keys are
> recognized and the insertion point changes accordingly, but the cursor does
> not move on screen. So, after pressing down-arrow several times,
On Feb 19, 2008, at 8:22 PM, Pavel Sanda wrote:
The added preferences all seem to work well. The only oddity I've
noticed
concerns "Toggle tabbar". When this is selected and there are
multiple tabs
in normal mode, switching to fullscreen mode properly hides the
tabs. But
(staying in fullscr
Am 19.02.2008 um 21:38 schrieb Stefan Schimanski:
... and am on the way to implement completion for the text mode as
well.
Done. Good night!
Stefan
<>
> The added preferences all seem to work well. The only oddity I've noticed
> concerns "Toggle tabbar". When this is selected and there are multiple tabs
> in normal mode, switching to fullscreen mode properly hides the tabs. But
> (staying in fullscreen mode) selecting File > New brings up the
On Feb 19, 2008, at 4:56 PM, Pavel Sanda wrote:
A final question/request (which may go beyond what you want to do,
so feel
free to ignore it): especially with widescreen monitors (standard
on Macs),
fullscreen mode as currently implemented results in unreadably
long lines.
Would it be possi
> A final question/request (which may go beyond what you want to do, so feel
> free to ignore it): especially with widescreen monitors (standard on Macs),
> fullscreen mode as currently implemented results in unreadably long lines.
> Would it be possible to define line length (or % of screen wid
> > > >> i need to call some kind of redraw when comming back from fullscreen
> > > >> mode
> > > >> (scrollbar needs some update and probably recomputation).
> > > >
> > > > I don't really understand why you need that as a redraw should be
> > > > triggered
> > > > automatically following a res
> > >> i need to call some kind of redraw when comming back from fullscreen mode
> > >> (scrollbar needs some update and probably recomputation).
> > >
> > > I don't really understand why you need that as a redraw should be
> > > triggered
> > > automatically following a resize event (which you g
Andre Poenitz wrote:
On Tue, Feb 19, 2008 at 08:32:30AM +0100, Abdelrazak Younes wrote:
rgheck wrote:
Do something to lyx2lyx to cause a syntax error. Now try to open a file
that needs converting. BOOM!
Does this help? Of course inset_iterator_begin() should not crash to begin
with.
Author:
Stefan Schimanski wrote:
Hi!
A small progress report of the patch: I made it very generic now and am
on the way to implement completion for the text mode as well. You can
see a tiny screencast here:
http://www.youtube.com/watch?v=vf3zSa9x2F4
That is impressive stuff Stefan!
Abdel.
Hi!
A small progress report of the patch: I made it very generic now and
am on the way to implement completion for the text mode as well. You
can see a tiny screencast here:
http://www.youtube.com/watch?v=vf3zSa9x2F4
Stefan
Am 06.02.2008 um 00:49 schrieb Stefan Schimanski:
Hi!
I was
I noted that postats.py does not work for me, unless I manually set LC_ALL
to 'C' before running make i18n.inc (else, the msgmerge messages are in
German).
Jürgen
On Tue, Feb 19, 2008 at 12:21:08PM +0100, Jean-Marc Lasgouttes wrote:
> Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
>
> > Paul A. Rubin wrote:
> >
> >> Done (#4561).
> >
> > I just committed a fix to both trees, since the fix was so obvious.
>
> So obvious... Not me me at least :) Where is t
On Tue, Feb 19, 2008 at 11:12:37AM +0100, Abdelrazak Younes wrote:
> Pavel Sanda wrote:
1. more workareas handling needs to be added (toolbars toggling wont
work with them now)
>> this seems to be tricky. Abdel, would it be complicated to have one
>> toolbars
>> info per workarea?
>
> Y
On Tue, Feb 19, 2008 at 08:32:30AM +0100, Abdelrazak Younes wrote:
> rgheck wrote:
>> Do something to lyx2lyx to cause a syntax error. Now try to open a file
>> that needs converting. BOOM!
>
> Does this help? Of course inset_iterator_begin() should not crash to begin
> with.
>
> Author: younes
>
Jean-Marc Lasgouttes wrote:
> - insert a Section heading
>
> - select the whole paragraph
>
> - insert a branch
>
> Result: the outside paragraph that contains the branch is in Section
> paragraph
This is easy to fix actually (it's fixed in trunk). I even had a fix ready,
but then I remembered
"Bo Peng" <[EMAIL PROTECTED]> writes:
>> This is applied to trunk now.
>
> Seems to be working. Thank you very much for fixing this annoying bug.
It was my most annoying bug in 1.5, but there is a second one I've got
to nuke:
- insert a Section heading
- select the whole paragraph
- insert a b
> This is applied to trunk now.
Seems to be working. Thank you very much for fixing this annoying bug.
BTW, opening user's guide and other help documents crashes lyx/trunk.
Bo
Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
> \def\sqint{\square\kern-17mu\int\kern6mu} esint
> or
> \def\idotsint{\int\kern-3mu\cdots\kern-3mu\int} amsmath
>
> for instance
Doh.
JMarc
Jean-Marc Lasgouttes wrote:
>> I happened to know that this file is responsible,
>
> This I knew too.
I would have been surpised if not.
>> and got the syntax from the existing entries.
>
> I cannot find an entry with \def and a require field...
\def\sqint{\square\kern-17mu\int\kern6mu} esint
> >> i need to call some kind of redraw when comming back from fullscreen mode
> >> (scrollbar needs some update and probably recomputation).
> >
> > I don't really understand why you need that as a redraw should be triggered
> > automatically following a resize event (which you get if you come ba
>> i need to call some kind of redraw when comming back from fullscreen mode
>> (scrollbar needs some update and probably recomputation).
>
> I don't really understand why you need that as a redraw should be triggered
> automatically following a resize event (which you get if you come back from
>
Pavel Sanda wrote:
this seems to be tricky. Abdel, would it be complicated to have one
toolbars
info per workarea?
Yes, very complicated and not good. The toolbars are part of a main window
i.e. GuiView. But perhaps you mean one toolbar by view?
yes, view is what i actually wanted.
OK.
I
Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
> I happened to know that this file is responsible,
This I knew too.
> and got the syntax from the existing entries.
I cannot find an entry with \def and a require field...
JMarc
Jean-Marc Lasgouttes wrote:
> So obvious... Not me me at least :) Where is the syntax of the symbols
> file somehow described. It looks random to me...
I happened to know that this file is responsible, and got the syntax from
the existing entries.
Jürgen
>> this seems to be tricky. Abdel, would it be complicated to have one
>> toolbars
>> info per workarea?
>
> Yes, very complicated and not good. The toolbars are part of a main window
> i.e. GuiView. But perhaps you mean one toolbar by view?
yes, view is what i actually wanted.
>In which case
Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
> Paul A. Rubin wrote:
>
>> Done (#4561).
>
> I just committed a fix to both trees, since the fix was so obvious.
So obvious... Not me me at least :) Where is the syntax of the symbols
file somehow described. It looks random to me...
JMarc
Paul A. Rubin wrote:
> Done (#4561).
I just committed a fix to both trees, since the fix was so obvious.
Jürgen
Pavel Sanda wrote:
1. more workareas handling needs to be added (toolbars toggling wont work
with them now)
this seems to be tricky. Abdel, would it be complicated to have one toolbars
info per workarea?
Yes, very complicated and not good. The toolbars are part of a main
window i.e. GuiView.
>> 1. more workareas handling needs to be added (toolbars toggling wont work
>> with them now)
this seems to be tricky. Abdel, would it be complicated to have one toolbars
info per workarea? i seem to be lost in gui hierarchy - why there are two
nested loops in fullscreen initialization - one ove
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
> This is something that has annoyed me for a looong time, and I have to
> thank uwe for making me look at it finally. I think the following
> patch is correct, but since I know how fragile this code is, I prefer
> to post it first.
>
> The only thi
33 matches
Mail list logo
