Re: Getting rid of "You cannot type two spaces this way" message?
On Wed, Nov 21, 2012 at 12:34:15PM -0500, Alex Vergara Gil wrote: > > >On Wed, Nov 21, 2012 at 03:08:27PM +, Alan R. Bleier sort of wrote: > >>On Apr 15, 2012, at 3:59 PM, Trevor Jenkins wrote: > >>> if the key sequence has no meaning in LyX then I'd argue that there is > >>> absolutely no need for a message at all. Just have it drop the second > >>> space quietly and move on. > >>> Sorry I'm late joining this conversation, but it was sufficiently > >>> annoying to me today that I searched for information about it and > >>> found this thread. > >> > >>I agree completely with Trevor. If you are serious about "what you > >>see is what you mean" and "LyX lets you concentrate on writing" (from > >>http://www.lyx.org/WhatIsLyX ), the message should not be displayed. > > > >So you volunteer to handle the bug reports saying "LyX doesn't > >accept what I type" ... ... ... "Ah, two spaces... won't work."? > > > >Andre' > > Oh like the "bug repots" of "LyX doesn't put my images where I > want", etc. Come on guys, this is ridiculous. Correct. It's ridiculous. Still it happens. And it eats time. > If some thing one > should do before using anything is to read the manual, and there it > is well written: "LyX is WYSIWYM", so meaningless thing won't work, This is 2012. Nobody reads documentation. It has to work out of the box. And if it doesn't, it's not the the user's fault, but the programmer's. At least in the user's view. Andre'
Re: Getting rid of "You cannot type two spaces this way" message?
On Wed, Nov 21, 2012 at 03:08:27PM +, Alan R. Bleier sort of wrote: > On Apr 15, 2012, at 3:59 PM, Trevor Jenkins wrote: > > if the key sequence has no meaning in LyX then I'd argue that there is > > absolutely no need for a message at all. Just have it drop the second > > space quietly and move on. > > Sorry I'm late joining this conversation, but it was sufficiently > > annoying to me today that I searched for information about it and > > found this thread. > > I agree completely with Trevor. If you are serious about "what you > see is what you mean" and "LyX lets you concentrate on writing" (from > http://www.lyx.org/WhatIsLyX ), the message should not be displayed. So you volunteer to handle the bug reports saying "LyX doesn't accept what I type" ... ... ... "Ah, two spaces... won't work."? Andre'
Re: Report (was: Qt: was Slow scrolling)
On Thu, Jan 05, 2012 at 02:17:29PM +0100, Pavel Sanda wrote: > Jean-Marc Lasgouttes wrote: > > Le 05/01/2012 02:40, André Pönitz a écrit : > >> The main performance problems I have seesn so far are due to an abuse of > >> the toolkit, not caused _by_ the toolkit (except for the remote raster > > please... there were many cases we have no clue where the problem is. > it can be lyx, qt, X, card drivers. to summarize the whole thing by saying > that all is abuse of qt smells like problem with your affiliation ;) [Sure, we can go ad hominem if you think that helps...] LyX is the _only_ application I know that e.g. still pretends to be able to draw outside of paint events by adding another level of buffering (GuiWorkArea::Private::screen_). And note, that's not a "problem originating from Qt", but imposed by some platforms, most notably MacOS_X_. This approach causes otherwise completely unnessary copies of all screen data when scrolling. Also, the core text drawing functionality is "abstracted", i.e. LyX does it (deteminining positioning, spacing etc), spoon-feeds the results to Qt's drawText() which does the same again. Similar for the handling of fonts, colors etc. I just stepped a bit through the code and there were tons of instances where single characters were passed to drawText, each setting up the text drawing machinery mostly from scratch. I do understand that this might be needed for math, but it should not happen often for regular test. Andre'
Re: Slow scrolling
On Thu, Jan 05, 2012 at 09:28:58AM +0100, Olivier Ripoll wrote: > >>To check if this is the culprit one may add the following line to your > >>preferences file: > >>\force_paint_single_char false > >>On a Mac this is the file "~/Library/Application > >>Support/LyX-2.0/preferences". > >>(Broken cursor placement for long lines should be one consequence.) > > > >Will try this when I have some time. > > I did not see significant changes with or without this line. Out of curiosity: Can you try the same with "\use_pixmap_cache false" ? Andre'
Re: Qt: was Slow scrolling
On Wed, Jan 04, 2012 at 05:19:02PM -0500, Steve Litt wrote: > On Tuesday, January 03, 2012 03:36:16 PM Stephan Witt wrote: > > Am 03.01.2012 um 17:15 schrieb Olivier Ripoll: > > > > Hi, > > > > > > Check my 2 messages in the "LyX 2.0.2 Released" thread, one dated > > > december 5th (user mailing lists, perhaps devel too) and the > > > other one dated december 16th (devel ML), which contains more > > > details: > > > > > > http://www.mail-archive.com/lyx-users@lists.lyx.org/msg90218.html > > > http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg172462.htm > > > l > > > > Hi, > > > > I'm almost sure it depends on Qt-Version. > > > > With LyX on Mac with Qt4 we have two fundamental problems: > > At the risk of sounding like a broken record, if Qt continues to > produce these types of problems, isn't there different library or > combination of libraries the developers can use? At the risk of sounding like a broken record: Some of the issues in the past have been caused by wrong usage within LyX (like repaint() instead of update()), and some by insisting to use Qt versions that have been released before the other components in the system, like newer versions of MacOSX. I just run svn up and README says "The Qt4 library, at least version 4.2.2. For all features newer versions (e.g. Qt 4.6) are recommended." _Please_? That was state of the art in _2006_? That is not to say that Qt is flawless, Enrico(?)'s execvp/exeve issue for instance. But the thing _is_ open source, too, so if it's a pain point, fix it. > Back when I wrote my "why oh why did you dump xforms" rant, it seemed > like maybe the compile problems were just growing pains from Qt going > from version 3 to version 4. But now it's years later, and we're still > hearing (I paraphrase) "the quality of your LyX program depends on > your Qt version." > > I know, you've told me before, Qt does a lot of busywork and makes > programming LyX much simpler. It handles all the localization, etc. > Programming LyX without Qt would be a horrendeous chore. > > But is Qt really doing you a favor when certain Qt versions make your > program perform badly? *gosh* The main performance problems I have seesn so far are due to an abuse of the toolkit, not caused _by_ the toolkit (except for the remote raster painter problem perhaps). Just start at RowPainter::paintChars() and walk down through all the mess _before_ it actually hits Qt's drawText() It is slow? You bet. > The LyX developers work so hard to create a > robust, high productivity program, only to have a tool vendor snatch > defeat from the jaws of victory. Isn't there another localization > library you can use, and another GUI library, and whatever? Which one do you think would do the trick for Window, Mac _and_ Linux? > Thanks Please backport LyX to xforms. There was even a new release 1.0.93 in May 2010. If you have done it, and it loads the UserGuide I'll shut up for eternity on that topic. Andre'
