[wxPython] Mail delivery failed: returning message to sender

Mail_Delivery_Syste2 · September 10, 2001, 2:52pm

This message was created automatically by mail delivery software (Exim).

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  jhsh@freemail.absa.co.za
    Connection refused:
    retry timeout exceeded

------ This is a copy of the message, including all the headers. ------

Resent-from: JHSH.BIOCHEM.LAND.PERS.SU@AKAD.SUN.AC.ZA
Resent-to: jhsh@freemail.absa.co.za
Resent-Date: Mon, 10 Sep 2001 23:05:32 +0200
MIME-version: 1.0
Content-type: text/plain
Sender: wxpython-users-admin@lists.wxwindows.org
Errors-To: wxpython-users-admin@lists.wxwindows.org
Precedence: bulk
Message-Id: <E15gYD9-0002mM-00@first.cirl.uoregon.edu>
Resent-Message-Id: <E15gYFW-0006DS-00@maties1.sun.ac.za>

Send wxpython-users mailing list submissions to
wxpython-users@lists.wxwindows.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.wxwindows.org/mailman/listinfo/wxpython-users
or, via email, send a message with subject or body 'help' to
wxpython-users-request@lists.wxwindows.org

You can reach the person managing the list at
wxpython-users-admin@lists.wxwindows.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of wxpython-users digest..."

Today's Topics:

   1. FW: DrawPointList and DrawLineList (Kevin Altis)
   2. Re: FW: DrawPointList and DrawLineList (Tim Hochberg)
   3. RE: FW: DrawPointList and DrawLineList (Kevin Altis)
   4. Re: Message Watcher sizer help (Donnal Walter)
   5. Re: wxSTC font sizes too small (Robin Dunn)
   6. Re: FW: DrawPointList and DrawLineList (Tim Hochberg)
   7. Re: FW: DrawPointList and DrawLineList (Chris Barker)
   8. Re: FW: DrawPointList and DrawLineList (Robin Dunn)
   9. RE: FW: DrawPointList and DrawLineList (Kevin Altis)
  10. RE: wxSTC font sizes too small (Patrick K. O'Brien)

···

From: wxpython-users-request@lists.wxwindows.org
Subject: wxpython-users digest, Vol 1 #352 - 10 msgs
To: wxpython-users@lists.wxwindows.org
Reply-To: wxpython-users@lists.wxwindows.org
Date: Mon, 10 Sep 2001 14:03:20 -0700

--__--__--

Message: 1
From: "Kevin Altis" <altis@semi-retired.com>
To: "Wxpython-Users" <wxpython-users@lists.wxwindows.org>
Date: Mon, 10 Sep 2001 11:51:14 -0700
Subject: [wxPython] FW: DrawPointList and DrawLineList
Reply-To: wxpython-users@lists.wxwindows.org

I'm forwarding this email to the list in the hopes that other people that
are interested in a higher performance method of drawing to a DC and that
know some C++ might be able to help.

Originally, I was thinking that it would be simplest to just provide a list
of points or lines. However, after looking at some other drawing APIs, it
probably makes sense to support a pen and brush as part of the argument
list. I could see wanting to draw a series of lines in a given color, with a
particular brush pattern, and copy mode (XOR...)

Other ideas? Any C++ coders here that could take this on?

ka

-----Original Message-----
From: cbarker@waves.hazmat.noaa.gov
[mailto:cbarker@waves.hazmat.noaa.gov]On Behalf Of Chris Barker
Sent: Monday, September 10, 2001 11:59 AM
To: Kevin Altis
Cc: Robin Dunn
Subject: Re: FW: Possible contribution for PythonCard

Kevin Altis wrote:

Robin,
Would it
be possible to provide two methods in wxPython 2.3.2 that would accept a
list of points (DrawPointList) and lines (DrawLinesList) that would then
call the appropriate C++ routines directly for each item in the list to
improve performance?

Kevin (and Robin),

Robin and I discussed this a while ago, and I think the short version is
(Robin, please correct and clarify as you see fit):

Yes, it could be done, and would probably help

Yes, it could be integrated into the wxPython code without too much
trouble

Yes, Robin would help with that part

But: someone would have to actually write the code!

I am interested in doing it, but I have no experience with either SWIG
or C++ (and only a little C) so it would be a lot for me to take on, so
I havn't started yet. I'm probably going to be using wxPython for a
project I'm working on were this would be a big help, and I have a
couple of experienced C++ progarmmeres helping me, so I may get to it.
However, we're on a tight schedule, so If I can get the performance I
need without it, it won't happen.

I wish I could contribute more, but we all have more things we'd like to
do than time to do them!

Chris probably has some other suggestions as well.

Yes, I do. both for performance and easier coding. Let's face it, how
often does someone have a single point to draw? THe data is probably
already in a sequence of some kind, so why not use it directly? I'm full
of ideas, if anyone else wants to impliment them!

-Chris

--__--__--

Message: 2
From: "Tim Hochberg" <tim.hochberg@ieee.org>
To: <wxpython-users@lists.wxwindows.org>
Subject: Re: [wxPython] FW: DrawPointList and DrawLineList
Date: Mon, 10 Sep 2001 12:35:18 -0700
Reply-To: wxpython-users@lists.wxwindows.org

Hi Kevin, etc.

I could probably be persuaded to do this. I've mucked around in this area of
the wxPython internals before so that I expect that it should be relatively
straightforward (famous last words....). However, since this is just for fun
and I'm busy at the moment, it would probably be at least a couple of weeks
before I could get to it. (Offers of beer have been known to speed me up
however....)

As to syntax, has the Draw<Thing>List syntax been blessed by Robin? It seems
reasonable to me in that it would be extensible to DrawPolygonList, etc if
someone later gets the urge. As far as Pens and Brushes go, I think that
only the pen is used for lines and points, so need to worry about the brush.
I would propose something like the following:

dc.DrawPointsList(points, pens=None)

If 'pens' is None, the current pen is used, otherwise 'pens' would be a list
equal in length to 'points'. This would be equivalent to:

N = len(points)
assert (pens is None or len(pens) == len(points), 'lengths of pens and
points must match')
for i in range(N):
   if pens:
      dc.SetPen(pens[i])
   dc.DrawPoint(points[i])

dc.DrawLines would be analogous.

-tim

----- Original Message -----
From: "Kevin Altis" <altis@semi-retired.com>
To: "Wxpython-Users" <wxpython-users@lists.wxwindows.org>
Sent: Monday, September 10, 2001 11:51 AM
Subject: [wxPython] FW: DrawPointList and DrawLineList

I'm forwarding this email to the list in the hopes that other people that
are interested in a higher performance method of drawing to a DC and that
know some C++ might be able to help.

Originally, I was thinking that it would be simplest to just provide a

list

of points or lines. However, after looking at some other drawing APIs, it
probably makes sense to support a pen and brush as part of the argument
list. I could see wanting to draw a series of lines in a given color, with

a

particular brush pattern, and copy mode (XOR...)

Other ideas? Any C++ coders here that could take this on?

ka

-----Original Message-----
From: cbarker@waves.hazmat.noaa.gov
[mailto:cbarker@waves.hazmat.noaa.gov]On Behalf Of Chris Barker
Sent: Monday, September 10, 2001 11:59 AM
To: Kevin Altis
Cc: Robin Dunn
Subject: Re: FW: Possible contribution for PythonCard

Kevin Altis wrote:
> Robin,
> Would it
> be possible to provide two methods in wxPython 2.3.2 that would accept a
> list of points (DrawPointList) and lines (DrawLinesList) that would then
> call the appropriate C++ routines directly for each item in the list to
> improve performance?

Kevin (and Robin),

Robin and I discussed this a while ago, and I think the short version is
(Robin, please correct and clarify as you see fit):

Yes, it could be done, and would probably help

Yes, it could be integrated into the wxPython code without too much
trouble

Yes, Robin would help with that part

But: someone would have to actually write the code!

I am interested in doing it, but I have no experience with either SWIG
or C++ (and only a little C) so it would be a lot for me to take on, so
I havn't started yet. I'm probably going to be using wxPython for a
project I'm working on were this would be a big help, and I have a
couple of experienced C++ progarmmeres helping me, so I may get to it.
However, we're on a tight schedule, so If I can get the performance I
need without it, it won't happen.

I wish I could contribute more, but we all have more things we'd like to
do than time to do them!

> Chris probably has some other suggestions as well.

Yes, I do. both for performance and easier coding. Let's face it, how
often does someone have a single point to draw? THe data is probably
already in a sequence of some kind, so why not use it directly? I'm full
of ideas, if anyone else wants to impliment them!

-Chris

_______________________________________________
wxpython-users mailing list
wxpython-users@lists.wxwindows.org
http://lists.wxwindows.org/mailman/listinfo/wxpython-users

--__--__--

Message: 3
From: "Kevin Altis" <altis@semi-retired.com>
To: <wxpython-users@lists.wxwindows.org>
Subject: RE: [wxPython] FW: DrawPointList and DrawLineList
Date: Mon, 10 Sep 2001 12:53:30 -0700
Reply-To: wxpython-users@lists.wxwindows.org

From: Tim Hochberg

I could probably be persuaded to do this. I've mucked around in
this area of
the wxPython internals before so that I expect that it should be
relatively
straightforward (famous last words....). However, since this is
just for fun
and I'm busy at the moment, it would probably be at least a
couple of weeks
before I could get to it. (Offers of beer have been known to speed me up
however....)

So where should the beer be sent?

As to syntax, has the Draw<Thing>List syntax been blessed by
Robin? It seems
reasonable to me in that it would be extensible to DrawPolygonList, etc if
someone later gets the urge. As far as Pens and Brushes go, I think that
only the pen is used for lines and points, so need to worry about
the brush.
I would propose something like the following:

dc.DrawPointsList(points, pens=None)

If 'pens' is None, the current pen is used, otherwise 'pens'
would be a list
equal in length to 'points'. This would be equivalent to:

N = len(points)
assert (pens is None or len(pens) == len(points), 'lengths of pens and
points must match')
for i in range(N):
   if pens:
      dc.SetPen(pens[i])
   dc.DrawPoint(points[i])

dc.DrawLines would be analogous.

Actually, I don't think you want to accept a pen list, the overhead for
setting the pen with each draw operation is huge, so it is better to just
set it once prior to the loop. There could be another version of the drawing
that does accept a list of pens, but my guess is that the user code would be
better off chunking the operation to use a single pen for each group of
points or lines rather than have a pen set for every single point/line
regardless of whether it was necessary. SetOptimization should be used as
well.

The more I think about it, the more it seems like this should be a method in
wxWindows that Robin wraps to provide the list to C++ pointer array
translation or whatever is appropriate.

What do you think Robin?

ka

--__--__--

Message: 4
Date: Mon, 10 Sep 2001 12:52:56 -0700 (PDT)
From: Donnal Walter <donnalcwalter@yahoo.com>
Subject: Re: [wxPython] Message Watcher sizer help
To: wxpython-users@lists.wxwindows.org
Reply-To: wxpython-users@lists.wxwindows.org

--- Robin Dunn <robin@alldunn.com> wrote:

> Then in the
> panel, I use a wxFlexGridSizer, so that the top row can have a
> constant height and the bottom row be set growable.

wxFlexGridSizer is probably overkill as this can also be done in
a wxBoxSizer, but either way it is fine.

Yes, I can see that now. The first time I tried this with
wxBoxSixer I set one of the expandable flags incorrectly.

> Second, the wxFrame
> has its own sizer, to which the wxPanel is added.

Strictly speaking, this isn't necessary as the frame will
automatically resize the panel to fill the client area if
it is the only child.

My primary interest in Kevin's original question was in defining
one or more subclasses of wxPanel with sizers that can be used in
other windows such as other panels, notebooks, dialogs and frames.
On my first attempt it did not seem to work properly without
putting the panel in its own sizer, but adding

sizer1.Fit(parent)
sizer1.SetSizeHints(parent)

to the panel did the trick. Of course if one were to put several
panels together to make a composite, one would just add them to a
sizer as I did originally.

================================================================
from wxPython.wx import *

class MessageWatcher(wxFrame) :
    def __init__(self, parent, ID, title, pos, size):
        wxFrame.__init__(self, parent, ID, title, pos, size)
        item1 = PanelA(self, -1)

class PanelA(wxPanel):
    def __init__(self, parent, id):
        wxPanel.__init__(self, parent, id)
        sizer1 = wxBoxSizer(wxVERTICAL)
        sizer2 = wxBoxSizer(wxHORIZONTAL)
        self.hideIdle = wxCheckBox(self, -1, 'Hide idle')
        sizer2.AddWindow(self.hideIdle, 0, wxALL, 5)
        sizer2.Add(5, 5, 1)
        self.hideUnused = wxCheckBox(self, -1, 'Hide unused')
        sizer2.AddWindow(self.hideUnused, 0, wxALL, 5)
        sizer1.AddSizer(sizer2, 0, wxEXPAND)
        self.msgHistory = wxTextCtrl(self, -1, '',
                                     wxDefaultPosition,
                                     wxSize(50,100),
                                     style=wxTE_MULTILINE |
                                     wxTE_READONLY)
        sizer1.AddWindow(self.msgHistory, 1, wxEXPAND)
        sizer1.Fit(parent)
        sizer1.SetSizeHints(parent)
        self.SetSizer(sizer1)
        self.SetAutoLayout(true)
        self.Layout()

class App(wxApp):
    def OnInit(self):
        frame = MessageWatcher(None, -1, 'Message Watcher',
                               wxDefaultPosition, wxDefaultSize)
        frame.Show(true)
        self.SetTopWindow(frame)
        return true

app = App()
app.MainLoop()

=====
Donnal Walter
Arkansas Children's Hospital

__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger

--__--__--

Message: 5
From: "Robin Dunn" <robin@alldunn.com>
To: <wxpython-users@lists.wxwindows.org>
Subject: Re: [wxPython] wxSTC font sizes too small
Date: Mon, 10 Sep 2001 13:27:27 -0700
Reply-To: wxpython-users@lists.wxwindows.org

Font sizes in wxSTC appear to be off by 2, at least under windows. For
example, a specified font of Courier New size 8 actually displays as

Courier

New size 10. You can open up Notepad, Word or any other app and compare

the

font sizes. Is this a known bug/feature?

It probably has something to do with the Zoom setting.

--
Robin Dunn
Software Craftsman
robin@AllDunn.com Java give you jitters?
http://wxPython.org Relax with wxPython!

--__--__--

Message: 6
From: "Tim Hochberg" <tim.hochberg@ieee.org>
To: <wxpython-users@lists.wxwindows.org>
Subject: Re: [wxPython] FW: DrawPointList and DrawLineList
Date: Mon, 10 Sep 2001 13:33:47 -0700
Reply-To: wxpython-users@lists.wxwindows.org

Hi Kevin,

So where should the beer be sent?

You can worry about that later, if we ever decide on a syntax and I ever do
any work

[snip]

> dc.DrawPointsList(points, pens=None)
>
> If 'pens' is None, the current pen is used, otherwise 'pens'
> would be a list equal in length to 'points'.

[snip]

Actually, I don't think you want to accept a pen list, the overhead for
setting the pen with each draw operation is huge, so it is better to just
set it once prior to the loop.

That's quite possible, I don't know what the overhead of setting the pen
from C++ would be, but I don't think it matters. The overhead for doing the
check "if pens is None" is essentially zilch, so the default would be no
slower than what you want. And if someone (like me for instance) wants to
set the pen everytime, then that would work as well. I'd rather avoid having
a proliferation of similar functions (such as both DrawPointsList and
DrawPointsWithPensList) when one will do.

There could be another version of the drawing
that does accept a list of pens, but my guess is that the user code would

be

better off chunking the operation to use a single pen for each group of
points or lines rather than have a pen set for every single point/line
regardless of whether it was necessary. SetOptimization should be used as
well.

I assume you mean something equivalent to:

def drawPointsList(points)
   oldOpt = dc.GetOptimization()
   dc.SetOptimization(1)
   # draw all the points....
   dc.SetOptimization(oldOpt)

After looking at SetOptimization a bit, I have to disagree. It seems that it
would work perfectly well to set the optimization outside of the
DrawPointsList routine. And, reading the caveats on SetOptimization leaves
me feeling that we should not be messing with the optimization behind the
programmers back...

The more I think about it, the more it seems like this should be a method

in

wxWindows that Robin wraps to provide the list to C++ pointer array
translation or whatever is appropriate.

I suspect that is not necessary. Based on my experience optimizing
DrawLines, the bottleneck is going to be extracting the points from the
sequences you pass in. (Although, if you are using NumPy, this may not be
strictly true.) In any event, I'd guess we could get at least a 10x speedup
doing the 'simple' thing, and that should probably be what's tried first.
In any event there's really no need in wxWindows proper for this kind of
operation, since when writing in C++ the call overhead is much, much lower.

(Just in case this is confusing -- although I use Python psuedocode for all
my examples, this would all be written in C++ and would probably look a lot
like the code wxPoint_LIST_helper from helpers.cpp in the wxPython
distribution.)

-tim

--__--__--

Message: 7
Date: Mon, 10 Sep 2001 13:58:41 -0700
From: Chris Barker <chrishbarker@home.net>
To: wxpython-users@lists.wxwindows.org
Subject: Re: [wxPython] FW: DrawPointList and DrawLineList
Reply-To: wxpython-users@lists.wxwindows.org

Kevin Altis wrote:

> From: Tim Hochberg
>
> I've mucked around in
> this area of
> the wxPython internals before so that I expect that it should be
> relatively
> straightforward (famous last words....).

You did the work on wxPoint_LIST_Helper for NumPy arrays didn't you?
Nice work.

(Offers of beer have been known to speed me up however....)
So where should the beer be sent?

I'll send some too...

> As to syntax, has the Draw<Thing>List syntax been blessed by
> Robin?

The idea, yes. the syntax: not yet, we need to work it out.

It seems

> reasonable to me in that it would be extensible to DrawPolygonList, etc if
> someone later gets the urge.

Absolutely. I would love that. It's a little less critical, however, as
it's unlikely that someone would draw thousands of polygons, where
thousands of points is pretty ordinary (for me anyway). Also, the time
it takes to draw a polygon is a LOT longer that a point, so you may not
see the same kind of perfomance improvement. For symetry and nice
syntax, however, I'd love to see it.

> As far as Pens and Brushes go, I think that
> only the pen is used for lines and points, so need to worry about
> the brush.

True, but if we want to extend to polygons, ellipses, etc. we will need
the brush.

> I would propose something like the following:
>
> dc.DrawPointsList(points, pens=None)
>
> If 'pens' is None, the current pen is used, otherwise 'pens'
> would be a list

I would prefer that you could pass a singleton pen, rather than use the
current one. Not a big deal, but I think it is a little more symetric.
So the code (in Python) would be something like:

N = len(points)
assert (type(pens) == type(wxPen) or len(pens) == len(points), 'lengths
of pens and points must match')
if type(pens) == type(wxPen):
    dc.SetPen(pens[i])
    for i in range(N):
       dc.DrawPoint(points[i])
else:
    for i in range(N):
        dc.SetPen(pens[i])
        dc.DrawPoint(points[i])

Pulling the "if" ouot of the loop probably doesn't buy much, but were
doing this for speed, right?

Actually, I don't think you want to accept a pen list, the overhead for
setting the pen with each draw operation is huge, so it is better to just
set it once prior to the loop. There could be another version of the drawing
that does accept a list of pens, but my guess is that the user code would be
better off chunking the operation to use a single pen for each group of
points or lines rather than have a pen set for every single point/line
regardless of whether it was necessary.

But this code (both Tim and my versions) does allow a single pen to be
used and set once.

SetOptimization should be used as well.

What's that?

The more I think about it, the more it seems like this should be a method in
wxWindows that Robin wraps to provide the list to C++ pointer array
translation or whatever is appropriate.

I think so too. THat way is could be put in wxDC, and it would
automagically find it's way into all the DCs. I'm guessing here, but if
it was not in the superclass that all the DCs derive from, there would
have to be a separate copy in all the various DCs. Robin?

Anyway, that is an implimentation decision, that I am not the least bit
qualified to make.

I'll work on a little Python prototype of what I'm thinking, and send in
in here.

-Chris

--
Christopher Barker,
Ph.D.
ChrisHBarker@home.net --- --- ---
http://members.home.net/barkerlohmann ---@@ -----@@ -----@@
------@@@ ------@@@ ------@@@
Oil Spill Modeling ------ @ ------ @ ------ @
Water Resources Engineering ------- --------- --------
Coastal and Fluvial Hydrodynamics --------------------------------------
------------------------------------------------------------------------

--__--__--

Message: 8
From: "Robin Dunn" <robin@alldunn.com>
To: <wxpython-users@lists.wxwindows.org>
Subject: Re: [wxPython] FW: DrawPointList and DrawLineList
Date: Mon, 10 Sep 2001 13:44:15 -0700
Reply-To: wxpython-users@lists.wxwindows.org

The more I think about it, the more it seems like this should be a method

in

wxWindows that Robin wraps to provide the list to C++ pointer array
translation or whatever is appropriate.

The one problem with this is that if it were added to the C++ wxDC then it
would be a wxArray or wxList that I would have to translate to from a Python
Sequence object before calling the wx C++ method, which would essentially
add another iteration of the data and a transformation or copy of each
element. It would be much better to add optimizations like this in Python
specific methods that get added to the real class, which SWIG makes very to
do.

I don't mind adding things like this to wxPython's DC, I just don't have
time to work out what the interface and functionality should be. So if you
guys want to take on that work and come up with at least some pseudo code
(or Python) then I can do the integration and get it into wxPython.

--
Robin Dunn
Software Craftsman
robin@AllDunn.com Java give you jitters?
http://wxPython.org Relax with wxPython!

--__--__--

Message: 9
From: "Kevin Altis" <altis@semi-retired.com>
To: <wxpython-users@lists.wxwindows.org>
Subject: RE: [wxPython] FW: DrawPointList and DrawLineList
Date: Mon, 10 Sep 2001 13:50:23 -0700
Reply-To: wxpython-users@lists.wxwindows.org

> SetOptimization should be used as well.

What's that?

Actually, now that I went back and reread the docs, we probably don't need
to do anything since SetOptimization(true) is the default.

From the docs:

"wxDC::SetOptimization
void SetOptimization(bool optimize)

If optimize is TRUE (the default), this function sets optimization mode on.
This currently means that under X, the device context will not try to set a
pen or brush property if it is known to be set already. This approach can
fall down if non-wxWindows code is using the same device context or window,
for example when the window is a panel on which the windowing system draws
panel items. The wxWindows device context 'memory' will now be out of step
with reality.

Setting optimization off, drawing, then setting it back on again, is a trick
that must occasionally be employed."

ka

--__--__--

Message: 10
From: "Patrick K. O'Brien" <pobrien@orbtech.com>
To: <wxpython-users@lists.wxwindows.org>
Cc: "Scintilla-Interest" <scintilla-interest@lists.sourceforge.net>
Subject: RE: [wxPython] wxSTC font sizes too small
Date: Mon, 10 Sep 2001 16:03:52 -0500
Reply-To: wxpython-users@lists.wxwindows.org

In PyCrust:

shell.GetZoom()

0

I'm not setting the zoom at all, so I would expect the point sizes to be the
same as all other Windows apps. No?

---
Patrick K. O'Brien
Orbtech (http://www.orbtech.com)
"I am, therefore I think."

-----Original Message-----
From: wxpython-users-admin@lists.wxwindows.org
[mailto:wxpython-users-admin@lists.wxwindows.org]On Behalf Of Robin Dunn
Sent: Monday, September 10, 2001 3:27 PM
To: wxpython-users@lists.wxwindows.org
Subject: Re: [wxPython] wxSTC font sizes too small

Font sizes in wxSTC appear to be off by 2, at least under windows. For
example, a specified font of Courier New size 8 actually displays as

Courier

New size 10. You can open up Notepad, Word or any other app and compare

the

font sizes. Is this a known bug/feature?

It probably has something to do with the Zoom setting.

--
Robin Dunn
Software Craftsman
robin@AllDunn.com Java give you jitters?
http://wxPython.org Relax with wxPython!

_______________________________________________
wxpython-users mailing list
wxpython-users@lists.wxwindows.org
http://lists.wxwindows.org/mailman/listinfo/wxpython-users

--__--__--

_______________________________________________
wxpython-users mailing list
wxpython-users@lists.wxwindows.org
http://lists.wxwindows.org/mailman/listinfo/wxpython-users

End of wxpython-users Digest