By the way, I succeed to associate the .lyx files to the
application manually, but the files are still not displayed with the LyX
icon.
On 11/03/2024 13:02, LyX Ticket Tracker wrote:
#13041: Lyx Installation: No file association, view/update toolbar inactive
Oh, sorry, I forgot that: Windows 11 64 bit Pro.
On 11/03/2024 13:02, LyX Ticket Tracker wrote:
#13041: Lyx Installation: No file association, view/update toolbar inactive
---+-
Reporter: jcgarreau | Owner: lasgouttes
Type
On Sun, Feb 21, 2021 at 10:22:05PM +, V K wrote:
> I checked new find ??? it's much more comfortable than previous! One thing
> ??? after reaching end and continuing search from beginning by Enter active
> is not search area but text area, so hitting Enter deletes matched word and
> creates
On Sunday, February 21, 2021, 10:39:39 PM GMT+2, Pavel Sanda
wrote:
On Sat, Feb 20, 2021 at 03:35:04AM +, V K wrote:
> P. S. I can't compile lyx master in Manjaro (Arch derivative) anymore because
> of autoconf versions:
>
> Using autoconf (GNU Autoconf) 2.71
> This autoconf
TITLE ETC
INCLUDE CHILD, which has most of the content
BIBLIOGRAPHY
On viewing (usually, this is master-buffer-view, from the child), I
often get an "aux file not found" error. Re-doing the view usually
solves the problem.
Can you try to come up with a MWE?
Yes, but it's very
INCLUDE CHILD, which has most of the content
> BIBLIOGRAPHY
>
> On viewing (usually, this is master-buffer-view, from the child), I
> often get an "aux file not found" error. Re-doing the view usually
> solves the problem.
Can you try to come up with a MWE?
Jürgen
>
Hi, all,
I've been using current master for work lately, and I'm getting frequent
errors when viewing a fairly simple master-child document. The structure is:
TITLE ETC
INCLUDE CHILD, which has most of the content
BIBLIOGRAPHY
On viewing (usually, this is master-buffer-view, from the
Am 31.08.2020 um 17:45 schrieb Stephan Witt :
>
> Am 31.08.2020 um 17:25 schrieb Jean-Marc Lasgouttes :
>>
>> Le 30/08/2020 à 22:29, Stephan Witt a écrit :
>>> Am 30.08.2020 um 16:56 schrieb Pavel Sanda :
On Sun, Aug 30, 2020 at 03:58:34PM +0200, Stephan Witt wrote:
> 1. Tab Bar re
Le 31/08/2020 à 17:45, Stephan Witt a écrit :
The patch looks good. What happens on older versions of macOS. Do they all
implement that?
It was a shot in the dark. It works surprisingly well on Catalina and Mojave.
I’ll check it for 10.11.6 (El Capitan) next.
In principle it should be handled
Am 31.08.2020 um 17:25 schrieb Jean-Marc Lasgouttes :
>
> Le 30/08/2020 à 22:29, Stephan Witt a écrit :
>> Am 30.08.2020 um 16:56 schrieb Pavel Sanda :
>>>
>>> On Sun, Aug 30, 2020 at 03:58:34PM +0200, Stephan Witt wrote:
1. Tab Bar related - I don???t know how. Probably not w/o Qt-support f
Le 30/08/2020 à 22:29, Stephan Witt a écrit :
Am 30.08.2020 um 16:56 schrieb Pavel Sanda :
On Sun, Aug 30, 2020 at 03:58:34PM +0200, Stephan Witt wrote:
1. Tab Bar related - I don???t know how. Probably not w/o Qt-support for it.
showBar like in GuiWorkArea.cpp:1714 does not work?
It could b
Le 30/08/2020 à 15:58, Stephan Witt a écrit :
Am 30.08.2020 um 15:48 schrieb Jean-Marc Lasgouttes :
Le 30/08/2020 à 15:20, Stephan Witt a écrit :
commit 292799a4bd3fead1d631678a94a4eccc89193201
Author: Stephan Witt
Date: Sun Aug 30 15:34:44 2020 +0200
#11756 cleanup the view menu on
On Sun, Aug 30, 2020 at 03:58:34PM +0200, Stephan Witt wrote:
> 1. Tab Bar related - I don???t know how. Probably not w/o Qt-support for it.
showBar like in GuiWorkArea.cpp:1714 does not work?
It could be easily added as a part of ui-toggle lfun.
Pavel
--
lyx-devel mailing list
lyx-devel@lists.l
Sun Aug 30 15:34:44 2020 +0200
>>>#11756 cleanup the view menu on Mac
>>> Using US english desktop language LyX's Mac OS adds some items to
>>> the view menu:
>>>1. Show/Hide Tab Bar and
>>>2. Enter Full Screen
>>>
Am 30.08.2020 um 15:48 schrieb Jean-Marc Lasgouttes :
>
> Le 30/08/2020 à 15:20, Stephan Witt a écrit :
>> commit 292799a4bd3fead1d631678a94a4eccc89193201
>> Author: Stephan Witt
>> Date: Sun Aug 30 15:34:44 2020 +0200
>> #11756 cleanup the view menu on Ma
Le 30/08/2020 à 15:20, Stephan Witt a écrit :
commit 292799a4bd3fead1d631678a94a4eccc89193201
Author: Stephan Witt
Date: Sun Aug 30 15:34:44 2020 +0200
#11756 cleanup the view menu on Mac
Using US english desktop language LyX's Mac OS adds some items to the view menu:
s within a (master) document. This is very
> handy for looking and going through the whole list, or find related
> items such as all references to a label.
>
> However, often I would like to go to a particular item that I know is
> in a certain chapter, section or such. Some kind of
and going through the whole list, or find related items such
as all references to a label.
However, often I would like to go to a particular item that I know is in
a certain chapter, section or such. Some kind of "TOC view" would be
helpful.
One way to do this would be to add extr
On 2/19/20 3:11 AM, Sivan Frenkel wrote:
> Hi,
>
> Oddly, I have not been experiencing today the bug that I have reported
> yesterday, and the "view" button works fine. I will be in touch if I
> could figure out when and how this bug appears.
>
> Sorry for the mess.
Hi,
Oddly, I have not been experiencing today the bug that I have reported
yesterday, and the "view" button works fine. I will be in touch if I could
figure out when and how this bug appears.
Sorry for the mess.
Best, Sivan
Sivan Frenkel
Lecturer in Finance (Assistant Professor)
Col
Am Di., 18. Feb. 2020 um 11:23 Uhr schrieb Sivan Frenkel <
sivanfren...@yahoo.com>:
> Hi,
>
> I am using Win10 and have just updated from version 2.3.4 to 2.3.4.3. The
> update did solve the delay in saving, but seems to have created a new bug.
>
> The bug interfer
Hi,
I am using Win10 and have just updated from version 2.3.4 to 2.3.4.3. The
update did solve the delay in saving, but seems to have created a new bug.
The bug interferes with the use of "view" command. I am using Adobe Reader to
views PDF files (I am using Adobe Reader
On Tuesday, 28 May 2019 12.28.29 WEST Pavel Sanda wrote:
> Fine with me. P
+1
--
José Abílio
On Mon, May 27, 2019 at 11:41:48PM -0400, Richard Kimberly Heck wrote:
> I propose the attached changes to the View menu for 2.4. The big
> advantage, to my mind, is much more sensible shortcuts. The downside
> would be that we make such a change, of course, but I think it would be
&
I propose the attached changes to the View menu for 2.4. The big
advantage, to my mind, is much more sensible shortcuts. The downside
would be that we make such a change, of course, but I think it would be
worth it. I've also re-organized the menu to put what I would expect to
be more often
same
file is open in two windows AFAICS. Very very weird.
Perhaps it is also relevant that when the view is split into left and
right panes, the cursor is placed at the start of the document in the
right pane, not at its current position in the left pane.
I do not think this is relevant. But
On 08/10/2018 22:40, Andrew Parsloe wrote:
When the view is split into left and right windows, the cursor is placed
at the *start* of the document in the right window. I wonder if this is
the best place? Shouldn't it initially be placed at the same position as
in the left pane?
My patte
When the view is split into left and right windows, the cursor is placed
at the *start* of the document in the right window. I wonder if this is
the best place? Shouldn't it initially be placed at the same position as
in the left pane?
My pattern of work is to start LyX, open a documen
Jean-Marc Lasgouttes wrote:
> No it is not a recursion issue, but about knowing who asked for update. I
Then I did not get the underlying problem correctly, anyway proceed as you wish
;)
P
Le 2 novembre 2017 11:24:19 GMT+01:00, Pavel Sanda a écrit :
>Jean-Marc Lasgouttes wrote:
>> Le 31 octobre 2017 13:36:47 GMT+01:00, Jean-Marc Lasgouttes
> a écrit :
>> >Yes 2 is good for fixing the symptom, but it is very fragile...
>>
>> We could also try
>> 4. Note when we have requested a repa
Jean-Marc Lasgouttes wrote:
> Le 31 octobre 2017 13:36:47 GMT+01:00, Jean-Marc Lasgouttes
> a écrit :
> >Yes 2 is good for fixing the symptom, but it is very fragile...
>
> We could also try
> 4. Note when we have requested a repaint and exit early from paintEvent()
> when we did not ask for th
Le 31 octobre 2017 13:36:47 GMT+01:00, Jean-Marc Lasgouttes
a écrit :
>Yes 2 is good for fixing the symptom, but it is very fragile...
We could also try
4. Note when we have requested a repaint and exit early from paintEvent() when
we did not ask for this repaint. (Or even boldlier do a full me
Le 31 octobre 2017 11:52:57 GMT+01:00, Pavel Sanda a écrit :
>Jean-Marc Lasgouttes wrote:
>> Yes, this is needed in some cases. I see 3 types of fixes
>> 1. Convince qt that there is no need to update a whole window when
>the status bar changes
>> 2. Audit the uses of Buffer::message and use somet
Jean-Marc Lasgouttes wrote:
> Yes, this is needed in some cases. I see 3 types of fixed
> 1. Convince qt that there is no need to update a whole window when the status
> bar changes
> 2. Audit the uses of Buffer::message and use something else when possible.
> 3. Change row painting code so that i
Le 30 octobre 2017 16:00:13 GMT+01:00, Pavel Sanda a écrit :
>Jean-Marc Lasgouttes wrote:
>My guess is that if we do it generally for all cases some messaging
>gets
>broken (like the updates for longer lfuns - e.g. reconfiguration or
>compilation).
Yes, this is needed in some cases. I see 3 types
Jean-Marc Lasgouttes wrote:
> The patch does the right thing by using Cursor::message instead (so that
I can confirm that the crash is fixed.
> where this may happen. I'd be grateful for ideas that would make
> buffer::message and BufferView::message safer. It might be enough to just
> delay t
Am Mittwoch, 25. Oktober 2017 um 15:24:33, schrieb Richard Heck
> On 10/25/2017 02:35 PM, Kornel Benko wrote:
> > Am Dienstag, 24. Oktober 2017 um 19:51:41, schrieb Jean-Marc Lasgouttes
> >
> >> Le 23/10/2017 à 22:26, Pavel Sanda a écrit :
> >>> And I have reproducible crash:
> >>> 1. start new
Le 23/10/2017 à 22:26, Pavel Sanda a écrit :
And I have reproducible crash:
1. start new document
2. write "ambititious ", spellcheck correctly underlies text.
3. try to fix spelling via context menu, choose "ambitious"
4. kaboom
Here is a patch, that raises as many question as is solves. The i
Le 27/10/2017 à 15:14, Kornel Benko a écrit :
BTW, I get the same crash also with QT4.
Every time the word to correct is 2 chars longer as the wrong spelled.
For instance using 'tesest' and correct to 'test'. I used Hunspell,
but using Enchant or Aspell made no difference.
2 characters, of cour
Am Freitag, 27. Oktober 2017 um 14:37:08, schrieb Kornel Benko
> > > I can reproduce with continuous spellcheck enabled. Qt5.
> > >
> > > It crashes on LASSERT(LASSERT(end > start && end <= size() + 1, return
> > > false);
> > > at src/Paragraph.cpp:612
> >
> > I still can't reproduce (with q
Am Freitag, 27. Oktober 2017 um 14:07:35, schrieb Jean-Marc Lasgouttes
> Le 25/10/2017 à 20:35, Kornel Benko a écrit :
> > Am Dienstag, 24. Oktober 2017 um 19:51:41, schrieb Jean-Marc Lasgouttes
> >
> >> Le 23/10/2017 à 22:26, Pavel Sanda a écrit :
> >>> And I have reproducible crash:
> >>> 1.
Le 25/10/2017 à 20:35, Kornel Benko a écrit :
Am Dienstag, 24. Oktober 2017 um 19:51:41, schrieb Jean-Marc Lasgouttes
Le 23/10/2017 à 22:26, Pavel Sanda a écrit :
And I have reproducible crash:
1. start new document
2. write "ambititious ", spellcheck correctly underlies text.
3. try to fix s
On 10/25/2017 02:35 PM, Kornel Benko wrote:
> Am Dienstag, 24. Oktober 2017 um 19:51:41, schrieb Jean-Marc Lasgouttes
>
>> Le 23/10/2017 à 22:26, Pavel Sanda a écrit :
>>> And I have reproducible crash:
>>> 1. start new document
>>> 2. write "ambititious ", spellcheck correctly underlies text.
>>
Am Dienstag, 24. Oktober 2017 um 19:51:41, schrieb Jean-Marc Lasgouttes
> Le 23/10/2017 à 22:26, Pavel Sanda a écrit :
> > And I have reproducible crash:
> > 1. start new document
> > 2. write "ambititious ", spellcheck correctly underlies text.
> > 3. try to fix spelling via context menu, choose
Jean-Marc Lasgouttes wrote:
> Le 23/10/2017 ?? 22:21, Pavel Sanda a écrit :
>> Another cursor issue (I have vague memory this was already discussed):
>> while editing paragraph of text go to the end of last word.
>> Hit spacebar - space is inserted, but cursor stays at the end of word
>> and shows
Jean-Marc Lasgouttes wrote:
> Le 23/10/2017 ?? 22:26, Pavel Sanda a écrit :
>> And I have reproducible crash:
>> 1. start new document
>> 2. write "ambititious ", spellcheck correctly underlies text.
>> 3. try to fix spelling via context menu, choose "ambitious"
>> 4. kaboom
>
> I can't reproduce.
Le 23/10/2017 à 22:26, Pavel Sanda a écrit :
And I have reproducible crash:
1. start new document
2. write "ambititious ", spellcheck correctly underlies text.
3. try to fix spelling via context menu, choose "ambitious"
4. kaboom
I can't reproduce. Qt4 or Qt5?
JMarc
Le 23/10/2017 à 22:21, Pavel Sanda a écrit :
Another cursor issue (I have vague memory this was already discussed):
while editing paragraph of text go to the end of last word.
Hit spacebar - space is inserted, but cursor stays at the end of word
and shows only after inserting the next non whitesp
Jean-Marc Lasgouttes wrote:
>> After some testing:
>> - initial thread report present
>
> Which one?
https://www.mail-archive.com/lyx-devel@lists.lyx.org/msg202482.html
>> - a is present
>
> I think it is gone now
Confirmed, this issue is gone.
>> - c mostly fixed, ghost c3*** still remains
Se
I added an early return for Update::None that got forgotten.
Le 20/10/2017 à 16:56, Pavel Sanda a écrit :
After some testing:
- initial thread report present
Which one?
- a is present
I think it is gone now
- b is fixed
- c mostly fixed, ghost c3*** still remains
Cannot reproduce, but
Pavel Sanda wrote:
> Pavel Sanda wrote:
> > Jean-Marc Lasgouttes wrote:
> > > Le 19/10/2017 ?? 15:05, Pavel Sanda a écrit :
> > >> Pavel Sanda wrote:
> > >>> d) Editing problems
> > >>> Don't see how to produce solid recipy but something is wrong with
> > >>> editing
> > >>> as well.
> > >> Try c
Pavel Sanda wrote:
> Jean-Marc Lasgouttes wrote:
> > Le 19/10/2017 ?? 15:05, Pavel Sanda a écrit :
> >> Pavel Sanda wrote:
> >>> d) Editing problems
> >>> Don't see how to produce solid recipy but something is wrong with editing
> >>> as well.
> >> Try couple times this one:
> >> 1. open user guid
Jean-Marc Lasgouttes wrote:
> Le 19/10/2017 ?? 15:05, Pavel Sanda a écrit :
>> Pavel Sanda wrote:
>>> d) Editing problems
>>> Don't see how to produce solid recipy but something is wrong with editing
>>> as well.
>> Try couple times this one:
>> 1. open user guid, uncheck disable editing
>> 2. go
update_flags_ variable. This
variable is only reset after the buffer view has actually been
redrawn.
A new Update::ForceRedraw flag has been added. It requires a full
redraw but no metrics computation. It is not used in the main code
(yet), but avoids to compute metrics repeatedly in consecutive
p
Le 19/10/2017 à 14:59, Pavel Sanda a écrit :
Pavel Sanda wrote:
While doing the above steps in c) and jumping to different tabs or undoing I
randomly get LyX crashing:
Assertion false violated in Coordcache.cpp:31.
Recipy is rather simple:
1. open new document
2. insert LyX note
3. kaboom
I
Jean-Marc Lasgouttes wrote:
> Thanks for testing. I complain, but I appreciate (time to find a shrink?)
I appreciate. Until the new painting stuff is merged into stable I need to stay
with lyx 2.0...
Pavel
Le 19/10/2017 à 14:38, Pavel Sanda a écrit :
Jean-Marc Lasgouttes wrote:
Could you have a go at this updated patch? I had to do now a rewrite of
processUpdateFlags that I planned to do later.
Indeed, the reported issues seem to be solved (qt5 test).
But I see new ones (all of these with appli
Pavel Sanda wrote:
> d) Editing problems
> Don't see how to produce solid recipy but something is wrong with editing as
> well.
Try couple times this one:
1. open user guid, uncheck disable editing
2. go to in front of "i" in "What is LyX"
3. hit delete
4. in most cases the character does not dis
Pavel Sanda wrote:
> > While doing the above steps in c) and jumping to different tabs or undoing
> > I randomly get LyX crashing:
> > Assertion false violated in Coordcache.cpp:31.
Recipy is rather simple:
1. open new document
2. insert LyX note
3. kaboom
Pavel Sanda wrote:
> But I see new ones (all of these with applied patch, but they might apply to
> 2.3 as well):
> a)
> 1. edit document
> 2. scroll to different page via mouse wheel
> 3. hit ctrl+s to save
> 4. caret suddenly appears on screen on totally wrong position
>unrelated to current
Jean-Marc Lasgouttes wrote:
> Could you have a go at this updated patch? I had to do now a rewrite of
> processUpdateFlags that I planned to do later.
Indeed, the reported issues seem to be solved (qt5 test).
But I see new ones (all of these with applied patch, but they might apply to
2.3 as we
argument is now different: its
value is now OR'ed with a private update_flags_ variable. This
variable is only reset after the buffer view has actually been
redrawn.
A new Update::ForceRedraw flag has been added. It requires a full
redraw but no metrics computation. It is not used in the main code
Jean-Marc Lasgouttes wrote:
> It was fixing the math completion thing, and other things that have not been
> identified yet...
Ok I stay tuned for the next merge :) P
Le 18 octobre 2017 02:05:12 GMT+02:00, Pavel Sanda a écrit :
>Jean-Marc Lasgouttes wrote:
>> OK, I reverted it.
>
>Was this commit fixing some issue or is it refactoring type of work
>to make things better in the future?
>
>Pavel
It was fixing the math completion thing, and other things that hav
Jean-Marc Lasgouttes wrote:
> OK, I reverted it.
Was this commit fixing some issue or is it refactoring type of work
to make things better in the future?
Pavel
Jean-Marc Lasgouttes wrote:
> Le 17/10/2017 ?? 18:46, Pavel Sanda a écrit :
>> Bisect leads to c19c54dd5b85.
>> JMarc, this commit renders master editing/scrolling unusable.
>> (Qt5/debian stable).
>
> OK, I reverted it. Before you update master, I'd appreciate a list of other
> buggy situations,
Le 17/10/2017 à 18:46, Pavel Sanda a écrit :
Bisect leads to c19c54dd5b85.
JMarc, this commit renders master editing/scrolling unusable.
(Qt5/debian stable).
OK, I reverted it. Before you update master, I'd appreciate a list of
other buggy situations, so that I can do some damage control.
JM
Pavel Sanda wrote:
> Anyway you are right. Any editing in master seems to be seriously
> broken now, combo of painting issues and cursor shadows reported
> previously. After recent update it became so bad that I don't
> even know what to report first :)
Bisect leads to c19c54dd5b85.
JMarc, this co
Pavel Sanda wrote:
> This is unrelated and likely connected to the problem JMarc is
> solving with Stephan on Mac. (But you run linux, right?)
Anyway you are right. Any editing in master seems to be seriously
broken now, combo of painting issues and cursor shadows reported
previously. After recent
Kornel Benko wrote:
> I see something different:
> 1. Open document than spans more than single screen.
> 2. Resize the lyx window ==> black window
This is unrelated and likely connected to the problem JMarc is
solving with Stephan on Mac. (But you run linux, right?)
My problem is rather scrollin
. The cursor position is set correcly, but the scrolling/view
>is wrong, i.e. I see on top last couple rows of text only, the
>rest of screen is unused.
>
> Qt 5. I see it consistently, but different documents show
> different size of unused space. Random manual showed only
&g
Hi,
I see regression wrt LyX 2.0.
1. Open document than spans more than single screen.
2. Set cursor at the very end of the document
3. Close LyX
4. Launch LyX and reopen the same document
5. The cursor position is set correcly, but the scrolling/view
is wrong, i.e. I see on top last couple
Am Samstag, den 30.09.2017, 22:46 -0400 schrieb Scott Kostyshak:
> If you compile e.g. the Japanese splash to PDF (ps2pdf), does the PDF
> output look good to you? For me, both PDF (ps2pdf) and PDF (dvipdfm)
> export with success, but on the PDF created with ps2pdf I see
> jibberish
> instead of Ja
If you compile e.g. the Japanese splash to PDF (ps2pdf), does the PDF
output look good to you? For me, both PDF (ps2pdf) and PDF (dvipdfm)
export with success, but on the PDF created with ps2pdf I see jibberish
instead of Japanese characters.
Scott
signature.asc
Description: PGP signature
On Sat, Dec 03, 2016 at 10:51:56PM -0700, Joel Kulesza wrote:
> In general, I've had some difficulty getting Korean to work well. There
> seem to have been several issues lately with Arabic, Hebrew, and Korean.
> Would there be value in providing an additional Help menu addressing some
> of the va
On Sat, Dec 3, 2016 at 8:53 PM, Scott Kostyshak wrote:
>
> Indeed. I've seen that mentioned a few places but never tested it.
> I wonder if we should mention this in the GuiSymbols dialog?
In general, I've had some difficulty getting Korean to work well. There
seem to have been several issues l
On Sun, Dec 04, 2016 at 03:27:42AM +0100, Kornel Benko wrote:
> I can see them. You probably have to use different input encoding (here utf8).
Indeed. I've seen that mentioned a few places but never tested it.
I wonder if we should mention this in the GuiSymbols dialog?
Scott
signature.asc
Des
s.
> >
> > > What was the point of subtracting 1 from
> > > symbols.size()?
> > >
> >
> > This is according to the documentation:
> > https://doc.qt.io/qt-5/qabstractitemmodel.html#beginInsertRows
> > Inserting from 0 to n informs the view
er the end of the list. These bugs are now
> fixed, except for the missing names and ranges of the new blocks.
>
> > What was the point of subtracting 1 from
> > symbols.size()?
> >
>
> This is according to the documentation:
> https://doc.qt.io/qt-5/qabstractitemmodel.
https://doc.qt.io/qt-5/qabstractitemmodel.html#beginInsertRows
Inserting from 0 to n informs the view that n+1 lines are inserted. But,
its place is after endResetModel.
Guillaume
On Sat, Nov 19, 2016 at 12:41:13AM +0100, Guillaume Munch wrote:
> I cannot reproduce with the provided info (2.3dev & Qt5).
A bisect led to b3bed292. The attached patch fixes it for me, although I
don't understand my patch. What was the point of subtracting 1 from
symbols.size()?
Scott
diff --g
Le 19/11/2016 à 00:16, Richard Heck a écrit :
On 11/18/2016 04:01 PM, Scott Kostyshak wrote:
If I go to Insert > Special Character > Symbols...
and then go to "Hangul Syllables", I get an assertion.
On Qt 5 with custom-compiled Qt:
ASSERT: "last >= first" in file
/usr/src/qt/qt5/qtbase/src/core
Am Freitag, 18. November 2016 um 18:16:06, schrieb Richard Heck
> On 11/18/2016 04:01 PM, Scott Kostyshak wrote:
> > If I go to Insert > Special Character > Symbols...
> > and then go to "Hangul Syllables", I get an assertion.
> >
> > On Qt 5 with custom-compiled Qt:
> > ASSERT: "last >= first" in
On 11/18/2016 04:01 PM, Scott Kostyshak wrote:
> If I go to Insert > Special Character > Symbols...
> and then go to "Hangul Syllables", I get an assertion.
>
> On Qt 5 with custom-compiled Qt:
> ASSERT: "last >= first" in file
> /usr/src/qt/qt5/qtbase/src/corelib/itemmodels/qabstractitemmodel.cpp,
If I go to Insert > Special Character > Symbols...
and then go to "Hangul Syllables", I get an assertion.
On Qt 5 with custom-compiled Qt:
ASSERT: "last >= first" in file
/usr/src/qt/qt5/qtbase/src/corelib/itemmodels/qabstractitemmodel.cpp,
line 2604
With Qt 4:
ASSERT failure in QList::at: "index
On 2016-09-23, Jean-Marc Lasgouttes wrote:
> Le 22/09/2016 à 00:43, Guillaume Munch a écrit :
>> The attached patch does what you want.
>> The only problem is that now "View/Update Master Document" is always
>> shown.
> What about renaming master-buffer-view
Le 23/09/2016 à 11:31, Jean-Marc Lasgouttes a écrit :
Le 22/09/2016 à 00:43, Guillaume Munch a écrit :
The attached patch does what you want.
The only problem is that now "View/Update Master Document" is always
shown.
What about renaming master-buffer-view to buffer-view and buff
Le 22/09/2016 à 00:43, Guillaume Munch a écrit :
The attached patch does what you want.
The only problem is that now "View/Update Master Document" is always
shown.
What about renaming master-buffer-view to buffer-view and buffer-view to
child-buffer-view ("View only child
Le 22/09/2016 à 04:41, Richard Heck a écrit :
On 09/21/2016 06:43 PM, Guillaume Munch wrote:
Le 29/08/2016 à 17:02, Jean-Marc Lasgouttes a écrit :
This has been discussed some time ago. The command:
command-alternative master-buffer-view; buffer-view
does what you want.
However, it would
On 09/21/2016 06:43 PM, Guillaume Munch wrote:
> Le 29/08/2016 à 17:02, Jean-Marc Lasgouttes a écrit :
>>>
>>> This has been discussed some time ago. The command:
>>> command-alternative master-buffer-view; buffer-view
>>> does what you want.
>>
&g
Le 29/08/2016 à 17:02, Jean-Marc Lasgouttes a écrit :
This has been discussed some time ago. The command:
command-alternative master-buffer-view; buffer-view
does what you want.
However, it would make sense to have a first-class command that just
does the right thing IMO.
The attached
On 29.08.2016 17:57, Guillaume Munch wrote:
The command:
command-alternative[s] master-buffer-view; buffer-view
does what you want.
Is there a reason why the work area is focus on the current cursor
position with this command? This is not the case with the other view
commands.
Daniel
Le 29/08/2016 à 16:05, Richard Heck a écrit :
Or just modify the bindings to use what's above.
+1
On 08/29/2016 04:48 PM, racoon wrote:
On 29.08.2016 15:28, Michael Berger wrote:
Are you sure to have understood the concept of master-child?
Michael
On 08/29/2016 12:22 PM, racoon wrote:
Hi,
I almost never View child documents. Most of the time they don't
compile properly on thei
On 08/29/2016 11:10 AM, racoon wrote:
> On 29.08.2016 17:57, Guillaume Munch wrote:
>> Le 29/08/2016 à 11:22, racoon a écrit :
>>> Hi,
>>>
>>> I almost never View child documents. Most of the time they don't
>>> compile
>>> properly on
On 29.08.2016 18:39, Richard Heck wrote:
On 08/29/2016 11:10 AM, racoon wrote:
On 29.08.2016 17:57, Guillaume Munch wrote:
Le 29/08/2016 à 11:22, racoon a écrit :
Hi,
I almost never View child documents. Most of the time they don't
compile
properly on their own anyway. So I would li
On 29.08.2016 17:57, Guillaume Munch wrote:
Le 29/08/2016 à 11:22, racoon a écrit :
Hi,
I almost never View child documents. Most of the time they don't compile
properly on their own anyway. So I would like to remove the View button
from my interface. Unfortunately, the View master doc
On 08/29/2016 11:02 AM, Jean-Marc Lasgouttes wrote:
> Le 29/08/2016 à 16:57, Guillaume Munch a écrit :
>> Le 29/08/2016 à 11:22, racoon a écrit :
>>> Hi,
>>>
>>> I almost never View child documents. Most of the time they don't
>>> compile
>>&
Le 29/08/2016 à 16:57, Guillaume Munch a écrit :
Le 29/08/2016 à 11:22, racoon a écrit :
Hi,
I almost never View child documents. Most of the time they don't compile
properly on their own anyway. So I would like to remove the View button
from my interface. Unfortunately, the View m
Le 29/08/2016 à 11:22, racoon a écrit :
Hi,
I almost never View child documents. Most of the time they don't compile
properly on their own anyway. So I would like to remove the View button
from my interface. Unfortunately, the View master document button is
grayed out if there are no
1 - 100 of 1375 matches
Mail list logo
