mac.textcontrol-use-spell-checker

wxPython Users
1

Hi Guys,

I have:

wx.SystemOptions.SetOptionInt(“mac.textcontrol-use-spell-checker”, 1)

in my code and it was working. However I have only just noticed it seems to
have disappeared from the Edit menu, and been replaced by a Start Dictation
menu pick.

I am using the current Mac ports python 2.7.3, wxpython-devel 2.9.4 under
Mountain Lion 10.8.1 which has probably happened since I last noticed it.

Has this happened for anyone else, or is it just me?

Also recently I have started getting:

swig/python detected a memory leak of type ‘wxFrame *’, no destructor found.

when I close my program, but I don’t get any traceback, and haven’t added
any new frames that I recall? I did load the WIT but it was not obvious to
me if it could be used to help me in this case?

TIA

MarkL

2

Hi Guys,

I have:

wx.SystemOptions.SetOptionInt("mac.textcontrol-use-spell-checker", 1)

in my code and it was working. However I have only just noticed it seems to
have disappeared from the Edit menu, and been replaced by a Start Dictation
menu pick.

I am using the current Mac ports python 2.7.3, wxpython-devel 2.9.4 under
Mountain Lion 10.8.1 which has probably happened since I last noticed it.

Has this happened for anyone else, or is it just me?

You should probably create a ticket for this one. I experimented a little on 10.7 and found that it works with or without the system option set, but that I had to select the word to spell-check it. But I could turn on spellcheck-as-you-type from the Spelling and Grammar submenu of the text widget's context menu, and also open the spell-check dialog from there.

I'm not sure if there is anything different in how the native bits work, or how the wx bits are supposed to work in 10.8 as I haven't installed it yet. So creating a ticket at trac.wxwidgets.org will probably get some more answers than what I have.

Also recently I have started getting:

swig/python detected a memory leak of type 'wxFrame *', no destructor found.

when I close my program, but I don't get any traceback, and haven't added
any new frames that I recall? I did load the WIT but it was not obvious to
me if it could be used to help me in this case?

That error usually happens when the Python proxy object thinks that it owns the C++ object, and when the proxy is GC'd and it sees that there is no destructor defined for the C++ object (that it knows about anyway) it complains about it with that message. However all wxPython widget classes will usually set the proxy's thisown attribute to False so that it doesn't think that it owns the C++ object so that shouldn't normally happen. Are you using XRC or 2-phase create for some other reason but are not calling PostCreate?

···

On 9/18/12 9:18 PM, Mark Livingstone wrote:

--
Robin Dunn
Software Craftsman

3

I have:

wx.SystemOptions.SetOptionInt(“mac.textcontrol-use-spell-checker”, 1)

in my code and it was working. However I have only just noticed it seems to

have disappeared from the Edit menu, and been replaced by a Start Dictation

menu pick.

You should probably create a ticket for this one. I experimented a

http://trac.wxwidgets.org/ticket/14676

little on 10.7 and found that it works with or without the system option
set, but that I had to select the word to spell-check it. But I could
turn on spellcheck-as-you-type from the Spelling and Grammar submenu of
the text widget’s context menu, and also open the spell-check dialog
from there.

Yes, if I right click a word in a grid cell I get the spelling stuff, but I don’t seem to be able to get the Edit Menu stuff.

I’m not sure if there is anything different in how the native bits work,
or how the wx bits are supposed to work in 10.8 as I haven’t installed
it yet. So creating a ticket at trac.wxwidgets.org will probably get
some more answers than what I have.

Well today we got 10.8.2 so you are now 2 versions behind :wink: It seems like a full time job just keeping up with stuff :frowning:

Also recently I have started getting:

swig/python detected a memory leak of type ‘wxFrame *’, no destructor found.

That error usually happens when the Python proxy object thinks that it
owns the C++ object, and when the proxy is GC’d and it sees that there
is no destructor defined for the C++ object (that it knows about anyway)
it complains about it with that message. However all wxPython widget
classes will usually set the proxy’s thisown attribute to False so that
it doesn’t think that it owns the C++ object so that shouldn’t normally
happen. Are you using XRC or 2-phase create for some other reason but
are not calling PostCreate?

Definitely not using XRC XML, and I checked for 2-phase keywords and nobody seems to have added anything.

renaissance-2:src mlivingstone$ grep “wx.PreDialog” *.py

renaissance-2:src mlivingstone$ grep “wx.SetExtraStyle” *.py

renaissance-2:src mlivingstone$ grep “Create(” *.py

renaissance-2:src mlivingstone$ grep “PreFrame” *.py

renaissance-2:src mlivingstone$ grep “wx.FRAME_EX_CONTEXTHELP” *.py

renaissance-2:src mlivingstone$

···

On Thursday, 20 September 2012 04:35:10 UTC+10, Robin Dunn wrote:

On 9/18/12 9:18 PM, Mark Livingstone wrote:

4

Look closer at the last frame(s) to be closed before the program exits, or any others that have references from there

···

On 9/19/12 8:14 PM, Mark Livingstone wrote:

On Thursday, 20 September 2012 04:35:10 UTC+10, Robin Dunn wrote:

    On 9/18/12 9:18 PM, Mark Livingstone wrote:

     > Also recently I have started getting:
     >
     > swig/python detected a memory leak of type 'wxFrame *', no
    destructor found.

    That error usually happens when the Python proxy object thinks that it
    owns the C++ object, and when the proxy is GC'd and it sees that there
    is no destructor defined for the C++ object (that it knows about
    anyway)
    it complains about it with that message. However all wxPython widget
    classes will usually set the proxy's thisown attribute to False so that
    it doesn't think that it owns the C++ object so that shouldn't normally
    happen. Are you using XRC or 2-phase create for some other reason but
    are not calling PostCreate?

  Definitely not using XRC XML, and I checked for 2-phase keywords and
nobody seems to have added anything.

renaissance-2:src mlivingstone$ grep "wx.PreDialog" *.py
renaissance-2:src mlivingstone$ grep "wx.SetExtraStyle" *.py
renaissance-2:src mlivingstone$ grep "Create(" *.py
renaissance-2:src mlivingstone$ grep "PreFrame" *.py
renaissance-2:src mlivingstone$ grep "wx.FRAME_EX_CONTEXTHELP" *.py
renaissance-2:src mlivingstone$

--
Robin Dunn
Software Craftsman