Re: Pixmap cache is broken for master

2015-10-15 Thread Richard Heck
On 10/15/2015 04:20 AM, Jean-Marc Lasgouttes wrote: Le 14/10/15 14:22, Stephan Witt a écrit : Indeed. What about just dumping it? :p I'm all for it. I did some profiling. Pixmaps are indeed a little bit faster visually. Here are the hard numbers Without Pixmaps: 66% LyX 32%

Re: Crash when quitting on OS X

2015-10-15 Thread disinteres...@gmail.com
They are definitely hard to reproduce, I spent a while trying to create a recipe, but with no success. I'd be happy to try the modified version. On Thu, Oct 15, 2015 at 12:41 AM, Stephan Witt wrote: > Am 15.10.2015 um 01:31 schrieb disinteres...@gmail.com: > > > With LyX 2.1.4

Re: Pixmap cache is broken for master

2015-10-15 Thread Jean-Marc Lasgouttes
Le 15/10/2015 14:47, Richard Heck a écrit : On 10/15/2015 04:20 AM, Jean-Marc Lasgouttes wrote: Le 14/10/15 14:22, Stephan Witt a écrit : Indeed. What about just dumping it? :p I'm all for it. I did some profiling. Pixmaps are indeed a little bit faster visually. Here are the hard numbers

Re: Form is function

2015-10-15 Thread Jean-Marc Lasgouttes
Le 15/10/15 00:13, Scott Kostyshak a écrit : The version of trac we use is almost 5 years old now. There have been a lot of changes since then. I don't think we should update before a major release, and I don't even know if we have someone who would have the time and knowledge to do the update.

Re: When to court Qt 5.6?

2015-10-15 Thread Jean-Marc Lasgouttes
Le 15/10/15 01:06, Scott Kostyshak a écrit : LyX 2.2.0 and the following 2.2.x releases will still continue to work well with Qt 4.8.6 but will also support Qt 5.6, which brings some advantages most notably for users with HiDPI displays. Note that if you compile LyX with a Qt 5 release before

Re: Moving towards a 2.2 release

2015-10-15 Thread Jean-Marc Lasgouttes
Le 12/10/15 11:02, Jean-Marc Lasgouttes a écrit : 2. What are the bugs that should be fixed before we release 2.2.0? Please note which of these bugs are regressions. Please note also if you are volunteering to work on the bug yourself. I have a bug (just created for the record) on my plate

Re: Pixmap cache is broken for master

2015-10-15 Thread Jean-Marc Lasgouttes
Le 14/10/15 14:22, Stephan Witt a écrit : Indeed. What about just dumping it? :p I'm all for it. I did some profiling. Pixmaps are indeed a little bit faster visually. Here are the hard numbers Without Pixmaps: 66% LyX 32% GuiWorkArea::Private::updateScreen 12,6%

Re: [PATCH] Get rid of ParagraphMetrics::insetDimension

2015-10-15 Thread Richard Heck
On 10/15/2015 09:30 AM, Jean-Marc Lasgouttes wrote: The following patch is a simple cleanup that was written before the acceptation of the role of release master by Scott. It removes the cache ParagraphMetrics:insetDimension, and relies on the already existing BufferView::coordCache instead.

[PATCH] Get rid of ParagraphMetrics::insetDimension

2015-10-15 Thread Jean-Marc Lasgouttes
The following patch is a simple cleanup that was written before the acceptation of the role of release master by Scott. It removes the cache ParagraphMetrics:insetDimension, and relies on the already existing BufferView::coordCache instead. It is quite straightforward, but does not bring

Re: When to court Qt 5.6?

2015-10-15 Thread Scott Kostyshak
On Thu, Oct 15, 2015 at 08:37:41AM +0200, Jean-Marc Lasgouttes wrote: > Le 15/10/15 01:06, Scott Kostyshak a écrit : > >LyX 2.2.0 and the following 2.2.x releases will still continue to work > >well with Qt 4.8.6 but will also support Qt 5.6, which brings some > >advantages most notably for users

Re: [PATCH] Get rid of ParagraphMetrics::insetDimension

2015-10-15 Thread Scott Kostyshak
On Thu, Oct 15, 2015 at 03:30:21PM +0200, Jean-Marc Lasgouttes wrote: > Scott, OK? Yes. > // FIXME (Abdel 23/09/2007): this is a bit messy > because of the > // elimination of Inset::dim_ cache. This coordOffset() > method needs >

Re: [patches] the last ones before 2.2

2015-10-15 Thread Georg Baum
Jean-Marc Lasgouttes wrote: >> Why do you need a new member variable at all? Why can't you just use the >> memory address? This would not consume memory and still be a unique id. > > I guess that the answer is the same as for paragraph ids: they can get > copied at unexpected times. If my

Re: Pixmap cache is broken for master

2015-10-15 Thread Guillaume Munch
Le 15/10/2015 09:20, Jean-Marc Lasgouttes a écrit : Le 14/10/15 14:22, Stephan Witt a écrit : Indeed. What about just dumping it? :p I'm all for it. I did some profiling. Pixmaps are indeed a little bit faster visually. Here are the hard numbers Without Pixmaps: 66% LyX 32%

Re: [patches] the last ones before 2.2

2015-10-15 Thread Guillaume Munch
Le 14/10/2015 21:35, Georg Baum a écrit : *#2: Add a unique id to math insets. I also print this information in the DEVEL_VERSION in the status bar similarly to what is done currently for paragraphs. It is interesting that while the paragraph id is usually below 1, this new math inset id

Re: IBus compatibility

2015-10-15 Thread Guillaume Munch
Le 14/10/2015 20:00, Georg Baum a écrit : Jean-Marc Lasgouttes wrote: Le 11/10/2015 12:43, Guillaume Munch a écrit : Qt 5.6.0 will probably be released before LyX 2.2.0. Therefore the most simple solution would be to disable IBus if an older qt is detected (at runtime) and mention in the

Re: [patches] the last ones before 2.2

2015-10-15 Thread Guillaume Munch
Le 15/10/2015 18:20, Georg Baum a écrit : Jean-Marc Lasgouttes wrote: Why do you need a new member variable at all? Why can't you just use the memory address? This would not consume memory and still be a unique id. I guess that the answer is the same as for paragraph ids: they can get copied

Re: Form is function

2015-10-15 Thread Guillaume Munch
Le 14/10/2015 09:38, Liviu Andronic a écrit : On Wed, Oct 14, 2015 at 7:55 AM, Guillaume Munch wrote: the hard truth is that our manpower is limited and our devels barely have the bandwidth to address crashes, regressions and the like (in between monitoring tickets, triaging,

Re: IBus compatibility

2015-10-15 Thread Georg Baum
Guillaume Munch wrote: > Beware of any confusion, the deadlock bug is with qt4 and is solved in > qt5 (any version I could test). Another bug makes qt < 5.6 impractical > for (all) Linux users. So the situation is more complex than what you > wrote. Oh, sorry, then I misunderstood the situation