pycrust-users Mailing List for PyCrust (Page 3)
Brought to you by:
pobrien
Menu
▾
▴
pycrust-users — PyCrust Users and Developers
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(76) |
Sep
(27) |
Oct
(5) |
Nov
(13) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(1) |
Feb
(24) |
Mar
|
Apr
(1) |
May
(3) |
Jun
(2) |
Jul
|
Aug
(4) |
Sep
|
Oct
|
Nov
(3) |
Dec
|
| 2003 |
Jan
|
Feb
(4) |
Mar
(5) |
Apr
(3) |
May
(4) |
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2006 |
Jan
|
Feb
(2) |
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Neil H. <ne...@sc...> - 2002-02-06 20:08:20
|
Patrick:
> That solves one problem, but creates another. Apply the change and then
run
> PyCrust and type:
>
> ...
>
> >>> ''._ (fails)
> >>> []._ (succeeds on most, but fails to match on >>> [].__d)
> >>> {}._ (succeeds, sort of, but fails to match on >>> {}.__cmp)
>
> Something is still broken in the search routine.
Yes, there is a bug here so I will look into it.
> Any chance a linear search
> would be good enough for what is usually a fairly reasonable sized list?
Some people have *megabytes* in autocompletion lists. There was even a
patch submitted to process them on a separate thread because they were too
slow.
Neil
|
|
From: Patrick K. O'B. <po...@or...> - 2002-02-06 13:28:00
|
That solves one problem, but creates another. Apply the change and then run
PyCrust and type:
>>> shell._
This matches nothing, while this:
>>> filling._
Matches just fine. (Well, sort of. See below.). Both objects have attributes
with leading underscores at the end of their lists.
Here are some more examples:
>>> ''._ (fails)
>>> []._ (succeeds on most, but fails to match on >>> [].__d)
>>> {}._ (succeeds, sort of, but fails to match on >>> {}.__cmp)
Something is still broken in the search routine. Any chance a linear search
would be good enough for what is usually a fairly reasonable sized list?
---
Patrick K. O'Brien
Orbtech
> -----Original Message-----
> From: pyc...@li...
> [mailto:pyc...@li...]On Behalf Of Neil
> Hodgson
> Sent: Wednesday, February 06, 2002 5:48 AM
> To: po...@or...; Kevin Altis; pycr
> Subject: Re: [PyCrust] FW: underscore kills command completion
>
>
> Patrick K. O'Brien:
>
> > I'm seeing this same problem in Pythoncard with Python 2.2 using the
> "Proof"
> > application. But it isn't consistent. For example, the following worked:
> >
> > >>> bg.DLG_SZE
> >
> > but this failed to match:
> >
> > >>> bg.on_
> >
> > The following also worked:
> >
> > >>> os.stat_result
> >
> > Those "on_" methods don't seem to want to match. I have no idea why.
>
> Replace the current sorting in getAttributeNames in introspect.py with
>
> attributes.sort(lambda x, y: cmp(x.upper(), y.upper()))
>
> so it is converting to upper case rather than lower case and
> this moves
> the on_* after on followed by a letter. The autocompletion box is assuming
> that case insensitive order places the '_' after 'Z', can't find
> any entries
> that match and so dies. It uses a binary rather than linear
> search so misses
> the on_ earlier. Since it is a binary search, it may sometimes
> find the on_
> even though it is in the wrong place as the binary search depends on order
> and the order is inconsistent.
>
> With case insensitive code, the characters [\]^_` which are located
> between Z and a have to sort somewhere, so Scintilla puts them after the
> letters.
>
> Neil
>
>
>
> _______________________________________________
> PyCrust-users mailing list
> PyC...@li...
> https://lists.sourceforge.net/lists/listinfo/pycrust-users
|
|
From: Neil H. <ne...@sc...> - 2002-02-06 11:48:26
|
Patrick K. O'Brien:
> I'm seeing this same problem in Pythoncard with Python 2.2 using the
"Proof"
> application. But it isn't consistent. For example, the following worked:
>
> >>> bg.DLG_SZE
>
> but this failed to match:
>
> >>> bg.on_
>
> The following also worked:
>
> >>> os.stat_result
>
> Those "on_" methods don't seem to want to match. I have no idea why.
Replace the current sorting in getAttributeNames in introspect.py with
attributes.sort(lambda x, y: cmp(x.upper(), y.upper()))
so it is converting to upper case rather than lower case and this moves
the on_* after on followed by a letter. The autocompletion box is assuming
that case insensitive order places the '_' after 'Z', can't find any entries
that match and so dies. It uses a binary rather than linear search so misses
the on_ earlier. Since it is a binary search, it may sometimes find the on_
even though it is in the wrong place as the binary search depends on order
and the order is inconsistent.
With case insensitive code, the characters [\]^_` which are located
between Z and a have to sort somewhere, so Scintilla puts them after the
letters.
Neil
|
|
From: Patrick K. O'B. <po...@or...> - 2002-02-05 23:21:33
|
This has been corrected in the CVS version. Thanks a bunch for the feedback. Sorry it took me so long to fix it. --- Patrick K. O'Brien Orbtech > -----Original Message----- > From: pyc...@li... > [mailto:pyc...@li...]On Behalf Of Syver > Enstad > Sent: Sunday, January 13, 2002 7:27 AM > To: pyc...@li... > Subject: [PyCrust] enabling shift+insert, control+insert, shift+delete > keys in pycrust > > > PyCrust disables as is disables some of the standard bindings for > copying, deleting and inserting text. > > The following code fixes the problem: > >From shell.Shell method OnKeyDown > # Don't toggle between insert mode and overwrite mode. > elif key == WXK_INSERT and not (event.ShiftDown() or > event.ControlDown()): > pass > > The only added code is : > and not (event.ShiftDown() or event.ControlDown()) > -- > > Vennlig hilsen > > Syver Enstad > > > > _______________________________________________ > PyCrust-users mailing list > PyC...@li... > https://lists.sourceforge.net/lists/listinfo/pycrust-users |
|
From: Patrick K. O'B. <po...@or...> - 2002-02-05 19:36:58
|
Bad puns aside, I've made some recent changes to PyCrust so that it tastes better with Python 2.2. Anyone who would like to help test things should check out the version in CVS (0.7.1) and let me know if anything is still broken, or whether anything new broke when used with older versions of Python (I tested Python 2.1.2 and Python 2.2). Thanks. http://sourceforge.net/projects/pycrust/ --- Patrick K. O'Brien Orbtech |
|
From: Patrick K. O'B. <po...@or...> - 2002-02-05 19:00:01
|
I'm seeing this same problem in Pythoncard with Python 2.2 using the "Proof" application. But it isn't consistent. For example, the following worked: >>> bg.DLG_SZE but this failed to match: >>> bg.on_ The following also worked: >>> os.stat_result Those "on_" methods don't seem to want to match. I have no idea why. --- Patrick K. O'Brien Orbtech > -----Original Message----- > From: Kevin Altis [mailto:al...@se...] > Sent: Tuesday, February 05, 2002 12:45 PM > To: po...@or...; pycr > Subject: RE: [PyCrust] FW: underscore kills command completion > > > > I'm not seeing this problem under Python 2.1.2 or Python 2.2. > Kevin, what > > version of Python are you running? > > PythonCard version: 0.6.4 (really just 0.6.3.2 but I'm using > what's in cvs) > wxPython version: 2.3.2.1 > PyCrust version: 0.7.1 > Python version: 2.1.1 (#20, Jul 26 2001, 11:38:51) [MSC 32 bit (Intel)] > Platform: win32 > > And this in PythonCard so that means that autocomplete include single and > double underscores is off, could that be the problem? > > shell.autoCompleteIncludeMagic = 1 > shell.autoCompleteIncludeSingle = 0 > shell.autoCompleteIncludeDouble = 0 > > ka > > > > -----Original Message----- > > > From: pyc...@li... > > > [mailto:pyc...@li...]On Behalf Of Patrick > > > K. O'Brien > > > Sent: Monday, February 04, 2002 5:51 PM > > > To: pycr > > > Subject: [PyCrust] FW: underscore kills command completion > > > > > > > > > Neil or Robin, > > > > > > Is this expected behavior for wxSTC, or am I doing something wrong? > > > > > > --- > > > Patrick K. O'Brien > > > Orbtech > > > > > > -----Original Message----- > > > From: Kevin Altis [mailto:al...@se...] > > > Sent: Monday, February 04, 2002 4:13 PM > > > To: Patrick K. O'Brien > > > Subject: underscore kills command completion > > > > > > > > > I never tried using a on_ handler in the shell before, so I'm just now > > > seeing this problem. Open up any PythonCard sample with the > > shell and then > > > type > > > bg.on > > > to get to the first event handler, then when you type the > underscore the > > > completion window goes away. > > > > > > ka > > > > > > > > > _______________________________________________ > > > PyCrust-users mailing list > > > PyC...@li... > > > https://lists.sourceforge.net/lists/listinfo/pycrust-users > > > > > > _______________________________________________ > > PyCrust-users mailing list > > PyC...@li... > > https://lists.sourceforge.net/lists/listinfo/pycrust-users > > > |
|
From: Kevin A. <al...@se...> - 2002-02-05 18:43:14
|
> I'm not seeing this problem under Python 2.1.2 or Python 2.2. Kevin, what > version of Python are you running? PythonCard version: 0.6.4 (really just 0.6.3.2 but I'm using what's in cvs) wxPython version: 2.3.2.1 PyCrust version: 0.7.1 Python version: 2.1.1 (#20, Jul 26 2001, 11:38:51) [MSC 32 bit (Intel)] Platform: win32 And this in PythonCard so that means that autocomplete include single and double underscores is off, could that be the problem? shell.autoCompleteIncludeMagic = 1 shell.autoCompleteIncludeSingle = 0 shell.autoCompleteIncludeDouble = 0 ka > > -----Original Message----- > > From: pyc...@li... > > [mailto:pyc...@li...]On Behalf Of Patrick > > K. O'Brien > > Sent: Monday, February 04, 2002 5:51 PM > > To: pycr > > Subject: [PyCrust] FW: underscore kills command completion > > > > > > Neil or Robin, > > > > Is this expected behavior for wxSTC, or am I doing something wrong? > > > > --- > > Patrick K. O'Brien > > Orbtech > > > > -----Original Message----- > > From: Kevin Altis [mailto:al...@se...] > > Sent: Monday, February 04, 2002 4:13 PM > > To: Patrick K. O'Brien > > Subject: underscore kills command completion > > > > > > I never tried using a on_ handler in the shell before, so I'm just now > > seeing this problem. Open up any PythonCard sample with the > shell and then > > type > > bg.on > > to get to the first event handler, then when you type the underscore the > > completion window goes away. > > > > ka > > > > > > _______________________________________________ > > PyCrust-users mailing list > > PyC...@li... > > https://lists.sourceforge.net/lists/listinfo/pycrust-users > > > _______________________________________________ > PyCrust-users mailing list > PyC...@li... > https://lists.sourceforge.net/lists/listinfo/pycrust-users > |
|
From: Patrick K. O'B. <po...@or...> - 2002-02-05 18:17:21
|
I'm not seeing this problem under Python 2.1.2 or Python 2.2. Kevin, what version of Python are you running? --- Patrick K. O'Brien Orbtech > -----Original Message----- > From: pyc...@li... > [mailto:pyc...@li...]On Behalf Of Patrick > K. O'Brien > Sent: Monday, February 04, 2002 5:51 PM > To: pycr > Subject: [PyCrust] FW: underscore kills command completion > > > Neil or Robin, > > Is this expected behavior for wxSTC, or am I doing something wrong? > > --- > Patrick K. O'Brien > Orbtech > > -----Original Message----- > From: Kevin Altis [mailto:al...@se...] > Sent: Monday, February 04, 2002 4:13 PM > To: Patrick K. O'Brien > Subject: underscore kills command completion > > > I never tried using a on_ handler in the shell before, so I'm just now > seeing this problem. Open up any PythonCard sample with the shell and then > type > bg.on > to get to the first event handler, then when you type the underscore the > completion window goes away. > > ka > > > _______________________________________________ > PyCrust-users mailing list > PyC...@li... > https://lists.sourceforge.net/lists/listinfo/pycrust-users |
|
From: Patrick K. O'B. <po...@or...> - 2002-02-04 23:47:20
|
Neil or Robin, Is this expected behavior for wxSTC, or am I doing something wrong? --- Patrick K. O'Brien Orbtech -----Original Message----- From: Kevin Altis [mailto:al...@se...] Sent: Monday, February 04, 2002 4:13 PM To: Patrick K. O'Brien Subject: underscore kills command completion I never tried using a on_ handler in the shell before, so I'm just now seeing this problem. Open up any PythonCard sample with the shell and then type bg.on to get to the first event handler, then when you type the underscore the completion window goes away. ka |
|
From: Syver E. <syv...@on...> - 2002-01-13 13:28:27
|
PyCrust disables as is disables some of the standard bindings for
copying, deleting and inserting text.
The following code fixes the problem:
From shell.Shell method OnKeyDown
# Don't toggle between insert mode and overwrite mode.
elif key == WXK_INSERT and not (event.ShiftDown() or event.ControlDown()):
pass
The only added code is :
and not (event.ShiftDown() or event.ControlDown())
--
Vennlig hilsen
Syver Enstad
|
|
From: Robin D. <ro...@al...> - 2001-11-30 01:34:22
|
> Can anyone offer suggestions on the best way to handle the issues explained > in the message below? Thanks. > Try 2.3.2. I made a bunch of changes to try and fix this in the wxSTC C++ code, but not having this type of keyboard means that I am just making changes blindly. I really need somebody with a non-US keyboard and C++ skills to dig in and figure out what it needs... -- Robin Dunn Software Craftsman ro...@Al... Java give you jitters? http://wxPython.org Relax with wxPython! |
|
From: Patrick K. O'B. <po...@or...> - 2001-11-29 19:46:08
|
Can anyone offer suggestions on the best way to handle the issues explained in the message below? Thanks. --- Patrick K. O'Brien Orbtech.com - Your Source For Python Development Services -----Original Message----- From: Jean-Michel Fauth [mailto:jm...@bl...] Sent: Thursday, November 22, 2001 4:10 PM To: po...@or... Subject: PyCrust - patch Hello Patrick K. O'Brien Subject: PyCrust - I cooked your pie five minutes more... 1) I only have a phone connection. That's why I send this message directly to you mail address. Sourceforge is slow and I don't undestand very well how it works. 2) I am a new pythonist and find this language very nice (and powerfull). I tested all the editors, IDE, development tools... I could find on the web. After some personal tests, I decided to stay on wxPython and python of course. wxPython seems to be a brilliant work, it does everything I need and even more. I specially appreciate all the stuff for printing: wxPreviewCanvas, wxPrintData,... All these things that I cann't do with tkinter. For larger application, I am using wscite, the Scintilla editor (very good). One of the good points with python, it is the interpreter and its interactive window. I am not really happy with IDLE or IDLE-fork. PyCrust comes just in time for me. 3) I am using Python 2.1.1, wxPython 2.3.1 and window 98SE 4) PyCrust works fine on my machine, except for one point. It can not be used by people, who have an european keyboard. I mean a keyboard where you have to press Ctrl+Alt (or the special key AltGr, that combines both keys) in order to get the following characters: #, ¦ @ [ ] { } \ |. As you can see, these chars are quite important! If you cann't type them, bye, bye Python and PyCrust. I do know how many people are using PyCrust or PyShell, but I didn't find any people complaining about that. I found a solution, that's the reason for my mail. This is done in 2 steps. First, I created the following file, called kbddict.py #--------------------------------------------- # module kbddict.py # # 22 November 2001 # # - keyboard dictionnaries for european keyboards # - to be used with PyCrust and PyShell # - comment the unused langages # - tested with swiss french and swiss german # - in order to work properly, need a modification of the file shell.py #--------------------------------------------- # swiss french keyboard # mapping keys is not necessary for the dead keys ´ (219) and ~ (221) ?! kbd_dict = {51: '#', 50: '@', 49: '¦', 56: '¢', 186: '[', 192: ']', \ 220: '{', 223: '}', 226: '\\', 54: '¬', 55: '|', 69: ''} # swiss german keyboard # same as swiss french # mapping keys is not necessary for the dead keys ´ (219) and ~ (221) ?! #kbd_dict = {51: '#', 50: '@', 49: '¦', 56: '¢', 186: '[', 192: ']', \ # 220: '{', 223: '}', 226: '\\', 54: '¬', 55: '|', 69: ''} # insert other keyboard here #kbd_dict = {} #eof--------------------------------------------- This file creates dictionnaries for keys mapping. Secondly, I modified the file shell.py in the following way. In the 'import section', I added the following line: from kbddict import kbd_dict Then I modified the following method. def OnKeyDown(self, event): """Key down event handler. The main goal here is to not allow modifications to previous lines of text.""" key = event.KeyCode() ... ... ... elif key == WXK_INSERT: pass # added by jmf # keycode 219: ´and 221: ~ (dead keys) work ok !? elif event.ControlDown() and event.AltDown(): if key in kbd_dict.keys(): self.write(kbd_dict[key]) # end of added ... else: event.Skip() 5) I am speaking french and german, so I tested the both keyboards, swiss french and swiss german, with success. The keyboard list can be extended. 6) Despite the fact that it is working fine, I don't think, this is the solution to be used. The problem lies in ths wxStyledTextCtrl, this control does not manage the chars # \ @ [ ] ... correctly, the control wxTextCtrl does it! (I did not inform the wxPython.org). I noticed the same problem in the Boa constructor. Python is portable, but it must be portable for all languages and keyboards. 7) A final remark. I created an exe with py2exe. Icon are not allowed when using win98, 98SE or winME. 8) PyCrust is a delicious cake. It is certainly a good advertisement for wxPython and Python. Best regards. Jean-Michel Fauth, Martigny, Switzerland, an amateur programmer. jm...@bl... |
|
From: Patrick K. O'B. <po...@or...> - 2001-11-20 17:57:35
|
This didn't get answered on the PyCrust list, so I thought I'd bump it up to the wxPython list. --- Patrick K. O'Brien Orbtech "I am, therefore I think." -----Original Message----- From: pyc...@li... [mailto:pyc...@li...]On Behalf Of Patrick K. O'Brien Sent: Wednesday, November 14, 2001 5:01 PM To: Robin Dunn; Pycrust-Users Subject: RE: [PyCrust] clipboard destroyed on program exit Is there any way to force wxPython to put the data on the clipboard, rather than just a promise? This seems like something that should be decided by each application, no? --- Patrick K. O'Brien Orbtech "I am, therefore I think." -----Original Message----- From: pyc...@li... [mailto:pyc...@li...]On Behalf Of Robin Dunn Sent: Monday, November 12, 2001 10:09 AM To: Pycrust-Users Subject: Re: [PyCrust] clipboard destroyed on program exit I believe wxWindows uses the promise method. --Robin Kevin: > Patrick thought I should bring this up here to see if Neil or Robin have > any ideas what causes this? Is there something in wxPython or > Scintilla that is messing with the clipboard when the app exits? I've > never seen this issue when copying text from a wxTextCtrl and > then exiting an app, it only happens with the PyCrust shell. This is on Windows? On X/Linux this is hard to fix as you only provide 'promises' (in Mac terms) of your clipboard value. Then when another app wants to paste, you are sent a message and you provide the full contents of the clipboard. On Windows, you can either provide promises or data. The reason for promises is the cost in rendering and storing the selection in all possibly required formats when processing the copy/cut commands. Because of this deep platform difference (and even worse, the asynchrony required on X), Scintilla leaves it up to the platform adaptation layer to handle clipboard operations. So it is up to Robin ;) Neil |
|
From: Patrick K. O'B. <po...@or...> - 2001-11-15 00:28:50
|
Is there any way to force wxPython to put the data on the clipboard, rather than just a promise? This seems like something that should be decided by each application, no? --- Patrick K. O'Brien Orbtech "I am, therefore I think." -----Original Message----- From: pyc...@li... [mailto:pyc...@li...]On Behalf Of Robin Dunn Sent: Monday, November 12, 2001 10:09 AM To: Pycrust-Users Subject: Re: [PyCrust] clipboard destroyed on program exit I believe wxWindows uses the promise method. --Robin |
|
From: Robin D. <ro...@al...> - 2001-11-12 16:09:25
|
I believe wxWindows uses the promise method.
--Robin
----- Original Message -----
From: "Patrick K. O'Brien" <po...@or...>
To: "Pycrust-Users" <pyc...@li...>
Sent: Monday, November 12, 2001 5:08 AM
Subject: RE: [PyCrust] clipboard destroyed on program exit
> Here is how I have coded the cut and copy operations:
>
> def Cut(self):
> """Remove selection and place it on the clipboard."""
> if self.CanCut() and self.CanCopy():
> if self.AutoCompActive(): self.AutoCompCancel()
> if self.CallTipActive: self.CallTipCancel()
> self.Copy()
> self.ReplaceSelection('')
>
> def Copy(self):
> """Copy selection and place it on the clipboard."""
> if self.CanCopy():
> command = self.GetSelectedText()
> command = command.replace(os.linesep + sys.ps2, os.linesep)
> command = command.replace(os.linesep + sys.ps1, os.linesep)
> command = self.lstripPrompt(text=command)
> data = wxTextDataObject(command)
> if wxTheClipboard.Open():
> wxTheClipboard.SetData(data)
> wxTheClipboard.Close()
>
> def CopyWithPrompts(self):
> """Copy selection, including prompts, and place it on the
> clipboard."""
> if self.CanCopy():
> command = self.GetSelectedText()
> data = wxTextDataObject(command)
> if wxTheClipboard.Open():
> wxTheClipboard.SetData(data)
> wxTheClipboard.Close()
>
> ---
> Patrick K. O'Brien
> Orbtech
> "I am, therefore I think."
>
> -----Original Message-----
> From: pyc...@li...
> [mailto:pyc...@li...]On Behalf Of Neil
Hodgson
> Sent: Monday, November 12, 2001 2:46 AM
> To: Pycrust-Users
> Subject: Re: [PyCrust] clipboard destroyed on program exit
>
> Kevin:
>
> > Patrick thought I should bring this up here to see if Neil or Robin have
> > any ideas what causes this? Is there something in wxPython or
> > Scintilla that is messing with the clipboard when the app exits? I've
> > never seen this issue when copying text from a wxTextCtrl and
> > then exiting an app, it only happens with the PyCrust shell.
>
> This is on Windows? On X/Linux this is hard to fix as you only provide
> 'promises' (in Mac terms) of your clipboard value. Then when another app
> wants to paste, you are sent a message and you provide the full contents
of
> the clipboard. On Windows, you can either provide promises or data. The
> reason for promises is the cost in rendering and storing the selection in
> all possibly required formats when processing the copy/cut commands.
Because
> of this deep platform difference (and even worse, the asynchrony required
on
> X), Scintilla leaves it up to the platform adaptation layer to handle
> clipboard operations. So it is up to Robin ;)
>
> Neil
>
>
>
> _______________________________________________
> PyCrust-users mailing list
> PyC...@li...
> https://lists.sourceforge.net/lists/listinfo/pycrust-users
>
>
> _______________________________________________
> PyCrust-users mailing list
> PyC...@li...
> https://lists.sourceforge.net/lists/listinfo/pycrust-users
>
|
|
From: Patrick K. O'B. <po...@or...> - 2001-11-12 13:04:45
|
Here is how I have coded the cut and copy operations:
def Cut(self):
"""Remove selection and place it on the clipboard."""
if self.CanCut() and self.CanCopy():
if self.AutoCompActive(): self.AutoCompCancel()
if self.CallTipActive: self.CallTipCancel()
self.Copy()
self.ReplaceSelection('')
def Copy(self):
"""Copy selection and place it on the clipboard."""
if self.CanCopy():
command = self.GetSelectedText()
command = command.replace(os.linesep + sys.ps2, os.linesep)
command = command.replace(os.linesep + sys.ps1, os.linesep)
command = self.lstripPrompt(text=command)
data = wxTextDataObject(command)
if wxTheClipboard.Open():
wxTheClipboard.SetData(data)
wxTheClipboard.Close()
def CopyWithPrompts(self):
"""Copy selection, including prompts, and place it on the
clipboard."""
if self.CanCopy():
command = self.GetSelectedText()
data = wxTextDataObject(command)
if wxTheClipboard.Open():
wxTheClipboard.SetData(data)
wxTheClipboard.Close()
---
Patrick K. O'Brien
Orbtech
"I am, therefore I think."
-----Original Message-----
From: pyc...@li...
[mailto:pyc...@li...]On Behalf Of Neil Hodgson
Sent: Monday, November 12, 2001 2:46 AM
To: Pycrust-Users
Subject: Re: [PyCrust] clipboard destroyed on program exit
Kevin:
> Patrick thought I should bring this up here to see if Neil or Robin have
> any ideas what causes this? Is there something in wxPython or
> Scintilla that is messing with the clipboard when the app exits? I've
> never seen this issue when copying text from a wxTextCtrl and
> then exiting an app, it only happens with the PyCrust shell.
This is on Windows? On X/Linux this is hard to fix as you only provide
'promises' (in Mac terms) of your clipboard value. Then when another app
wants to paste, you are sent a message and you provide the full contents of
the clipboard. On Windows, you can either provide promises or data. The
reason for promises is the cost in rendering and storing the selection in
all possibly required formats when processing the copy/cut commands. Because
of this deep platform difference (and even worse, the asynchrony required on
X), Scintilla leaves it up to the platform adaptation layer to handle
clipboard operations. So it is up to Robin ;)
Neil
_______________________________________________
PyCrust-users mailing list
PyC...@li...
https://lists.sourceforge.net/lists/listinfo/pycrust-users
|
|
From: Neil H. <ne...@sc...> - 2001-11-12 08:46:10
|
Kevin: > Patrick thought I should bring this up here to see if Neil or Robin have > any ideas what causes this? Is there something in wxPython or > Scintilla that is messing with the clipboard when the app exits? I've > never seen this issue when copying text from a wxTextCtrl and > then exiting an app, it only happens with the PyCrust shell. This is on Windows? On X/Linux this is hard to fix as you only provide 'promises' (in Mac terms) of your clipboard value. Then when another app wants to paste, you are sent a message and you provide the full contents of the clipboard. On Windows, you can either provide promises or data. The reason for promises is the cost in rendering and storing the selection in all possibly required formats when processing the copy/cut commands. Because of this deep platform difference (and even worse, the asynchrony required on X), Scintilla leaves it up to the platform adaptation layer to handle clipboard operations. So it is up to Robin ;) Neil |
|
From: Kevin A. <al...@se...> - 2001-11-12 03:19:15
|
For a long time I've been annoyed that the clipboard appears to be destroyed when exiting a PythonCard app when PyCrust is running. Until tonight I didn't think to investigate this problem. This typically shows up for me when I copy some text from the PyCrust shell and then exit the app and then try and paste into Notepad or email only to find that the text is not in the clipboard. If you do the copy/paste before the app exits, the text is okay. Patrick thought I should bring this up here to see if Neil or Robin have any ideas what causes this? Is there something in wxPython or Scintilla that is messing with the clipboard when the app exits? I've never seen this issue when copying text from a wxTextCtrl and then exiting an app, it only happens with the PyCrust shell. ka |
|
From: Patrick K. O'B. <po...@or...> - 2001-11-08 19:55:55
|
Version 7.0, currently in CVS only, is very stable for me. Im also running it with wxPython 2.3.2 (beta 6), which may have something to do with it, as 2.3.2 is much improved over 2.3.1. I would recommend getting the version from CVS, if you can. If you cant, I can send you the files. I havent tested it with wxPython 2.3.1 as there are too many problems with that version, but it might still be better than what you are experiencing. If anyone else has had this problem they havent complained, but should certainly feel free to do so. --- Patrick K. O'Brien Orbtech "I am, therefore I think." -----Original Message----- From: pyc...@li... [mailto:pyc...@li...]On Behalf Of eric Sent: Thursday, November 08, 2001 12:42 PM To: pyc...@li... Subject: [PyCrust] 0.6 crashes on w2k wx2.3.1, Python 2.1 Hello, I'm having some strange behavior when running PyCrust 0.6 on W2K that either crashes my machine or causes me to have to shut down my machine. PyCrust runs just fine for maybe 30 minutes or even much longer. But after a while, the screen on my computer goes berzerk with random windows flashing up, no mouse showing, and even an occasional blue screen reboot. This can happen even when PyCrust is in the background. It doesn't appear to have anything to do with what code has been executed in the shell (though I am not positive about this) since it has happened to me many different times . Its an unpleasant problem to debug since it seems to run fine for so long. I'm using wxPython 2.3.1 and Python 2.1. Other apps using both of these will run for days at a time without issue. I'd like to know (1) if others are seeing the same problem. (2) if anyone has any hints on what might be happening here. thanks, eric |
|
From: Robin D. <ro...@al...> - 2001-11-08 19:54:55
|
Try wxPython 2.3.2b6. 2.3.1 had some problems. -- Robin Dunn Software Craftsman ro...@Al... Java give you jitters? http://wxPython.org Relax with wxPython! ----- Original Message -----=20 From: eric=20 To: pyc...@li...=20 Sent: Thursday, November 08, 2001 10:41 AM Subject: [PyCrust] 0.6 crashes on w2k wx2.3.1, Python 2.1 Hello, I'm having some strange behavior when running PyCrust 0.6 on W2K that = either crashes my machine or causes me to have to shut down my machine. = PyCrust runs just fine for maybe 30 minutes or even much longer. But = after a while, the screen on my computer goes berzerk with random = windows flashing up, no mouse showing, and even an occasional blue = screen reboot. This can happen even when PyCrust is in the background. = It doesn't appear to have anything to do with what code has been = executed in the shell (though I am not positive about this) since it has = happened to me many different times . Its an unpleasant problem to debug since it seems to run fine for so = long. I'm using wxPython 2.3.1 and Python 2.1. Other apps using both = of these will run for days at a time without issue. I'd like to know (1) if others are seeing the same problem. (2) if = anyone has any hints on what might be happening here. thanks, eric |
|
From: eric <er...@sc...> - 2001-11-08 19:39:53
|
Hello, I'm having some strange behavior when running PyCrust 0.6 on W2K that = either crashes my machine or causes me to have to shut down my machine. = PyCrust runs just fine for maybe 30 minutes or even much longer. But = after a while, the screen on my computer goes berzerk with random = windows flashing up, no mouse showing, and even an occasional blue = screen reboot. This can happen even when PyCrust is in the background. = It doesn't appear to have anything to do with what code has been = executed in the shell (though I am not positive about this) since it has = happened to me many different times . Its an unpleasant problem to debug since it seems to run fine for so = long. I'm using wxPython 2.3.1 and Python 2.1. Other apps using both = of these will run for days at a time without issue. I'd like to know (1) if others are seeing the same problem. (2) if = anyone has any hints on what might be happening here. thanks, eric |
|
From: Patrick K. O'B. <po...@or...> - 2001-11-06 23:41:33
|
Thanks for patch. Sorry about my stupidity. (It worked fine on my machine.
<wink>)
---
Patrick K. O'Brien
Orbtech
"I am, therefore I think."
-----Original Message-----
From: pyc...@li...
[mailto:pyc...@li...]On Behalf Of Jochen Küpper
Sent: Saturday, November 03, 2001 9:40 PM
To: pyc...@li...
Subject: [PyCrust] setup
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Importing PyCrust before installing it doesn't work:(
Index: setup.py
===================================================================
RCS file: /cvsroot/pycrust/PyCrust/setup.py,v
retrieving revision 1.3
diff -u -r1.3 setup.py
- --- setup.py 2001/10/25 14:33:37 1.3
+++ setup.py 2001/11/04 03:36:56
@@ -8,11 +8,10 @@
__version__ = "$Revision: 1.3 $"[11:-2]
from distutils.core import setup
- -from PyCrust import version
import glob
setup(name="PyCrust",
- - version=str(version.VERSION),
+ version="0.7",
description="PyCrust - The Flakiest Python Shell",
author="Patrick K. O'Brien",
author_email="po...@or...",
@@ -35,4 +34,3 @@
],
)
- -
\ No newline at end of file
Greetings,
Jochen
PS: I am not on the list.
- --
Einigkeit und Recht und Freiheit http://www.Jochen-Kuepper.de
Liberté, Égalité, Fraternité GnuPG key: 44BCCD8E
Sex, drugs and rock-n-roll
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Processed by Mailcrypt and GnuPG <http://www.gnupg.org/>
iD8DBQE75Lh4iJ/aUUS8zY4RAoVrAKCS5v+JA7ugwjLyiifjcpqc0vPxxACgvX43
gCn8Z/dPsjeYxgeT+ZkDnhI=
=CA8t
-----END PGP SIGNATURE-----
_______________________________________________
PyCrust-users mailing list
PyC...@li...
https://lists.sourceforge.net/lists/listinfo/pycrust-users
|
|
From: Jochen <jo...@jo...> - 2001-11-04 03:39:47
|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Importing PyCrust before installing it doesn't work:(
Index: setup.py
===================================================================
RCS file: /cvsroot/pycrust/PyCrust/setup.py,v
retrieving revision 1.3
diff -u -r1.3 setup.py
- --- setup.py 2001/10/25 14:33:37 1.3
+++ setup.py 2001/11/04 03:36:56
@@ -8,11 +8,10 @@
__version__ = "$Revision: 1.3 $"[11:-2]
from distutils.core import setup
- -from PyCrust import version
import glob
setup(name="PyCrust",
- - version=str(version.VERSION),
+ version="0.7",
description="PyCrust - The Flakiest Python Shell",
author="Patrick K. O'Brien",
author_email="po...@or...",
@@ -35,4 +34,3 @@
],
)
- -
\ No newline at end of file
Greetings,
Jochen
PS: I am not on the list.
- --
Einigkeit und Recht und Freiheit http://www.Jochen-Kuepper.de
Liberté, Égalité, Fraternité GnuPG key: 44BCCD8E
Sex, drugs and rock-n-roll
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Processed by Mailcrypt and GnuPG <http://www.gnupg.org/>
iD8DBQE75Lh4iJ/aUUS8zY4RAoVrAKCS5v+JA7ugwjLyiifjcpqc0vPxxACgvX43
gCn8Z/dPsjeYxgeT+ZkDnhI=
=CA8t
-----END PGP SIGNATURE-----
|
|
From: Patrick K. O'B. <po...@or...> - 2001-10-22 23:33:18
|
The CVS version of PyCrust now has basic "smart" cut/copy/paste!!! I'll add a few more bells and whistles, but the current implementation has most of what you might want. What might that be? Well, all calls to cut/copy/paste are intercepted and translated to deal with line endings, secondary prompts, etc. For example, that means you can copy a function definition from a source file and paste it into the PyCrust shell and the line endings (of any style) will convert to os.linesep + sys.ps2. Likewise, commands selected in the shell will be stripped of their secondary prompts so you can paste them into a source file or email without having to delete all the "... " prefixes. What I intend to add next is a way to control whether or not to strip out the prompts when you cut or copy. I'd like to make this work with the default keybindings for cut and copy, so one idea I had was that if the selection *included* the primary prompt ">>> ", then all the secondary prompts would be left intact. If the selection did *not* include the primary prompt, then all the secondary prompts would be stripped out. Does that sound like a reasonable feature? Once again, I invite you to sample our latest creation and give it a nibble. --- Patrick K. O'Brien Orbtech "I am, therefore I think." |
|
From: Patrick K. O'B. <po...@or...> - 2001-10-19 15:38:26
|
The CVS version of PyCrust now has full support for multi-line commands. You can scroll back to any line of a multi and the whole command is copied down where it can be modified, including adding and deleting lines. The command history retrieval functions (Ctrl-Up or Alt-P, Ctrl-Down or Alt-N, F8) all retrieve entire multi-line commands as well. The retrieval method has been modified as well so that retrieved commands are inserted into the existing command (and highlighted), making it easier to build new commands that make use of old commands. Give it a try and let me know if anything breaks. P.S. The current CVS version also works with wxPython 2.3.2b6, for any of you testing the beta. --- Patrick K. O'Brien Orbtech "I am, therefore I think." |
1 message has been excluded from this view by a project administrator.
