Henning Hraban Ramm wrote:

> - the find field doesn't work (maybe a Mac issue)
You have to press Enter to actually trigger the search, did you do that?


Sure. I guess the wx.WXK_RETURN -- or rawKeyCode at all -- isn't the right thing on every platform. I remember some discussions about checking key codes on the wx mailing list...

I changed something with the search stuff. Would you please have another go.

> - the find/replace dialog doesn't do anything
Find works fine under windows, replace I haven't implemented (tried).


Sorry, it works. Don't know why it didn't yesterday.

The Find/Replace dialog is Dabo standard. I think it fires for all text like control. So I think it tries to find in the control that was active when calling the dialog.
I don't know I'll have to check into it.

> - I don't know if I like to alt-click on tabs. Perhaps a wiki- like behaviour would be better? i.e. distinguish between 'read' and 'edit' mode, perhaps using a toggle button, where you can simply click on tags in read mode and nothing in edit mode (switching from edit to read mode would save the note).
>
I'll think about it. I don't want to implement editing modes (read/ edit). How about navigation with middle mouse button. (Preference in later versions).


Using middle mouse buttons is very uncommon outside of Linux (don't know about Unices). I guess a lot of Windows users don't even know that their scroll wheel mostly works as a third button. And there are still too much Mac users that use Apple's one button mouse (and I don't even know the modifier key for the middle button emulation).

Let's see when we go along.

> - This looks like another dabo issue:
> File "/Library/Frameworks/Python.framework/Versions/2.4/lib/ python2.4/site-packages/Dabo-0.5-py2.4.egg/dabo/ui/uiwx/ dMenuBar.py", line 35, in __onWxMenuOpen
>     menu.raiseEvent(dEvents.MenuHighlight)
> AttributeError: 'Menu' object has no attribute 'raiseEvent'
>
Yep. Ed. :)
I'll see what I can do about that.
When does that happen?


I found several of that in the shell window after quitting freeNotes...
But I found it again: Every time i rightclick in some note (but the context menu pops up and works).

I can't dupöicate this under windows. But I'll keep alook out for it.

Python once crashed with a "bus error" after clicking on a list item; couldn't reproduce that.

[snip]

TypeError: activateEditorContent() takes exactly 2 arguments (1 given)

That should be gone now.

Another one:
I activate a sub-note and delete it, but choose "No" in the delete dialog. freeNotes then closes all open sub-note trees. I get the traceback if I open one again:

TypeError: int() argument must be a string or a number

I could duplicate this either.

Sorry for only increasing your heap of tasks...

No problem. :)

adi


_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users

Reply via email to