OK, David Boddie helped clear up my confusion (as did rereading
chapter 1 of "Rapid GUI Programming") -- to get from a QString to
something I can work on in Python it is only necessary to apply
unicode(). Doh! (Facepalm).
BLEEP represents any transformation that the user requires, which is
not in
On Saturday 06 August 2011, 00:35:51 David Boddie wrote:
> On Fri Aug 5 19:27:51 BST 2011, David Cortesi wrote:
> > I present a document to a user in a QPlainTextEdit widget. The
> > widget nicely handles most editing functions, but there is a unique
> > operation I want to provide. When the user s
On Fri Aug 5 19:27:51 BST 2011, David Cortesi wrote:
> I present a document to a user in a QPlainTextEdit widget. The widget
> nicely handles most editing functions, but there is a unique operation
> I want to provide. When the user selects Edit > BLEEP, the app is
> supposed to BLEEP the document
On Friday 05 August 2011, 20:27:51 David Cortesi wrote:
> I present a document to a user in a QPlainTextEdit widget. The widget
> nicely handles most editing functions, but there is a unique
> operation I want to provide. When the user selects Edit > BLEEP, the
> app is supposed to BLEEP the docume
I present a document to a user in a QPlainTextEdit widget. The widget
nicely handles most editing functions, but there is a unique operation
I want to provide. When the user selects Edit > BLEEP, the app is
supposed to BLEEP the document.
BLEEPing is not something Qt does, I have to implement BLEE
