On Mac, I get the following error:
Making all in qt4
/Users/bennett/lyx/qt-4.3-install///bin/moc -o DialogView_moc.cpp
DialogView.h
DialogView.h:0: Warning: No relevant classes found. No output generated.
/Users/bennett/lyx/qt-4.3-install///bin/moc -o DockView_moc.cpp
DockView.h
DockView.h:
> And maybe additional information on mouse hover?
That leads to the attached patch (against 1.5.x). It displays
CharStyle: type when this inset is enterred or hovered.
Jose?
Bo
Index: src/insets/InsetCharStyle.h
===
--- src/insets/I
On Sat, Sep 29, 2007 at 03:32:34PM -0500, Bo Peng wrote:
> > But the information what kind of char style this is ois still available
> > somewhere? In the status line perhaps when the cursor is inside the
> > style inset perhaps?
>
> I think the font used in such an inset is (almost) enough to tel
Some results on running 'g++ -E | wc -l' with the appropriate
includes/defines and a single #include in a compilation unit:
boost/signal.hpp: 62141 (!)
boost/signals/trackable.hpp : 40849
boost/tokenizer.hpp : 39490
boost/iterator/indirect_
> But the information what kind of char style this is ois still available
> somewhere? In the status line perhaps when the cursor is inside the
> style inset perhaps?
I think the font used in such an inset is (almost) enough to tell us
what kinds of charstyle it is. If someone really wants to know
On Sat, Sep 29, 2007 at 03:15:27PM -0500, Bo Peng wrote:
> Dear all,
>
> Do you like the attached patch? It stops InsetCharStyle from
> displaying a initial label, and removes the additional spaces above
> and below this inset. I have attached two screenshots to demonstrate
> the effect.
>
> The
On Thu, Sep 06, 2007 at 01:34:16AM +, Angus Leeming wrote:
> Andre Poenitz <[EMAIL PROTECTED]> writes:
> > Summary:
> >
> > Before merging controller and view for the "About" dialog:
> >
> >315 frontends/controllers/ControlAboutlyx.lo
> > 88760 frontends/controllers/ControlAboutlyx.o
>
Since I got no response from the marvosym package maintainer, g-brief won't be usable for MiKTeX and
TeXLive 2007 users. I therefore added a warning to the templates to switch to g-brief2.
What do you think?
regards Uwe
Index: g-brief-de.lyx
=
Helge Hafting wrote:
A really strange test:
I compiled LyX, ran it, and couldn't type fast.
If I press down 10 keyboard keys at the same time, then I get
instant response (10 lowercase letters) in xterm. LyX outputs the
characters one by one! I could type a little faster than LyX writing
"test" o
A really strange test:
I compiled LyX, ran it, and couldn't type fast.
If I press down 10 keyboard keys at the same time, then I get
instant response (10 lowercase letters) in xterm. LyX outputs the
characters one by one! I could type a little faster than LyX writing
"test" over and over, a good t
Is the attached patch OK to go into trunk?
regards Uwe
Index: stdmenus.inc
===
--- stdmenus.inc (revision 20593)
+++ stdmenus.inc (working copy)
@@ -332,6 +332,11 @@
Item "Protected Space|P" "space-insert protected"
Item "Inter
>> No, it's only an UI and LaTeX-output change.
>
> Will the current output be equivalent to the previous? Starting from the
> same document, of course.
Of course. But now the optional height argument is really optional: only used when needed or the
users says "use it" in the dialog. See also
Andre Poenitz wrote:
On Sat, Sep 29, 2007 at 11:27:56AM -0400, Richard Heck wrote:
and I'm getting times on the order of 125ms just for that one call.
I remember sending at least two messages to the list saying that calling
QClipboard::text() is an extremely expensive operation and should be
Bo Peng wrote:
> > This is nonsense. I do not argue in favour of removing bold, italic and
> > small caps. However, they should not be visible on top.
>
> But if there is no charstyle equivalence, why not?
No one implemented it.
> > > If you hide bold, why do not you hide noun, emph and others? D
Richard Heck wrote:
Abdelrazak Younes wrote:
I can't reproduce the selection problem (because I'm not on X11) but
could you please apply this patch and report if the slowness problem
still persist?
Unfortunately, that did not help. But here are some more things I've
found out.
First, the slo
> This is nonsense. I do not argue in favour of removing bold, italic and small
> caps. However, they should not be visible on top.
But if there is no charstyle equivalence, why not?
> > If you hide bold, why do not you hide noun, emph and others? Do
> > not tell me they are using charstyles.
>
>
On Sat, Sep 29, 2007 at 11:27:56AM -0400, Richard Heck wrote:
> Abdelrazak Younes wrote:
> >I can't reproduce the selection problem (because I'm not on X11) but
> >could you please apply this patch and report if the slowness problem
> >still persist?
> Unfortunately, that did not help. But here a
Bo Peng wrote:
> > C-b works here.
>
> Why do not you remove C-b as well if you decide to hide it? If you
> have C-b, why cannot you have Toggle bold menu item (and toolbar
> icon)?
This is nonsense. I do not argue in favour of removing bold, italic and small
caps. However, they should not be vi
Abdelrazak Younes wrote:
I can't reproduce the selection problem (because I'm not on X11) but
could you please apply this patch and report if the slowness problem
still persist?
Unfortunately, that did not help. But here are some more things I've
found out.
First, the slowness is coming durin
> it would be good to put link to this thread/mail somewhere in comment of the
> code.
Done.
Uwe
> > I do not get it. You say, B should be used so I remove A, but B does
> > not exist yet ! Right mow, there is no easy way to input either
> > \textbf or \strong (textstyle) and you think there is no problem?
>
> C-b works here.
Why do not you remove C-b as well if you decide to hide it? If you
Abdelrazak Younes wrote:
> As you like but please note that testing is rather simple in this case:
> just put lots of inset nested one in each other and look for painting
> problems.
> Attached an updated patch that remove even more code :-) but is not
> fully working within inset... yet!
Please n
Abdelrazak Younes wrote:
Andre Poenitz wrote:
On Sat, Sep 29, 2007 at 09:31:22AM -0400, Richard Heck wrote:
Andre Poenitz wrote:
Can anybody think of a reason why ControlCharacter has a Font* member,
and not a Font?
I think it must be connected with these lines:
bool ControlCharacter::initi
Andre Poenitz wrote:
On Sat, Sep 29, 2007 at 09:31:22AM -0400, Richard Heck wrote:
Andre Poenitz wrote:
Can anybody think of a reason why ControlCharacter has a Font* member,
and not a Font?
I think it must be connected with these lines:
bool ControlCharacter::initialiseParams(string const &
On Sat, Sep 29, 2007 at 09:31:22AM -0400, Richard Heck wrote:
> Andre Poenitz wrote:
> >Can anybody think of a reason why ControlCharacter has a Font* member,
> >and not a Font?
> >
> I think it must be connected with these lines:
> bool ControlCharacter::initialiseParams(string const &)
> {
> //
I am confused. In a .lyx file, we have
emph \emph on/default
bold \series bold/default
code \family typewriter
noun \noun on
So you want to define charstyle bold, emph, code and noun and lyx2lyx
everything to something like
\begin_inset CharStyle Emph
blah
end_inset
Bo
José Matos wrote:
On Saturday 29 September 2007 12:29:00 [EMAIL PROTECTED] wrote:
I'd say we wait with this until 1.5.2 is out and do
the change for 1.5.3. Then this has enough time for testing.
+1
+1
JMarc
PS: Abdel please don't be discouraged with this. If you finish the patch
soo
José Matos wrote:
On Saturday 29 September 2007 11:36:29 Martin Vermeer wrote:
That's why we need first of all toolbar buttons for emph,
strong, code and noun -- _as charstyles_.
(remember bold = strong, usually)
I agree. It is not difficult to implement, what is missing is the lyx2ly
Andre Poenitz wrote:
Can anybody think of a reason why ControlCharacter has a Font* member,
and not a Font?
I think it must be connected with these lines:
bool ControlCharacter::initialiseParams(string const &)
{
// Do this the first time only.
if (!font_.get())
font_.reset(new Font(Font::ALL
On Saturday 29 September 2007 11:12:55 Andre Poenitz wrote:
> Objections?
>
> Andre'
Not from me. :-)
--
José Abílio
On Saturday 29 September 2007 12:29:00 [EMAIL PROTECTED] wrote:
> > I'd say we wait with this until 1.5.2 is out and do
> > the change for 1.5.3. Then this has enough time for testing.
>
> +1
+1
> JMarc
PS: Abdel please don't be discouraged with this. If you finish the patch
soon I(/we) wo
On Saturday 29 September 2007 11:36:29 Martin Vermeer wrote:
> That's why we need first of all toolbar buttons for emph,
> strong, code and noun -- _as charstyles_.
>
> (remember bold = strong, usually)
I agree. It is not difficult to implement, what is missing is the lyx2lyx
part, right?
> -
> I'd say we wait with this until 1.5.2 is out and do
> the change for 1.5.3. Then this has enough time for testing.
+1
JMarc
> Jean-Marc, would that be the right patch?
Yes.
JMarc
On Fri, Sep 28, 2007 at 02:20:39PM -0500, Bo Peng wrote:
> Jurgen:
>
> Would you agree to add following menu items (bold, emph, underline,
> code) and toolbar icon (bold) to 1.5.2?
>
> John and Richard agree with this change. Basically speaking, although
> we should encourage the use of the text
On Fri, Sep 28, 2007 at 11:14:10AM -0400, Richard Heck wrote:
> John Levon wrote:
> > On Fri, Sep 28, 2007 at 01:03:38AM -0500, Bo Peng wrote:
> >
> >> I helped a friend upgrade his lyx 1.3.7 to 1.5.1, and waited for his
> >> praises while he played with the new version
> >>
> > It's b
Can anybody think of a reason why ControlCharacter has a Font* member,
and not a Font?
Andre'
I'd like to move the ChangeLog files to a place where they do not
produce any false positives when grepping around in the sources.
I'd suggest
src/ChangeLog -> development/changelogs/ChangeLog.src
src/mathed/ChangeLog -> development/changelogs/ChangeLog.src.mathed
or similar, plus a short READ
Abdelrazak Younes wrote:
so letting the depend on a validate would be better
Agreed. Could you do it?
will have a look when i find some time
Jürgen Spitzmüller wrote:
Abdelrazak Younes wrote:
Here is a better patch. There are some issues when the text is too close
to the right edge of an inset. But these issues are already in 1.5svn
and are not brought by my patch.
While I'm very much in favour of this change, I'm reluctant to shov
Martin Vermeer wrote:
On Fri, Sep 28, 2007 at 09:52:29AM +0200, Abdelrazak Younes wrote:
Abdelrazak Younes wrote:
Helge Hafting wrote:
Arrange one paragraph with 25 lines.
Type a string og W's in the next paragraph. The W's comes out with
great speed until this second paragraph needs to linew
Bo Peng wrote:
> Would you agree to add following menu items (bold, emph, underline,
> code) and toolbar icon (bold) to 1.5.2?
No. I think this is the wrong direction.
Jürgen
Abdelrazak Younes wrote:
> Here is a better patch. There are some issues when the text is too close
> to the right edge of an inset. But these issues are already in 1.5svn
> and are not brought by my patch.
While I'm very much in favour of this change, I'm reluctant to shove it in so
short before
43 matches
Mail list logo
