I have a situation where I insert an empty pane and then press action and
put the find pane in there. If I then use the focus-to-find command I get
this error:
exception executing command
Traceback (most recent call last):
File "C:\MyPrograms\Leo5.1-b1\leo\core\leoCommands.py", line 550, in doCommand
val = command(event)
File "C:\MyPrograms\Leo5.1-b1\leo\core\leoFind.py", line 326, in focusToFind
self.c.frame.log.selectTab('Find')
File "C:\MyPrograms\Leo5.1-b1\leo\plugins\qt_frame.py", line 3403, in
selectTab
self.selectHelper(tabName)
File "C:\MyPrograms\Leo5.1-b1\leo\plugins\qt_frame.py", line 3424, in
selectHelper
widget.ensureWidgetVisible(findbox)
AttributeError: 'LeoQTextBrowser' object has no attribute 'ensureWidgetVisible'
On Wednesday, April 8, 2015 at 7:48:44 AM UTC-4, john lunzer wrote:
>
> One thing I noticed last night was a strange behavior when rearranging
> outlines (with keyboard Shift+L/R/U/D).
>
> Create three nodes in order named Head1,Head2,Head3. Under Head1 create a
> child called Sub1.
>
> Navigate to Head2. Type Shift+Down, you will see Head2 and Head3 swapped
> positions and Head2 is still selected. Now with Head2 selected type
> Shift+Up, you will see Head2 does not move back to its original position
> but instead becomes a child of Head1.
>
> If this is intended behavior please let me know.
>
> On Wednesday, April 8, 2015 at 7:11:37 AM UTC-4, john lunzer wrote:
>>
>> Thank you for your guidance. I will continue to bring *real* issues here
>> and try to refrain from "suggestions" and "enhancements". There are plenty
>> of real issues to deal with and never enough time to deal with them all.
>>
>> Leo is oozing with potential and very exciting. I got pretty excited,
>> especially when I realized the main developers are actually committed to
>> listening to users! When I get excited about something I tend to go all in
>> and it can be overwhelming to others as well as myself.
>>
>> On Wednesday, April 8, 2015 at 6:24:10 AM UTC-4, Edward K. Ream wrote:
>>>
>>>
>>> On Tue, Apr 7, 2015 at 7:23 PM, john lunzer <[email protected]> wrote:
>>>
>>>> I get the feeling this post was triggered partially by my actions.
>>>>
>>>
>>> Yes, it was. My reply was an intended to suggest that not every
>>> preference or ui glitch is a bug :-)
>>>
>>> Otoh, newbies often discover real problems that more experienced users
>>> never would. So there is an unavoidable tension here.
>>>
>>> UI bugs are particularly distracting to me. If it makes you feel any
>>>> better I've only posted about half of the bugs I've actually encountered.
>>>>
>>>> I'll try to keep it down.
>>>>
>>>
>>> Please do not apologize for reporting problems as you see them. I would
>>> like to hear about *all *the problem you have experienced. This thread
>>> would be a good place. Please follow these guidelines:
>>>
>>> - The briefer the report the better. I am a prime offender :-)
>>>
>>> - No need to lobby for how important an issue is. The Leo community
>>> will be the ultimate judge of that.
>>>
>>> - Please do not file bug reports until you are sure the issue is a real
>>> bug.
>>>
>>> In short, this thread would be a good place to discuss *everything *that
>>> you have found distracting or troubling as you are learning Leo.
>>>
>>> Thanks again for your help. Programming is inherently a detail oriented
>>> enterprise. It's good to consider all details, regardless of their
>>> ultimate disposition. I am reminded of the informal motto of the ANSI C
>>> Standards Committee, on which I briefly served: consider much, adopt little.
>>>
>>> Edward
>>>
>>
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
