work.
Yeah, just do a simple print. Can you submit the patch as bzr branch?
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send
=QItemDelegate+lang%3Apy
Conveniently, you can probably override the QItemDelegates paint()
method, call the superclasses paint() method and draw your bar over
it.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because
the ssh key thing done though.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
you can make between the core and gui you can
make, the better (not least because it makes the code much easier to
understand). Esp. the direction where core calls the gui should be
minimal - it doesn't really matter how much the gui needs to call the
core.
--
Ville M. Vainio
http://tinyurl.com
)) PyQt4.uic.exceptions.WidgetPluginError: type
'exceptions.IOError': [Errno 2] No such file or directory:
'/usr/lib/python2.5/site-packages/PyQt4/uic/widget-plugins/qtwebkit.py'
Try installing python-webkit and webkit from 8.10 as well.
--
Ville M. Vainio
http://tinyurl.com/vainio
{hasattr}
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group
?
I'm just sure wheter it's worthwhile to dillute the development
effort, esp. if it's not just about the development of core, but also
the development of gui specific plugins.
Notably, wx has no advantages over Qt, now that Qt is under LGPL.
--
Ville M. Vainio
http://tinyurl.com/vainio
the installer, next next next?
?
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
perspective, it could still be
better to emphasize that leo has 2 gui's, with other code existing
for entertainment purposes only.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
the performance.
What gui were you using, and how big was the .leo file?
As said above: it was qt, and the file was the standard leoPyRef.leo.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you
.
It looks like you have a very slow machine :-)
Yes, I was testing with my asus eee (1 ghz).
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post
be that
the attributes are of universal utility.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send email to leo-editor
, not at the bottom
when you expand a node. That is, it should use
QTreeWidget.PositionAtCenter, but only when scrolling is necessary
(i.e. on redraw).
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed
, but it may require more work than
changing the current redraw behaviour to only touch the child nodes
(I'm not 100% sure about this though).
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed
On Wed, Jan 21, 2009 at 5:29 PM, tfer tfethers...@aol.com wrote:
On Jan 21, 9:51 am, Ville M. Vainio vivai...@gmail.com wrote:
Or, if you want to avoid the hassle, just send demo.py to me. It's
really a simple thing once you got the ssh key thing done though.
I'll work on getting it pushed
On Mon, Feb 2, 2009 at 12:23 PM, tfer tfethers...@aol.com wrote:
I added this bug, (and another), so I can reference them when I
request a review of my changes to demo.py.
Aah, sorry about the confusion :-)
--
Ville M. Vainio
http://tinyurl.com/vainio
.
This is pretty much it: http://www.3dtree.com/ev/e/sbooks/leo/sbframetoc_ie.htm
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send
changed it to use selectPosition, which probably is the way to go.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send email to leo
?
Interesting problem that may warrant documenting.
I think this would involve the code currently used for copy-paste,
storing the string somewhere, nuking an old subtree and pasting it
programmatically on restore.
--
Ville M. Vainio
http://tinyurl.com/vainio
On Tue, Feb 3, 2009 at 4:53 PM, Edward K. Ream edream...@gmail.com wrote:
Rev 1507 contains my latest attempt at minimizing scrolling. It seems
to work better. What do you think?
It still scroll horizontally when I expand/move around, which is
rather annoying...
--
Ville M. Vainio
http
btw? :-) is way ahead
of you. The body part is a QFrame with QGridLayout.
For an example, run this script:
QQQ
from PyQt4.QtGui import QTextEdit
w = QTextEdit()
c.frame.top.ui.leo_body_inner_frame.layout().addWidget(w,0,1)
QQQ
--
Ville M. Vainio
http://tinyurl.com/vainio
.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email
.
Full redraw does need to scroll, but redraw-after-expand doesn't (if
it doesn't delete the current item, but only creates items as current
items children).
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you
unicode(s) directly on that to avoid
any kind of conversion overhead.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send email
in the leo outline. You'll
figure something out, toplevel if nothing else ;-)
Also, are you planning some kind of @graph node that is an entry point
for loading/saving different graphical views of the data?
--
Ville M. Vainio
http://tinyurl.com/vainio
I fiddled a little bit with setup.py, setup.py install seems to
work now. Only with qt ui though. I pushed the changes to trunk.
Install setuptools, run setup.py install, launch leo by doing leo --gui=qt
Next, I'll see how much work creating a debian package for this would be...
--
Ville M
you are editing (and need to do the highlighting) the *initial
condition* of the highlighting is based on that last node.
That's pretty much what fast-color branch does, now.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received
alternative qt_main_hardyheron.ui to trunk. Copy it
over qt_main.ui if you get this error.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post
On Tue, Feb 10, 2009 at 4:48 PM, Ville M. Vainio vivai...@gmail.com wrote:
AttributeError: currentBlock
This ubuntu has qt version 4.3.3-2ubuntu4.1
Would it be possible to disable syntax highlighter globally if qt
doesn't have that method? I'd rather have leo *launchable*, even if we
On Tue, Feb 10, 2009 at 6:58 PM, Edward K. Ream edream...@gmail.com wrote:
I decided to play with this a little bit.
Could you post this to somewhere more permanent, that is, somewhere like
Leo's wiki? Thanks.
I'll add it as example to ileo chapter.
--
Ville M. Vainio
http://tinyurl.com
On Tue, Feb 10, 2009 at 3:43 PM, Edward K. Ream edream...@gmail.com wrote:
Please report any problem immediately. Thanks.
Try pasting e.g. qtGui.py file contents in a node. It hangs indefinitely.
Apart from that, editing is very snappy now.
--
Ville M. Vainio
http://tinyurl.com/vainio
On Tue, Feb 10, 2009 at 8:18 PM, Ville M. Vainio vivai...@gmail.com wrote:
On Tue, Feb 10, 2009 at 3:43 PM, Edward K. Ream edream...@gmail.com wrote:
Please report any problem immediately. Thanks.
Try pasting e.g. qtGui.py file contents in a node. It hangs indefinitely.
And pretty much
:
g.insqs(c)
And check out the QuickSearch tab. Press enter to do the search.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send
On Tue, Feb 10, 2009 at 8:55 PM, Edward K. Ream edream...@gmail.com wrote:
On Tue, Feb 10, 2009 at 12:29 PM, Ville M. Vainio vivai...@gmail.com
wrote:
It seems it's not all that fast to do getAllText every time.
Good catch. For large text (as in a large paste) the reallocation
On Wed, Feb 11, 2009 at 5:56 AM, Ville M. Vainio vivai...@gmail.com wrote:
No hacks so actual thought should be needed. Just add caching and
.. hacks OR actual thought...
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received
()
for i in range(1):
s2 = hello + s
It's pretty bad (and sloppy), but not really the biggest problem in
this recolor. It took long enough that I tired of waiting...
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received
like this
can make sense as a backup of your data. This would make most sense as
a @button.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post
is not recolor, but some other inefficiency
somewhere. Well, profiler will tell.
BTW, did ensure that @nocolor is handled in a very fast fashion? It's
critical to skip all of this machinery for huge log files/data
--
Ville M. Vainio
http://tinyurl.com/vainio
On Feb 10, 6:31 pm, Edward K. Ream edream...@gmail.com wrote:
Rev 1538 of the trunk disables the colorizer if not
hasattr(highlighter,'currentBlock')
I have only tested that the code works if the highlighter *does* have the
currentBlock method. Please verify that coloring is disabled if
--gui=qt
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group
converted to backslashes, and Leo reports that it can't find the file.
Forward slashes should always work. Leo probably uses os.path.abspath
(finalize?) which converts the slashes. This is probably a bug in leo,
%run -p does nothing special. Perhaps the path was just wrong.
--
Ville M. Vainio
http
and
run the latest version of Leo. Thanks...appreciate the help and
feedback.
Install bazaar:
http://edge.launchpad.net/bzr/1.11/1.11/+download/bzr-setup-1.11-1.exe
And do:
bzr branch lp:leo-editor
cd leo-editor
python launchLeo.py
--
Ville M. Vainio
http://tinyurl.com/vainio
. I always use forward slashes anyway,
since they work everywhere (while backslashes only work in windows).
This is why I try to avoid os.path.join and the likes.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because
:-).
leo-as-package thing seems to work - i.e. if you launch ipython and
have ipy_leo loaded, running lleo launches leo.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo
On Sat, Feb 14, 2009 at 1:27 AM, Ville M. Vainio vivai...@gmail.com wrote:
keypresses overall - and it seems get_directives_dict took almost 75%
of the time! That might be the next optimization target..
Looking at get_directives_dict, I can see that it uses a pattern that
is somewhat
On Sat, Feb 14, 2009 at 1:39 AM, Ville M. Vainio vivai...@gmail.com wrote:
Something like re.findall would probably be much more efficient.
e.g. (if I understood the code correctly)
re.findall(@(\w+)|\s*.*?\s*, string)
Or if I understood correctly and these must be on the beginning
On Sat, Feb 14, 2009 at 1:59 AM, Ville M. Vainio vivai...@gmail.com wrote:
On Sat, Feb 14, 2009 at 1:39 AM, Ville M. Vainio vivai...@gmail.com wrote:
Something like re.findall would probably be much more efficient.
e.g. (if I understood the code correctly)
re.findall(@(\w+)|\s*.*?\s
the conversion? And by
grepping fileIndex, it seems leo mostly wants to deal with gnx as
strings anyway. It may be in parts where performance doesn't matter,
but it would add some clarity to the code anyway.
--
Ville M. Vainio
http://tinyurl.com/vainio
On Wed, Feb 11, 2009 at 7:33 PM, Ville M. Vainio vivai...@gmail.com wrote:
Yet another trivial ILeo hack that needs extreme polish ;-).
This uses directory ~/.leo/dump to store version history of leo nodes
that you dump there explicitly. It's a git repository with gnx'es as
the file name
to edit much larger files with equal efficiency, so much the
better. And the code could be simpler as well.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor
of leo to debian
ubuntu. Hopefully we could make the Qt ui the default by then - Tk
does look a bit dated linux systems, even though the new Tk versions
will provide antialiased fonts.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received
winpdb
winpdb launchLeo.py foo
... and set the graphically.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send email to leo
On Mon, Feb 16, 2009 at 6:13 PM, Ville M. Vainio vivai...@gmail.com wrote:
Did you really try implementing getAllText cache properly? I took a
look at it, and it seems to be call toPlainText directly, without
using any knid of cache. I really think it's important to implement
the cache
in getAllText directly, as opposed to doing it on upper
level - there are many calls to getAllText in the code, and all of
them should benefit from the cache.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you
. Thanks.
Will do.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from
On Mon, Feb 16, 2009 at 6:44 PM, Ville M. Vainio vivai...@gmail.com wrote:
Yes. It should be the all_s ivar that recolor uses.
I plan to put the implementation in getAllText itself (and remove
all_s altogether).
Done pushed (please pull before working more, I had to edit
guiPluginsRef too
On Mon, Feb 16, 2009 at 7:42 PM, Ville M. Vainio vivai...@gmail.com wrote:
Done pushed (please pull before working more, I had to edit
guiPluginsRef too).
As a nice side effect, moving cursor around is much faster now ;-). It
seems it called getAllText as well.
But still not fast enough
On Mon, Feb 16, 2009 at 7:52 PM, Ville M. Vainio vivai...@gmail.com wrote:
But still not fast enough. Did more profiling, and found this
problematic: moveUpOrDownHelper. What's the point of this? can we
prevent running this in qt ui? It seems to do something that is
already done by QTextEdit
On Mon, Feb 16, 2009 at 8:13 PM, Ville M. Vainio vivai...@gmail.com wrote:
In case we can't actually disable them (because they are in the core),
perhaps we should monkeypatch from qtGui side.
Or do the same as with PgDn / PgUp, i.e. leave them unbound on the
body (they are very fast).
I
On Mon, Feb 16, 2009 at 8:25 PM, Ville M. Vainio vivai...@gmail.com wrote:
I also noted that I didn't aclually solve the getAllText problem
properly, toPlainText still gets done on up/down cursor keys.
Investigating...
Yeah, I did it in leoQtBody, I should have done it at lower level
On Mon, Feb 16, 2009 at 8:30 PM, Ville M. Vainio vivai...@gmail.com wrote:
I also noted that I didn't aclually solve the getAllText problem
properly, toPlainText still gets done on up/down cursor keys.
Investigating...
Yeah, I did it in leoQtBody, I should have done it at lower level
On Mon, Feb 16, 2009 at 8:44 PM, Ville M. Vainio vivai...@gmail.com wrote:
I think text entry still needs some work. I'll profile that some more.
Here are the problems:
856 15.0710.018 15.2350.018
leoGlobals.py:384(findTabWidthDirectives)
857 15.0260.018 15.068
On Mon, Feb 16, 2009 at 9:03 PM, Edward K. Ream edream...@gmail.com wrote:
I don't see any recent pushes. Are you sure you pushed to the trunk?
Pull again and see if you can get the code. I had to resolve some conflicts.
--
Ville M. Vainio
http://tinyurl.com/vainio
brought in at last merge.
Have to check it out.
I improved the color regexp a little bit (50%, according to profiler).
Can you pull?
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
On Mon, Feb 16, 2009 at 9:35 PM, Ville M. Vainio vivai...@gmail.com wrote:
I believe it may be a problem in tracing code (wrong assert /
something). It was introduced by code you brought in at last merge.
Have to check it out.
It checks whether we are in synch with all_s, which I believe
On Mon, Feb 16, 2009 at 9:38 PM, Ville M. Vainio vivai...@gmail.com wrote:
It checks whether we are in synch with all_s, which I believe is
redundant code now.
Actually, this happens because textChanged signal is run *after*
calling highlightBlock. It seems to colorize correcly, but only 1
On Mon, Feb 16, 2009 at 10:19 PM, Ville M. Vainio vivai...@gmail.com wrote:
Actually, this happens because textChanged signal is run *after*
calling highlightBlock. It seems to colorize correcly, but only 1
character too late. The checkRecolor call needs to be removed though.
However, let's
On Mon, Feb 16, 2009 at 11:05 PM, Ville M. Vainio vivai...@gmail.com wrote:
I added invalidateBodyCache to setAllText, which solves the problem on
first selection of a node at least. Errors still appear on incremental
edit.
I think it would be best to move cache invalidation out from
there is no cache clearing at the moment on
functions that manipulate the text. Let's try that anyway.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group
the hot spots elsewhere can avoid doing
getAllText. The performance improvements I saw where quite drastic.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor
do that?
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group
thinking of recolor anymore - I'm concerned about other
performance problems (text entry, cursor movement...).
Using separate cache for recolor seems like a more specific hack
when the cache can exist at a deeper level, benefitting the rest of
leo as well.
--
Ville M. Vainio
http://tinyurl.com/vainio
line of thinking (which I think you might like much more than the
cache ;-).
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send
, since the calls mostly come from core. This is
how my post about QTextCursor is relevant.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post
higher granularity!
toPlainText gets all the text which is slow. If we only look at a
small part of text,, we should attempt to only extract that part.
Unfortunately its not easy.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received
an external editor to deal with
situations like this (editing large amounts of text) - perhaps it's
still the recommended way?
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
On Thu, Feb 19, 2009 at 10:16 PM, Kent Tenney kten...@gmail.com wrote:
Are Leo clones conceptually different than symlinks in Unix?
Yes, with symlinks you can delete the target file/dir and the symlink
gets broken. They are more like hardlinks (if you could do them a
directory).
--
Ville M
, call stacks...). Now it'll be very
easy to browse the source tree and add clones to relevant source code
positions.
This really makes @auto nodes come to life (even if you need to do
read-at-auto-nodes after activating a file).
--
Ville M. Vainio
http://tinyurl.com/vainio
On Fri, Feb 20, 2009 at 6:23 PM, Ville M. Vainio vivai...@gmail.com wrote:
Great stuff!
With the caveat that the @button stopped working ;-). I now get 'no
script selected' on log every time I push it.
Can you inject something to g namespace, so the @button could just do
On Fri, Feb 20, 2009 at 6:39 PM, Ville M. Vainio vivai...@gmail.com wrote:
With the caveat that the @button stopped working ;-). I now get 'no
script selected' on log every time I push it.
Can you inject something to g namespace, so the @button could just do
'g.active_path_activate(c,p
to specify tab stop width that
is not exactly 4/8 spaces. That way, mixed spaces and tabs will stand
out in the code.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo
the this bug was introduced in revision 1527.
It's my guess these would all be fixed if leo started to call
unicode(s) instead of ...toUnicode(s). Perhaps g.app.gui.toUnicode
should be direct call to unicode()?
--
Ville M. Vainio
http://tinyurl.com/vainio
M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email to
leo
in between should be considered
a bug.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
not need to care about this stuff at all.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
.
I am myself partial to the MIT license, which is the next best thing
after Public Domain in its simplicity:
http://www.opensource.org/licenses/mit-license.php
BSD is more complicated, though it seems they fixed it somewhat last
year: http://www.opensource.org/licenses/bsd-license.php
--
Ville M
, without the complications.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
or MIT, you know the project is fair game.
Likewise, when you see GPL, you know to watch your step.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group
the diffs. It looks like this:
http://leo.zwiki.org/Scripts/diff
then navigate left/right and choose revert to this revision
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo
M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email to
leo
can't recall, leo currently removes the pyqt inputhook with
pyqtRemoveInputHook (which console ipython depends on). Perhaps this
should be reinvestigated...
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you
# This generates gui events, so we must use a lockout.
self.setCurrentItemHelper(item)
-if True: scroll:
+if scroll: scroll:
if trace: g.trace(self.traceItem(item),g.callers(4))
self.scrollToItem(item)
--
Ville M. Vainio
On Sun, Feb 22, 2009 at 10:55 AM, Ville M. Vainio vivai...@gmail.com wrote:
(or anthing else) and then runs the command. This is just a trivial
special of the generic hook.
special CASE...
So how should we proceed?
I suggest we do create CommandChainDispatcher in g namespace:
g.act_on_node
).
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email
On Sun, Feb 22, 2009 at 2:38 PM, Ville M. Vainio vivai...@gmail.com wrote:
The implementation is completely obvious and has absolutely no effect
on existing code, I'll probably push it this evening (have to leave
now).
I have pushed it now. Introdoces command act-on-node (keyboard
shortcut
On Sat, Feb 21, 2009 at 6:24 PM, Ville M. Vainio vivai...@gmail.com wrote:
It used to check for 'scroll' variable (judging by comments), but it
was disabled and now it always does scrolling. I tried calling it with
scroll=False in afterSelectHint, and returned the old code (I think
.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send
get stuck in a
scrolled state, at least.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
On Fri, Feb 20, 2009 at 6:57 PM, Ville M. Vainio vivai...@gmail.com wrote:
It's my guess these would all be fixed if leo started to call
unicode(s) instead of ...toUnicode(s). Perhaps g.app.gui.toUnicode
should be direct call to unicode()?
I tried this, i.e. changed this:
--- leo/plugins
need to configure it before it works
right, whereas leo should work right out of the box IMO.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post
301 - 400 of 2371 matches
Mail list logo
