Pavel Sanda wrote:
> btw when do you plan to release it?
There is one outstanding issue which should be fixed, since it potentially
results in really bad dataloss:
http://bugzilla.lyx.org/show_bug.cgi?id=5813
Apart from that, we are ready.
Unfortunately, I'm totally blocked by real work, so I c
Jürgen Spitzmüller wrote:
> strings to translate, please wait for 1.6.3.
btw when do you plan to release it?
pavel
Pavel Sanda wrote:
> just found box and note insets do not have open/close item in their
> context menu. i'll add them unless comebody complains.
You can submit to 1.6.2svn, if exactly these strings are already in the *.po
files (i.e., including the accelerators). If the commit generates new
stri
>just found box and note insets do not have open/close
>item in their context menu. i'll add them unless comebody
>complains.
And if you right-click on the text in an open note or box or inside a
table, you should get the edit menu + inset menu.
>Pavel
Vincent
rgheck wrote:
If I open (say) the Customization manual and immediately right-click on
a charstyle, then Toggle Inset line is disabled. It remains that way
through further right-clicking. If I double click into the inset,
though, then it works.
Hello,
I am very pleased with how you guys end
rgheck wrote:
> If I open (say) the Customization manual and immediately right-click on
> a charstyle, then Toggle Inset line is disabled. It remains that way
> through further right-clicking. If I double click into the inset,
> though, then it works.
This is strange. next-inset-toggle is disabled
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> Maybe yes but at least that's still a benefit for me if I am to do
> something :-).
I did not say it was a completely bad motivation :)
JMarc
Jean-Marc Lasgouttes wrote:
I do not say that expandToc/expandToc2 are a model of good coding. But
they are more complicated, since the number of submenus is decided
dynamically depending on their complexity (i.e. subsections are not in
a submenu if not needed). I am not sure that it is necessary
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> I guess 'not bad' means good here ;-)
Yes.
> Algorithms are algorithms, why do you want to recreate them? FWIW,
> I've created the TocModel class for Navigation purpose and it uses
> approximatively the same algorithm as in expandToc()/expandToc2(
Jean-Marc Lasgouttes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
I thought a bit more about that. Instead of QMenu, I'd generate a list
of Actions instead. A QMenu can be automatically constructed with
that. The idea is that this would get us closer to my idea of "Action
unification" (
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> I thought a bit more about that. Instead of QMenu, I'd generate a list
> of Actions instead. A QMenu can be automatically constructed with
> that. The idea is that this would get us closer to my idea of "Action
> unification" (menu and toobar actions
Jean-Marc Lasgouttes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
I would of course keep all the algorithms. I am just thinking of
dropping all classes and variable that have a Qt equivalent.
Why not. Remember that you need to have a menu with all the
uninterpreted things, and another
Jean-Marc Lasgouttes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
First thing is to define new menu types for Context menu in addition
to menu bar. I guess this will involve a modification of stdmenu.inc
as well as MenuBackend. I don't know really what is needed as I get
lost in this me
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> First thing is to define new menu types for Context menu in addition
> to menu bar. I guess this will involve a modification of stdmenu.inc
> as well as MenuBackend. I don't know really what is needed as I get
> lost in this menu business every times
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> I would of course keep all the algorithms. I am just thinking of
> dropping all classes and variable that have a Qt equivalent.
Why not. Remember that you need to have a menu with all the
uninterpreted things, and another one which is the raw menu. Y
On Fri, Dec 28, 2007 at 07:38:48PM +0100, Abdelrazak Younes wrote:
> Jean-Marc Lasgouttes wrote:
>> Abdelrazak Younes <[EMAIL PROTECTED]> writes:
>>> Dear all,
>>>
>>> As Juergen already uncovered I am pleased to announce preliminar basic
>>> support for context menus in trunk. Still a lot of ui po
Jean-Marc Lasgouttes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Dear all,
As Juergen already uncovered I am pleased to announce preliminar basic
support for context menus in trunk. Still a lot of ui polishing to do
before this feature is really useful. Right now we only get the 'edit
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> Dear all,
>
> As Juergen already uncovered I am pleased to announce preliminar basic
> support for context menus in trunk. Still a lot of ui polishing to do
> before this feature is really useful. Right now we only get the 'edit'
> menu when right cl
On Thu, Oct 11, 2007 at 11:10:50AM -0400, Richard Heck wrote:
>
> I have a friend I'm converting to LyX, and he likes it but misses the
> right-click context menu that is common in other apps. Has previous
> thought been given to this?
>
> rh
LyX was not a very GUI-ish application for most of
Richard Heck wrote:
I'd add Copy, Cut, Paste, as these are very standard.
you'd only want these when there is a selection
if there is a selection the popup should show edit stuff like this and
text attributes
whereas if there is no selection the popup should show stuff that is
related to t
Jean-Marc Lasgouttes wrote:
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
To show more precisely what I have in mind, have a look at the
following patch. It adds a new "Context menu" top-level menu, which
contains some entries from both the edit menu and the edit>table menu.
The entries o
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
> We could have in stdmenu.inc a menu named "contextmenu" that contains
> a bunch of OptItem entries. Then only the entries that make sense at a
> given place will be present.
To show more precisely what I have in mind, have a look at the
following
shouldn't this be inset specific?
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> Lots of thought... like often in LyX ;-) But so far no initial plan
> for implementation. Should be rather easy to implement though at Qt
> level. The question is how to implement the backend for the menu
> contents. One simple solution would be to j
Richard Heck wrote:
I have a friend I'm converting to LyX, and he likes it but misses the
right-click context menu that is common in other apps. Has previous
thought been given to this?
Lots of thought... like often in LyX ;-) But so far no initial plan for
implementation. Should be rather
25 matches
Mail list logo
