Re: [SE|PY-macdev] Continuing OS X compiling

[valley <va...@ic...>]

Ok, here is what i found....

> I can add an icon for File panel but i'm also thinking at a different
solution for Mac users (maybe a combo box would be better?)
>
Actually I like the solution with this Listbook, it's quite similar to the
multiline tabs because you also see
the pictures. So I wouldn't prefer a combobox. But it would be good to add
an image for the Files panel too,
because without the name of this panel ("Files") doesn't get written on the
same horizontal line as the other names do,
but a little bit more above. And that doesn't look ok ;-)


> ::Perhaps you could fire the event that is called when the ::splitter is
dragged and moved just after completing the
> ::initialization of the left split pane...
>
> Mmhh.. I cannot reproduce that :(
>
Ok, i could try that out. Can you tell me how/where you bind the split pane
dragging event
and if it's possible to "manually" raise this event ?


> ::
> ::Ok, so for the moment the only two things a have to comment ::when i get
the newest cvs version are:
> ::   - line 285 (Editor.py): self.SetCodePage(stc.STC_CP_UTF8)
> ::     --> is there an alternative or can we just leave it commented ?
>
> Which was the issue with this? I cannot remember ^_^
>
The problem arose on SEPY startup. This is an excerpt of my mail to Richard
Wallace:
    << it seems that at the moment using unicode with wxPython isn't
possible.
    i 've just tried to build the newest wxWidget/wxPython from the source
and
    with unicode
    enabled. wxWidget built and installed correctly, but when i try to build
    wxPython then i get 'UNICODE mode not currently supported on this
WXPORT: mac'

    So it seems that we have to wait for this feature for the os x mode.
    >> Alessandro: Is it possible to use another CodePage than STC_CP_UTF8
    or is there another possibility to get over this current error ? >>

And this is the error message when this line isn't commented:
    File "/usr/local/src/SciTE/Editor.py", line 276, in __init__
     self.SetCodePage(stc.STC_CP_UTF8)
   File
"//Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/site-
    packages/wx/stc.py", line 1069, in SetCodePage
         return _stc.StyledTextCtrl_SetCodePage(*args, **kwargs)
    wx._core.PyAssertionError: C++ assertion "codePage != wxSTC_CP_UTF8"
    failed in /usr/local/src/wxWidgets/contrib/src/stc/stc.cpp(423):
    wxSTC_CP_UTF8 may not be used when wxUSE_UNICODE is off.



> ::
> ::   - line 597 (Editor.py): comment the bind event for the UPDATEUI
> ::     --> what can we do here for the moment ? or what exactly won't be
> ::           covered/updated when we leave this line commented ?
> ::
>
> Can you put a
> print "initialized the bind event" at the line above the Bind command? And
try to take a look how many times is called when a doc is created.
>
I did: This binding is called once for every new document you create, i.e.
on startup also once for the standard Untitled document.
So it's the event that is raised all the time.

>
> ::
> ::And the Tools/Preferences choice still creates the following error:
> ::    C++ assertion "wxAssertFailure" failed in /tmp/BUILD/
> ::    wxPythonSrc-2.5.2.8/src/generic/listctrl.cpp(3614):
> ::invalid list ctrl item index in SetItem
>
> There are 2 points where I use the SetItem in the WindowsPrefs.py file.
> Commenting the "sys.excepthook = exc_hook" in the SEPY.py file can't you
tell me in which line exactly raise the error?
>
No I can't, because this error message isn't reported in the shell but an
extra Python error message
window pops up for this error. So I have no idea where in your code the
error happens.
But if there are only two occurences we can get it out...

Regards
valley