I am trying to solve bug 3529 and things seems to be weird. I check if the
modelItem for the TOC entry is passed correctly. For kernel/model to view
side everything seems OK. Apparently the problem is in paint mechanism of
treeView. I did every possible trick to make the treeview repaint
, Abdelrazak Younes [EMAIL PROTECTED] wrote:
Ozgur Ugras BARAN wrote:
Attached patch solves two TOC dialog bugs 3528 and 3534. Can smb
review (Abdel?, Juergen?, John?) and commit it (Jose?)
I need an explanation (which will go in the svn log).
Abdel.
On 5/10/07, Abdelrazak Younes [EMAIL PROTECTED] wrote:
Ozgur Ugras BARAN wrote:
This bug exists before the patch. lof and lot has never been updated
correctly.
Yes, I noticed that afterwards, sorry for accusing you :-)
I did not felt accused, sir.. :-)
The problem is TocBackend::item
it and inform you today. Maybe we need that labyrinth at the
end.. :-)
Ugras
On 5/10/07, Abdelrazak Younes [EMAIL PROTECTED] wrote:
Ozgur Ugras BARAN wrote:
Attached patch solves two TOC dialog bugs 3528 and 3534. Can smb
review (Abdel?, Juergen?, John?) and commit it (Jose?)
I took the time
Attached trivial patch solves Bug 3377 (In insert graphic window: canceling
open dialog erases entry in text box). This bug is not Mac specific, but
exist in Linux. (should exist in other OSes).
Please may somebody apply the patch?
regards,
ugras
--- QGraphicsDialog.cpp (revision 18067)
+++
Abdel, I am afraid your patch introduces a couple of problems:
In toc combo number of entries is multiplied when update button is pressed.
(typeCO has entries tables/figure/TOC/tables/figure/TOC/. depending
on how many times you pressed the button.)
eventually, when older TOC is chosen
for the compliments, sir :)
Ugras
PS. I guess it is safe to close the bug 3377. I couldn't find a bugzilla
entry for QExternal bug.
On 5/11/07, Abdelrazak Younes [EMAIL PROTECTED] wrote:
Ozgur Ugras BARAN wrote:
Attached trivial patch solves Bug 3377 (In insert graphic window:
canceling open dialog erases
Thanks, Uwe.
On 5/12/07, Uwe Stöhr [EMAIL PROTECTED] wrote:
PS. I guess it is safe to close the bug 3377.
Done.
regards uwe
Don't worry about it. I will apply it later, if I can get svn access.
Ugras
On 5/14/07, Abdelrazak Younes [EMAIL PROTECTED] wrote:
Abdelrazak Younes wrote:
Ozgur Ugras BARAN wrote:
Thanks, sir. But I have one more patch. I had a look at the usage of
the browse function through lyx, and saw
Dear JMarc
I am in Lyx development for nine -ten months and wish to continue for
developing/ debugging for Lyx. I believe, I understood the development
practices of lyx community well and I wish to gain svn commit access in
order not to disturb other developers to commit in my place and also my
When demote button is pressed too many times, TOC item dissapears from
the toc dialog, since it is no longer numbered. Hence, promoting back
to the original state from TOC dialog is not possible. Attached patch
is a way of correcting this behaviour. It simply prevents demoting the
item more than
another idea?
Ugras
On 5/14/07, Edwin Leuven [EMAIL PROTECTED] wrote:
shouldn't the proper enabled flag be set in the kernel
(bufferview.cpp?) instead of putting this in the controller?
Ozgur Ugras BARAN wrote:
When demote button is pressed too many times, TOC item dissapears from
the toc
On 5/14/07, Andre Poenitz [EMAIL PROTECTED] wrote:
On Mon, May 14, 2007 at 08:19:59PM +0200, Ozgur Ugras BARAN wrote:
+bool const ControlToc::allowDemoteCurrentItem(size_t type) const
+{
+ return ((kernel().buffer().params().tocdepth -
(*getCurrentTocItem(type)).depth() + 1)0
Attached patch solves TOC bug 3529 for Qt-4.3-pre. The problem was
blocked selectionchanged signal for selectionModel prevents correct
repainting. I have no idea whether this patch works for qt-4.2 or not.
Therefore, please somebody test it?
verify, commit, enjoy :)
Abdel, I have asked
I can confirm that patch also works for qt 4.2.0.
On 5/14/07, Ozgur Ugras BARAN [EMAIL PROTECTED] wrote:
Attached patch solves TOC bug 3529 for Qt-4.3-pre. The problem was
blocked selectionchanged signal for selectionModel prevents correct
repainting. I have no idea whether this patch works
:
Ozgur Ugras BARAN wrote:
Attached patch solves TOC bug 3529 for Qt-4.3-pre. The problem was
blocked selectionchanged signal for selectionModel prevents correct
repainting. I have no idea whether this patch works for qt-4.2 or not.
Therefore, please somebody test it?
Works for me (qt 4.2.3
This one should be better in behaviour, but ugly as hell.
Would you please test it, again?
regards,
Ugras
On 5/15/07, Ozgur Ugras BARAN [EMAIL PROTECTED] wrote:
Oh, there is another problem, now. Please do not apply patch. When you
change the selection with mouse, cursor goes
-send the patch with your comments applied, after coding the
proposed solution of Abdel.
Ugras
On 5/15/07, Jürgen Spitzmüller [EMAIL PROTECTED] wrote:
Ozgur Ugras BARAN wrote:
strange.. nobody complained the code below..
+
moveInTB-setEnabled(form_-allowDemoteCurrentItem(typeCO-currentIndex
Correct bug 3529-(TOC widget does not select the current
part/section/subsection correctly) by replacing blockSignal()
directives for tocTV- selectionModel() with disconnect and reconnect
relevant signal.
Thanks Jurgen, Abdel.
ugras
On 5/15/07, Jürgen Spitzmüller [EMAIL PROTECTED] wrote:
Umm. let me check, then. How can I enable stdlib-debug ?
Ugras
On 5/15/07, Jürgen Spitzmüller [EMAIL PROTECTED] wrote:
Ozgur Ugras BARAN wrote:
I can't reproduce this. I even tried inline-in command from buffer.
One point is, if you have older versions of toc stuff (pre 18265) and apply
place for this
IMHO.
regards,
Ugras
On 5/15/07, Helge Hafting [EMAIL PROTECTED] wrote:
Ozgur Ugras BARAN wrote:
It is strictly dialog related problem, therefore I should have put
some function in controller. The place for a flag like demotionEnabled
maybe in TocBackend, but this doesn't remove
This small patch prevents LOF, LOT always selects the last entry.
LOT/LOF still does not follow the cursor, yet, but for this, we need
serious update in TocBackend.
Do you think this solves bug 3183?
Hopefully, last patch for toc stuff.
here is svn log message:
*
Gosh.. this takes hours to link..
I have tested, but no crashes.. sorry. I will test it again tonight.
regards,
ugras
On 5/15/07, Jürgen Spitzmüller [EMAIL PROTECTED] wrote:
Ozgur Ugras BARAN wrote:
How can I enable stdlib-debug ?
--enable-stdlib-debug
Jürgen
I guess I'll leave implementation of this to others for the moment. If
nobody take care about this problem, then it would be a good point for
me to learn lyx internals.
thanks a lot for taking care of the patch, Abdel.
Ugras
On 5/15/07, Abdelrazak Younes [EMAIL PROTECTED] wrote:
Ozgur Ugras
On 5/15/07, Jürgen Spitzmüller [EMAIL PROTECTED] wrote:
Ozgur Ugras BARAN wrote:
Gosh.. this takes hours to link..
I have tested, but no crashes.. sorry. I will test it again tonight.
Maybe my system is pickier (64bit). Anyway, seems your other (TOC backend)
patch is getting more sympathy
Is there a place that I can order the book lyx developer's handbook
vol:1 :101 ways o write svn logs :-)
On 5/15/07, Abdelrazak Younes [EMAIL PROTECTED] wrote:
Ozgur Ugras BARAN wrote:
This small patch prevents LOF, LOT always selects the last entry.
LOT/LOF still does not follow the cursor
There is no bugzilla entry. I found it from mailing list..
http://marc.info/?l=lyx-develm=117880601303849w=2
On 5/15/07, Jürgen Spitzmüller [EMAIL PROTECTED] wrote:
José Matos wrote:
I agree.
+1
Committed. Was there a bugzilla entry about this? I thought so, but I
don't
find it now.
Glossaries has. See Extended.lyx section 3.3.
On 5/15/07, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:
On Tue, 15 May 2007, José Matos wrote:
On Sunday 13 May 2007 20:26:49 [EMAIL PROTECTED] wrote:
I would if I could - I have only used LyX once in the last year or so,
which means I have no
when selecting LOF/ LOT for User Guide assertion triggered. Here is debug info:
#0 0x40c7c327 in raise () from /lib/tls/libc.so.6
#1 0x40c7db75 in abort () from /lib/tls/libc.so.6
#2 0x085ffb47 in lyx::support::abort () at abort.cpp:25
#3 0x0807339a in boost::assertion_failed
No there were no assertion. Actually, assertion is triggered due to a
problem introduced by two previous patches (today?) that solves
LOF/LOT selection issue and solving this bug.
Abdel, if you will not have time to solve this, would you revert
LOT/LOF patch and apply my workaround? We are too
The patch works well for child documents. I should also report that,
it works for algorithms list.
On 5/16/07, Ozgur Ugras BARAN [EMAIL PROTECTED] wrote:
No there were no assertion. Actually, assertion is triggered due to a
problem introduced by two previous patches (today?) that solves
LOF/LOT
For me, another candidate for multiple glossaries implementation in lyx.
Supporting all available package will not be as easy as it was in multiple
indices..
I really like to hear how would you rate it? Especially compared to gloss
and glossary.
Documentation is awful, though. For a standard
On 5/17/07, Jürgen Spitzmüller [EMAIL PROTECTED] wrote:
Ozgur Ugras BARAN wrote:
For me, another candidate for multiple glossaries implementation in lyx.
Supporting all available package will not be as easy as it was in
multiple
indices..
I really like to hear how would you rate it?
From
Compile and works fine here.
Looks pretty solid at the first glance. Thanks Jose (and everybody)
Ugras
On 5/18/07, José Matos [EMAIL PROTECTED] wrote:
On Thursday 17 May 2007 1:05:33 pm José Matos wrote:
Hi all,
I will be busy until tonight, when I intend to release beta 3.
I have
Attached patch sorts listings inset params, and hence solves bug 3639.
Please somebody review and apply the patch.
I could also sort the listings_param_table[] entries manually, but I find
this way easier (and more guaranteed).
regards,
ugras
Index: insets/InsetListingsParams.cpp
On 5/25/07, Bo Peng [EMAIL PROTECTED] wrote:
On 5/25/07, Ozgur Ugras BARAN [EMAIL PROTECTED] wrote:
Attached patch sorts listings inset params, and hence solves bug 3639.
Please somebody review and apply the patch.
1. table[idx].name is char * so != is better because no conversion
would
5. I would appreciate it you can also implement
?xx == all parameters that contains xx. That is to say, ?placement
would show floatplacement. style would show all style related
parameters. You can also consider xx == all parameters that
prefixIs(xx), and other parameters that contains(xx).
I
variable that we compare with empty string is of type const char, not
string.. A possible way of doing it would be:
!string(listings_param_table[idx].name).empty()
But it is more difficult to read, IMHO.
Ugras
Use string::empty() instead.
Abdel.
Ah... OK, I didn't get the thing.
Why don't you use string in the first place (in listings_param_table) ?
But it is more difficult to read, IMHO.
Yes. You could as well use:
if (listings_param_table[idx].name[0])
:D I guess, I remember this from hilarious web site how to write an
Ah, yes I forgot contains.. I'll fix it.
Shall I also make the conversion to docstring for every string and
char* I use in parValidator::parValidator?
ugras
On 5/26/07, Bo Peng [EMAIL PROTECTED] wrote:
Indeed, I am agree with Alfredo on this issue. Therefore I have
attached another patch
Attached is a patch for a small feature that Bo asked for. It simply
filters InsetListingsParams when the text in the corresponding dialog
is entered as ?string .
Sorry Bo, it is been a bit late, but I wait for all the changes for
the source file settles.
cheers
Ugras
Index:
On 5/30/07, Abdelrazak Younes [EMAIL PROTECTED] wrote:
Bo Peng wrote:
Sorry Bo, it is been a bit late, but I wait for all the changes for
the source file settles.
It can go in if you change .find() to contains(), and trim() suffix to
avoid problem with '?style ' etc (if it has not been
Otherwise, '?something ' will not match anything.
I guess, a trim is already applied. I updated the code for the situations '? something' and attached the patch. However, It does not cover the situations '?some thing'.
I used trim (), but since the string is already trimmed, rtrim() is
Attached patch corrects the buglet mentioned in the heading. I don't know
this quick hack has any consequences, so please somebody verify.
here is the svn log:
Fix unnumbered toc entries do not update automatically as you type.
regards,
Ugras
--- buffer_funcs.cpp-lyx-1.5.0rc1 2007-06-11
No, unfortunately not yet, Abdel. I guess I can get an access after the
release. So, I'll be glad if you can commit.
thanks,
Ugras
On 6/14/07, Abdelrazak Younes [EMAIL PROTECTED] wrote:
Juergen Spitzmueller wrote:
Ozgur Ugras BARAN wrote:
Attached patch corrects the buglet mentioned
I'd love to join, but apparently it won't be possible for me. Do you plan
any means of online access for hacking/ conferencing etc?
regards,
Ugras
Dear all,
At last I had time and play with the insetcommandparams as requested
on nomencl discussion. The new implementation keeps the contents and
options in lists. There is also support for individual parameters with
std::multimaps for future implementations. I haven't put any kind of
nested
Thanks a lot for reviewing the code. I will be more careful about
formatting. Here are some some answers:
- What I mean with the nested command support is something like:
\command {\command{content}}
An example is basic index command : \index { entry @{\myformat
{entry}} }. I see that
Yes, indeed. And also kdvi..
But I have another idea. Why don't we build a kde4 frontend and use
okular as embedded viewer. From usability point of view, I am not very
happy about xdvi windows popping around my desktop.
just an idea..
On 9/29/06, Neal Becker [EMAIL PROTECTED] wrote:
Since lyx
On 9/29/06, Abdelrazak Younes [EMAIL PROTECTED] wrote:
Helge Hafting wrote:
Ozgur Ugras BARAN wrote:
Yes, indeed. And also kdvi..
But I have another idea. Why don't we build a kde4 frontend and use
Can't see anything wrong with that - if you can find someone willing
to do the work
On 9/30/06, Georg Baum [EMAIL PROTECTED] wrote:
Am Freitag, 29. September 2006 10:01 schrieb Ozgur Ugras BARAN:
Thanks a lot for reviewing the code. I will be more careful about
formatting. Here are some some answers:
- What I mean with the nested command support is something like
A trivial (looking) patch to correct inset behavior, which is broken
with revision 15068. Without this patch, it is not possible to modify
an existing inset. All modifications processed as new index. (see
lyxfunc.C:1420)
I will be glad if somebody review the attached patch (and submit to
svn if
On 10/2/06, Georg Baum [EMAIL PROTECTED] wrote:
Ozgur Ugras BARAN wrote:
A trivial (looking) patch to correct inset behavior, which is broken
with revision 15068. Without this patch, it is not possible to modify
an existing inset. All modifications processed as new index. (see
lyxfunc.C
On 10/2/06, Georg Baum [EMAIL PROTECTED] wrote:
Ozgur Ugras BARAN wrote:
On 9/30/06, Georg Baum
[EMAIL PROTECTED] wrote:
This is a specialization, but I think we should keep it generic and
simple. InsetCommandParams would just store a number of parameters, and
the LaTeX command generated
Is there anyone working on multiple indices? If no, I'd like to start
working on it..
ugras
What do you have in mind?
well... multiple indices.. :)
JMarc
I plan to support splitidx, since it runs once on the file. So, it is
easier to handle. For example, I will not have to control the number
of indices, since the file write handle of Latex is limited.
However, splitidx is not
On 10/6/06, Jean-Marc Lasgouttes [EMAIL PROTECTED] wrote:
Ozgur == Ozgur Ugras BARAN [EMAIL PROTECTED] writes:
What do you have in mind?
Ozgur well... multiple indices.. :)
Like in ${x_i}_j$, for example? ;)
Ozgur I plan to support splitidx, since it runs once on the file. So,
Ozgur
On 10/6/06, Juergen Spitzmueller [EMAIL PROTECTED] wrote:
Ozgur Ugras BARAN wrote:
I plan to support splitidx, since it runs once on the file. So, it is
easier to handle. For example, I will not have to control the number
of indices, since the file write handle of Latex is limited
On 10/6/06, Georg Baum [EMAIL PROTECTED] wrote:
I think you misunderstood Jürgen. I believe he agrees with you.
oh, sorry :/
I have already sent the inetcommandparams changes. There is no change
for insetcommand from me.. Georg will improve it a little and submit
to svn, i guess.. This
On 10/6/06, Jean-Marc Lasgouttes [EMAIL PROTECTED] wrote:
Ozgur == Ozgur Ugras BARAN [EMAIL PROTECTED] writes:
What is wrong with multind.sty?
Ozgur nothing.. It just seems to me it is no fancier than index.sty..
Ozgur it also requires multiple makeindex runs, so I didn't see any
Ozgur
OK, what I meant is: if there will be more changes, it might be tricky for you
to maintain your tree (because there might be conflicting changes).
we are thinking in parallel then.. My only concern is for index.sty
there are four obligatory and one optional parameter. it will be hell
of a
well, quite a diff..
Giving a unique name for each params is a good idea. I didn't dare to
touch getOptions() etc. functions since they are called everywhere. I
see that you are bold enough. :) Thanks for the patch. I can
participate by getting rid of those get/set functions, if you wish. It
On 10/16/06, Georg Baum [EMAIL PROTECTED] wrote:
Ozgur Ugras BARAN wrote:
well, quite a diff..
Giving a unique name for each params is a good idea. I didn't dare to
touch getOptions() etc. functions since they are called everywhere. I
see that you are bold enough. :) Thanks for the patch
Here we go...
I can't compile for gtk no more due to fontmetrics issues, therefore
gtk frontend haven't been tested. I have tested it before the
corresponding svn commit, and it was working.
Ugras
On 10/17/06, Georg Baum [EMAIL PROTECTED] wrote:
It is in now.
Am Sonntag, 15. Oktober 2006
or later,
Ozgur Ugras BARAN
On 10/18/06, Georg Baum [EMAIL PROTECTED] wrote:
Georg Baum wrote:
Ozgur Ugras BARAN wrote:
Here we go...
I can't compile for gtk no more due to fontmetrics issues, therefore
gtk frontend haven't been tested. I have tested it before the
corresponding svn commit
By the way, I am starting to cleanup of get/set options/contents stuff
from Lyx code (excluding cite related files). However, tomorrow I am
going to holidays for a week. I will send you the patch as much as I
can finish. I can do the rest as I return back form holidays.
ugras
this diff removes most of the get/set command function calls from the
lyx code. I didn't touch cite stuff, as we decided.
On 10/19/06, Ozgur Ugras BARAN [EMAIL PROTECTED] wrote:
By the way, I am starting to cleanup of get/set options/contents stuff
from Lyx code (excluding cite related files
OK.. here we go.. The diff is against rev 15393. I made a couple of
updates after your commit.
ugras
On 10/20/06, Georg Baum [EMAIL PROTECTED] wrote:
Am Freitag, 20. Oktober 2006 10:39 schrieben Sie:
Sure.. Is there something similar that I can put instead of
Here is the updated nomencl files.
I will be away for the next week for holidays. Everybody enjoy Denmark..
Ugras
Stupid me, I forgot the file... :)
Here it is.
On 10/20/06, Ozgur Ugras BARAN [EMAIL PROTECTED] wrote:
Here is the updated nomencl files.
I will be away for the next week for holidays. Everybody enjoy Denmark..
Ugras
nom.tgz
Description: GNU Zip compressed data
On 11/2/06, Georg Baum [EMAIL PROTECTED] wrote:
Am Mittwoch, 1. November 2006 15:38 schrieb Ozgur Ugras BARAN:
By the way, I haven't seen nomencl commit in svn. Is something
missing, or do you need new diff?
Shortly after you went on holiday a freeze was announced, and nothing new
was allowed
Georg, I have updated your patch as you can see in the attachments. I
find this way easier. I think you will find it easier to review, too.
The draft documentations is also attached. I have written it
considering the new User Guide (UserGuideNV.lyx). Consider this as the
section 5.8.
And, don't
On 11/2/06, José Matos [EMAIL PROTECTED] wrote:
On Thursday 02 November 2006 12:15 pm, Georg Baum wrote:
Ozgur Ugras BARAN wrote:
Oh, this is bad news, since I have almost completed the multiple indices
stuff..
Do you have the code? :-)
Yes I do.. At least 80% of it :)) I can finish
On 11/4/06, Georg Baum [EMAIL PROTECTED] wrote:
Am Freitag, 3. November 2006 12:23 schrieb Ozgur Ugras BARAN:
Georg, I have updated your patch as you can see in the attachments. I
find this way easier. I think you will find it easier to review, too.
The draft documentations is also attached
Dear all,
Attached contains the diff and new files for the multiple index support.
- supports makeidx, index, splitidx styles
Glitches, TODOs
- no multind support, yet. (maybe never)
- when the multiple index support is switched off, all index entries
is merged to one, which can be easily
Attached is uglypatch/ugly for docbook glossaries export. Missing
features are:
- glossary entries in insets does not appear in glossary. I couldn't
find a chic way to include those.. (the current one is not so chic
anyway.. ) Any ideas??
- prefix is not working, therefore, you cannot change the
attached is the updated documentation. Added howto change nomlabelwidth.
ugras
Index: src/insets/insetnomencl.h
===
--- src/insets/insetnomencl.h (revision 15801)
+++ src/insets/insetnomencl.h (working copy)
@@ -53,8 +53,7 @@
void
This patch solves the crash while calling Qt4-TOC dialog in Linux /gcc-4.1
Can somebody commit it?
Index: frontends/qt4/TocModel.C
===
--- frontends/qt4/TocModel.C (revision 15811)
+++ frontends/qt4/TocModel.C (working copy)
@@
On 11/9/06, Georg Baum [EMAIL PROTECTED] wrote:
Ozgur Ugras BARAN wrote:
This patch solves the crash while calling Qt4-TOC dialog in Linux /gcc-4.1
Are you sure?
I have tested here and it works now..
The old code is perfectly valid for a std::map: if the element does not
exist
On 11/9/06, Abdelrazak Younes [EMAIL PROTECTED] wrote:
Ozgur Ugras BARAN wrote:
On 11/9/06, Georg Baum
What I understand is map::operator[] returns mapped_type, (for this
case a const_iterator). When you use operator = you try to
copy-construct with another const_iterator
No problem Ugras. Post your patch to the list and we'll manage.
Not sure this is a thing to say but have a nice journey ;-)
Abdel.
Thanks.. I will send postcards :-)
Ugras
following trivial looking patch corrects switching between different TOC types.
please somebody commits, if there is no problem.
Ugras
--- frontends/qt4/QTocDialog.C (revision 15836)
+++ frontends/qt4/QTocDialog.C (working copy)
@@ -104,6 +104,7 @@
void QTocDialog::on_typeCO_activated(int
As nobody had reviewed the multi-index patch, I guess we will postpone
it for 1.6 series, won't we?
Ugras
On 11/13/06, José Matos [EMAIL PROTECTED] wrote:
Hi all,
I am thinking about starting the procedures leading to the alpha
release. I
would like to ask now what do you think it
Following patch corrects some misbehavior in TOC dialog:
- When clicking on Toc insets, dialog switches to correct list.
- cursor goes to correct entry when clicked..
- some other fixes..
There is one strange problem, though. After clicking table toc
entries, cursor goes to correct table, but
weeks ago. I can clean
my working code and resend the patch.
Ugras
-- Forwarded message --
From: José Matos [EMAIL PROTECTED]
Date: Nov 15, 2006 2:29 PM
Subject: Re: Preparing for alpha release
To: lyx-devel@lists.lyx.org
On Monday 13 November 2006 3:18 pm, Ozgur Ugras BARAN wrote
I have two questions on the bug entries in file status15:
* The items in the treeview are editable
Do You mean they shouldn't be editable? Or when they edited the actual
entry in the document should be altered simultaneously?
* In the TOC dialog, the slider for altering the display level is
Thanks, Abdel..
Ugras
On 11/16/06, Abdelrazak Younes [EMAIL PROTECTED] wrote:
Ozgur Ugras BARAN wrote:
Following patch corrects some misbehavior in TOC dialog:
- When clicking on Toc insets, dialog switches to correct list.
- cursor goes to correct entry when clicked..
- some other fixes
On 11/16/06, Abdelrazak Younes [EMAIL PROTECTED] wrote:
Ozgur Ugras BARAN wrote:
I have two questions on the bug entries in file status15:
* The items in the treeview are editable
Do You mean they shouldn't be editable?
Yes, I think that's what he means.
Or when they edited the actual
I'll do it then. I don't know a one-liner, therefore, the code I'll
write may be a bit brutal..
you are warned, sir!!
Looks like you already are in your military shoes ;-)
Have fun,
SIR I WILL SIR!! ;-)
Abdel.
attached patch implement slider in TOC dialog.
I have implemented a getDepth function to get the model indices. In my
opinion, somebody should derive a new qvariant class for tocModelItem
which saves the string data and depth information. that will save the
depth calculation.
I'll be glad
On 11/16/06, Abdelrazak Younes [EMAIL PROTECTED] wrote:
Ozgur Ugras BARAN wrote:
Following patch corrects some misbehavior in TOC dialog:
- When clicking on Toc insets, dialog switches to correct list.
- cursor goes to correct entry when clicked..
- some other fixes..
I have tested
On 11/17/06, Abdelrazak Younes [EMAIL PROTECTED] wrote:
Ozgur Ugras BARAN wrote:
attached patch implement slider in TOC dialog.
I have implemented a getDepth function to get the model indices. In my
opinion, somebody should derive a new qvariant class for tocModelItem
which saves the string
On 11/17/06, Jean-Marc Lasgouttes [EMAIL PROTECTED] wrote:
Ozgur == Ozgur Ugras BARAN [EMAIL PROTECTED] writes:
Ozgur In short, there is something weird in cursor control for table
Ozgur floats. (other floats does not have the same problem).
Is it with table floats themselves, or table insets
On 11/17/06, Abdelrazak Younes [EMAIL PROTECTED] wrote:
Ozgur Ugras BARAN wrote:
attached patch implement slider in TOC dialog.
I have implemented a getDepth function to get the model indices. In my
opinion, somebody should derive a new qvariant class for tocModelItem
which saves the string
when iconpalette detached from the math dialog, the iconpalette widget
width may become too large to fit to the screen.
when detached resized to a too small size, icons overlap.
attached patch solves these problems.
I'll be glad if somebody reviews and commits the patch.
Ugras
p.s. Abdel,
)
should write tex2lyx code for version 254, and my code will reduce the
work that should be done, I guess.
I'll correct label and resend the patch. Documentation should follow.
Ugras
On 11/21/06, Georg Baum [EMAIL PROTECTED] wrote:
Am Dienstag, 21. November 2006 15:57 schrieb Ozgur Ugras BARAN
title should read I am a half-hero now :)
What is missing is:
linebreak code is working but there is no ui entry. therefore I skip
some parts of the code:
- there is no separate draw() function for linebreak, but it uses the
code from the newline. if you have any idea how to implement it,
Abdel, IMO, the last patch makes the TOC slider very useful.
Otherwise, TOC collapses everytime you change the section, which is
very annoying.
On 11/22/06, Bo Peng [EMAIL PROTECTED] wrote:
Sorry Ugras, but I don't have much time today to test your patch. I
suggest that you send again the
The code is extremely simple and easy to maintain, therefore, one
developer should be enough. Considering that I won't be available for
a couple of months, this one person cannot be me.
If you wish, you can add these features without ui entry, so, they are
accepted in lyx-1.5.0 file format and
Sorry for not writing earlier, but I was incredibly busy. I'll try to
write for all the conversation:
Herbert, I did not create the confusion on the insetpagebreak and
/newpage. It was already there. I wanted to implement /pagebreak, but
in order not to deepen confusion between versions, I
1 - 100 of 254 matches
Mail list logo
