Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion mac.textcontrol-use-spell-chec ker
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Mark Livingstone  
View profile  
 More options Sep 19 2012, 11:14 pm
From: Mark Livingstone <livingstonem...@gmail.com>
Date: Wed, 19 Sep 2012 20:14:25 -0700 (PDT)
Local: Wed, Sep 19 2012 11:14 pm
Subject: Re: [wxPython-users] mac.textcontrol-use-spell-checker

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

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

> > 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 ;-) It seems like
a full time job just keeping up with stuff :-(

> > 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$


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.