pythoncard-users Mailing List for PythonCard (Page 49)

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.338 / Virus Database: 267.10.0/63 - Release Date: 03/08/2005

Thanks for the response, Bryan.

Reworking my code to use the wxGrid widget would
require a lot of code rewrites - and all I need to
know is which row and which column the user clicked.

I see that there's mentioning of a:

   MultiColumnListColumnClickEvent

in the code.  It would seem to be possible to somehow
get to the column clicked - and that would save me a
lot of effort.

May be with my next project, I will learn how to use
the wxGrid widget.

Regards,

Bryan Murdock wrote:
> On 8/4/05, kim...@ya...
> <kim...@ya...> wrote:
> 
>>Hi everyone,
>>
>>With the multi-column control, is there anyway to
>>allow the user to select a particular cell (instead
of
>>the whole row like it's doing now)?
> 
> 
> Sounds like you might want the wxGrid widget instead
of the
> multiColumntList.  I don't think that's part of
pythoncard, but you
> could still use it probably
> 
> http://wiki.wxpython.org/index.cgi/wxGrid_20Manual
> 
> Bryan
> 
> 

--
John Henry

On 8/4/05, kim...@ya...
<kim...@ya...> wrote:
> Hi everyone,
>=20
> With the multi-column control, is there anyway to
> allow the user to select a particular cell (instead of
> the whole row like it's doing now)?

Sounds like you might want the wxGrid widget instead of the
multiColumntList.  I don't think that's part of pythoncard, but you
could still use it probably

http://wiki.wxpython.org/index.cgi/wxGrid_20Manual

Bryan

Hi everyone,

With the multi-column control, is there anyway to
allow the user to select a particular cell (instead of
the whole row like it's doing now)?

As a temporary measure, I pop up a (dumb) question
after receving the mouseClick event and ask which
column he wants.

I hope that there's a way.

Thanks,

--
John Henry

Robert Pieczonka wrote:

> Hello.
>
> I'd to use gauge component in the code below. I want to show 
> Queue.quantity in  gauge (during running thread, every time when it 
> changed). I don't know which event i must use. I find some info about 
> Time event for gauge but don't understand how it works. Any suggestions?
>
The only events that a gauge will get (by default) are mouse events when 
the user clicks in, or moves over the gauge. I don't think you are 
interested in those - you simply want a timed event and want to update 
the gauge at that point in time.

Assuming hat's right - see code added below.

>
> #---gauge.rcrc.py---
>
> {'application':{'type':'Application',
>          'name':'Template',
>    'backgrounds': [
>    {'type':'Background',
>          'name':'GaugeTest',
>          'size':(187, 147),
>
>         'components': [
>
> {'type':'Gauge',
>    'name':'gauge',
>    'position':(4, 10),
>    'size':(156, 28),
>    'foregroundColor':(248, 29, 67),
>    'layout':'horizontal',
>    'max':100,
>    'value':0,
>    },
>
> {'type':'Button',
>    'name':'startbtn',
>    'position':(5, 44),
>    'label':'record',
>    },
> ] }] } }
> #---------------------------
>
>
> #--------gauge.py----------------------
> from threading import Thread
> from threading import Condition
> import time
>
> class Queue:
>    def __init__(self):
>        self.quantity=0
>
>    def produce(self):
>        self.quantity+=1
>
>    def consume(self):
>        self.quantity-=1
>          def isEmpty(self):
>        return not self.quantity
>
> class Prod(Thread):
>    def __init__(self, queue, cond):
>        Thread.__init__(self)
>        self.queue=queue
>        self.cond=cond
>          def run(self):
>        while 1:
>            self.cond.acquire()
>            self.queue.produce()
>            print "Producer produce(1),  quantity:",self.queue.quantity
>            self.cond.notifyAll()
>            self.cond.release()
>            time.sleep(1)
>   class Cons(Thread):
>    def __init__(self, queue, cond):
>        Thread.__init__(self)
>        self.queue=queue
>        self.cond=cond
>          def run(self):
>        while 1:
>            time.sleep(2)
>            self.cond.acquire()
>            while self.queue.isEmpty():
>                print "     >>>Quantity: 0. I'm waiting."
>                self.cond.wait()
>                          self.queue.consume()
>            print "     >>>Consumer consume(1), quantity:", 
> self.queue.quantity
>            self.cond.release()
>          
> from PythonCard import model
> class PythonCardWin(model.Background):
>    def on_initialize(self,event):
>        self.q=Queue()
>        self.c=Condition()
>        self.p=Prod(self.q,self.c)
>        self.c=Cons(self.q,self.c)

       self.timer = timer.Timer(self.components.gauge, -1)

>
>    def on_startbtn_mouseClick(self,event):
>        self.p.start()
>        self.c.start()

      self.timer.start(100)   # number of millisecs for timer frequency

>
>    def on_gauge_???????(self, event):      <---------------- look here

def on_gauge_timer(self, event):
       self.components.gauge.value = ????  # whatever value you need. 
range is 0 to self.components.gauge.max
                                                               #  max 
can be set in resourceEditor, or by script
       # just to show how to do it
       if ????:
           self.timer.stop()

>          
> if __name__ == '__main__':
>    app = model.Application(PythonCardWin)
>    app.MainLoop()
>
I'll try to come up with some reason to add a gauge to one of the 
samples (or with a new sample to demonstrate the gauge). If anyone has 
suggestions - or any other component type that needs a sample to 
demonstrate it - please tell me.

-- 
Alex Tweedly       http://www.tweedly.net

-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.338 / Virus Database: 267.10.0/63 - Release Date: 03/08/2005

Hello.

I'd to use gauge component in the code below. I want to show 
Queue.quantity in  gauge (during running thread, every time when it 
changed). I don't know which event i must use. I find some info about 
Time event for gauge but don't understand how it works. Any suggestions?

#---gauge.rcrc.py---

{'application':{'type':'Application',
          'name':'Template',
    'backgrounds': [
    {'type':'Background',
          'name':'GaugeTest',
          'size':(187, 147),

         'components': [

{'type':'Gauge',
    'name':'gauge',
    'position':(4, 10),
    'size':(156, 28),
    'foregroundColor':(248, 29, 67),
    'layout':'horizontal',
    'max':100,
    'value':0,
    },

{'type':'Button',
    'name':'startbtn',
    'position':(5, 44),
    'label':'record',
    },
] }] } }
#---------------------------

#--------gauge.py----------------------
from threading import Thread
from threading import Condition
import time

class Queue:
    def __init__(self):
        self.quantity=0

    def produce(self):
        self.quantity+=1

    def consume(self):
        self.quantity-=1

    def isEmpty(self):
        return not self.quantity

class Prod(Thread):
    def __init__(self, queue, cond):
        Thread.__init__(self)
        self.queue=queue
        self.cond=cond

    def run(self):
        while 1:
            self.cond.acquire()
            self.queue.produce()
            print "Producer produce(1),  quantity:",self.queue.quantity
            self.cond.notifyAll()
            self.cond.release()
            time.sleep(1)

class Cons(Thread):
    def __init__(self, queue, cond):
        Thread.__init__(self)
        self.queue=queue
        self.cond=cond

    def run(self):
        while 1:
            time.sleep(2)
            self.cond.acquire()
            while self.queue.isEmpty():
                print "     >>>Quantity: 0. I'm waiting."
                self.cond.wait()

            self.queue.consume()
            print "     >>>Consumer consume(1), quantity:", 
self.queue.quantity
            self.cond.release()

from PythonCard import model
class PythonCardWin(model.Background):
    def on_initialize(self,event):
        self.q=Queue()
        self.c=Condition()
        self.p=Prod(self.q,self.c)
        self.c=Cons(self.q,self.c)

    def on_startbtn_mouseClick(self,event):
        self.p.start()
        self.c.start()

    def on_gauge_???????(self, event):      <---------------- look here

if __name__ == '__main__':
    app = model.Application(PythonCardWin)
    app.MainLoop()

Alex Tweedly wrote on 08/02/2005 06:01:08 PM:

> Another approach (not quite so simple, I'm afraid) would be to define 
> your own background handler (this idea and code stolen from the 
> resourceEditor's way of doing gridlines). This works fine (as far as I 
> can tell) on Windows - and should, I hope, work on other systems as well 

> (assuming the resourceEditor's gridlines work)

I tried it on my Mac and it worked great. Thanks, Alex! This seems like
a pretty good workaround to this problem. Since the image components
are invisible, they don't seem to cause any problems overlapping with
other widgets, and the colors are actually drawn on the panel itself.

The only drawback is that I can't easily see these colors in the
Resource Editor as I'm editing a layout. Eventually it might
be nice to have something like this integrated into PythonCard as a
new widget so that it could be handled specially by the Resource
Editor.

Kevin Altis wrote:

> IIRC, z-order and overlapping widgets is going to be a problem on the 
> Mac in the foreseeable future. wx doesn't really support overlapping 
> widgets anyway, it is just that there are certain situations you can 
> get away with them on Windows and Linux.

Oh boy, am I glad you said that now. I was just about to set off on a 
project that would have utterly failed because it was completely 
dependent on reliable z-order and overlapping components. And of course 
I'd have been developing on Win, so it would probably have worked *most* 
of the time - leaving me baffled why sometimes I didn't get away with 
it. And eventually, I'd have put it on a Mac and discovered I'd wasted a 
lot of time.
So I'm really glad you said that now - thanks Kevin.

> Another possibility might be to use a background image which has the 
> rectangles you want and will be drawn instead of the normal background 
> window pattern; see the proof sample for an example of the use of a 
> background image. The downside is that the background image you create 
> will need to be tweaked as your layout changes, window grows, etc. but 
> it should work on all platforms.

Using an image and adjusting it for changes sounds like a nuisance, so I 
kept looking ....

Brad,

Another approach (not quite so simple, I'm afraid) would be to define 
your own background handler (this idea and code stolen from the 
resourceEditor's way of doing gridlines). This works fine (as far as I 
can tell) on Windows - and should, I hope, work on other systems as well 
(assuming the resourceEditor's gridlines work)

For this demo, I just defined Image components called "colouredArea1", 
"colouredArea2", etc. and defined their fore & backgroundColor (remember 
they're not going to be actually visible, so shouldn't be any 
platform-specific issues) - but doing this let me see in the 
resourceEditor how it should look. And using simple components like this 
means that you can use them in sizers, or adjust their size in your own 
geometry handlers. 

class MyBackground(model.Background):

    def on_initialize(self, event):
        # if you have any initialization
        # including sizer setup, do it here
        for comp in self.components.itervalues():
            if comp.name[:12] == "colouredArea":
                comp.visible = False
        self.panel.Bind(wx.EVT_ERASE_BACKGROUND, self.drawBackgroundAreas)
        self.panel.Refresh()
        pass

    def on_close(self, event):
        # Not sure why this is needed - resourceEditor doesn't appear to 
have an equivalent
        # but without this, we get attempts to use "dead" C++ objects
        self.panel.Unbind(wx.EVT_ERASE_BACKGROUND)
        event.skip()

    def drawBackgroundAreas(self, event):
        dc = event.GetDC()
        if not dc :
            dc = wx.ClientDC(self.panel)
            r = self.panel.GetUpdateRegion().GetBox()
            dc.SetClippingRegion(r.x, r.y, r.width, r.height)
        # need to set the background color to the default panel color
        brush = dc.GetBackground()
        brush.SetColour(self.panel.GetBackgroundColour())
        dc.SetBackground(brush)
        dc.Clear()
        for comp in self.components.itervalues():
            if comp.name[:12] == "colouredArea":
                dc.SetPen(wx.Pen(comp.backgroundColor, 1, wx.SOLID))
                dc.SetBrush(wx.Brush(comp.backgroundColor, wx.SOLID))
                x,y = comp.position
                sx,sy = comp.size
                dc.DrawRectangle(x,y, sx,sy)

Good luck ...

-- 
Alex Tweedly       http://www.tweedly.net

-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.338 / Virus Database: 267.9.9/62 - Release Date: 02/08/2005

Kevin Altis wrote on 08/02/2005 12:50:46 PM:

> IIRC, z-order and overlapping widgets is going to be a problem on the 
> Mac in the foreseeable future. wx doesn't really support overlapping 
> widgets anyway, it is just that there are certain situations you can 
> get away with them on Windows and Linux. 

That would explain why StaticBox doesn't work on the Mac (it blocks
mouse events to overlapping/contained widgets), except it doesn't
explain why a StaticBox works fine in a plain wx app (see below):

#---------------------- contributed by Alex Tweedly --------------------- 

class TestPanel(wx.Panel):
   def __init__(self, parent, log):
       wx.Panel.__init__(self, parent, -1)
       self.log = log
       self.count = 0

       self.lb = wx.StaticBox(self, -1, "This example uses the 
wx.StaticBox.", (45, 100), (200,400))
       self.btn = wx.Button(self, -1, "Test", (50,120))
       wx.EVT_LEFT_DOWN(self.lb, self.on_box)
       wx.EVT_LEFT_DOWN(self.btn, self.on_btn)

   def on_box(self, event):
       print "box"
   def on_btn(self, event):
       print "btn"

if __name__ == '__main__':
   import sys
   app = wx.PySimpleApp()
   frame = wx.Frame(None, -1, "title")
   TestPanel(frame, sys.stdout)
   frame.Show(True)
   app.MainLoop() 

On Aug 2, 2005, at 10:29 AM, bra...@om... wrote:

>
> Alex Tweedly <al...@tw...> wrote on 08/01/2005 05:31:59 PM:
>
>  >> bra...@om... wrote:
> >
>  >> One thing my users miss now that we've transitioned away from
>  > >FileMaker is the color.
>  >> In FileMaker, specific regions of a form were colored to help =
break
>  >> up the window
>  >> into visual groupings. This was accomplished in FileMaker through=20=

> the use of
>  >> a rectangle widget.
>  >> Does anyone have any recommendations for how to bring more color =
to
>  >> PythonCard layouts?
>
> > imageButton with no file (image) specified. set to visible,
>  > disabled, border =3D none and set the backgroundColor to what you
>  > want. =A0(just watch your layer order =A0:-)
>
> That sounds like a nifty solution, but it didn't work when I tried it=20=

> on
> the Mac. It just turns gray and is unresponsive to changes in the
> backgroundColor or foregroundColor. If I set the border to =
transparent,
> the whole image button turns transparent (still gray), but when the
> border is None, the image button obscures any overlapping widgets,
> even the ones that are supposedly in front.
>
> The Image widget worked a little better, in that I could change the
> color, but it still obscures all overlapping widgets.
>
> I'm using PythonCard .82 (latest CVS) and wxPython 2.5.3 on Mac OS=20
> 10.4.2
> with Python 2.3.5. Since I'm at home today, I don't have access to my
> work PC, but tomorrow I can try it on Windows XP.

IIRC, z-order and overlapping widgets is going to be a problem on the=20
Mac in the foreseeable future. wx doesn't really support overlapping=20
widgets anyway, it is just that there are certain situations you can=20
get away with them on Windows and Linux. Another possibility might be=20
to use a background image which has the rectangles you want and will be=20=

drawn instead of the normal background window pattern; see the proof=20
sample for an example of the use of a background image. The downside is=20=

that the background image you create will need to be tweaked as your=20
layout changes, window grows, etc. but it should work on all platforms.

ka=

Alex Tweedly <al...@tw...> wrote on 08/01/2005 05:31:59 PM:

>> bra...@om... wrote: 
> 
>> One thing my users miss now that we've transitioned away from 
> >FileMaker is the color. 
>> In FileMaker, specific regions of a form were colored to help break 
>> up the window 
>> into visual groupings. This was accomplished in FileMaker through the 
use of 
>> a rectangle widget. 
>> Does anyone have any recommendations for how to bring more color to 
>> PythonCard layouts? 

> imageButton with no file (image) specified. set to visible, 
> disabled, border = none and set the backgroundColor to what you 
> want.  (just watch your layer order  :-)

That sounds like a nifty solution, but it didn't work when I tried it on
the Mac. It just turns gray and is unresponsive to changes in the
backgroundColor or foregroundColor. If I set the border to transparent,
the whole image button turns transparent (still gray), but when the
border is None, the image button obscures any overlapping widgets, 
even the ones that are supposedly in front.

The Image widget worked a little better, in that I could change the
color, but it still obscures all overlapping widgets.

I'm using PythonCard .82 (latest CVS) and wxPython 2.5.3 on Mac OS 10.4.2
with Python 2.3.5. Since I'm at home today, I don't have access to my
work PC, but tomorrow I can try it on Windows XP. 

Alex Tweedly wrote on 08/01/2005 03:53:01 PM:

>> bra...@om... wrote: 
>> 
>> I just noticed that there is a component called ToggleButton in the 
>> Resource Editor's Components menu, and there is an example of 
>> ToggleButton in the Widgets sample. However, I don't see the 
>> difference between a toggle button and a normal button. It's also 
>> not documented anywhere on the PythonCard website. 

> There's not much difference to see in the resourceEditor - the 
> button itself looks the same. However, it has an additional 
> attribute "checked" (on same line as enabled and visible); also, it 
> cannot be "default". 

Aha. Thanks. I guess I just didn't notice that..

No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.338 / Virus Database: 267.9.6/59 - Release Date: 27/07/2005

Kevin Altis wrote:

> If you're using wxPython 2.6.x with the current release version of 
> PythonCard or the version in cvs, please report any issues here. In 
> particular, I would like to hear about differences from 2.5.x that 
> you've had to workaround or that are simply broken and we need to 
> address in the next release.

I moved up to wxPython 2.6 (and Python 2.4), using PythonCard from CVS 
(from yesterday).

I saw 2 (or 3) differences (small sample files below).

1. (as originally reported by Brad)
I have a checkbox which overlaps a (later in the rsrc file) staticText.
In wxPython 2.5.3, this "works", in 2.6 it doesn't.

I think 2.6 is correct - the staticText should be drawn after the 
checkbox's label, and so it should hide the checkbox's text, and so I 
believe 2.6 is correct.
So this is a compatibility warning, but not a bug in wxPython 2.6 (nor 
in PythonCard).

2. transparent PNG image.
I have an imageButton where the image is a file reference to a PNG file 
with transparent pixels. The imageButton has border set to 
"transparent". (Needs to be "transparent" to see the problem, works OK 
if the button is style "3d").

In wxPython 2.5 this works properly. In 2.6, the background of the 
button shows what was there before the window opened. i.e. it's as 
though it were transparent all the way through the background of the app 
window.

3. missing PNG image
if the image file is missing, both versions report "cannot load image 
file". In 2.5, it works OK - so the effect is simply that where the 
button is shows as background. In 2.6, it works as though the entire 
image were transparent - i.e. you can see  the desktop behind the app 
window. (so far, just the same as problem 2).

BUT - the transparent area is far larger than the imageButton's size. 
The imageButton has size 20,20 but the transparent area is something 
like 100,20. So this might be another bug, or it might not.

So I think 2 and 3 (if 3 is actually different, not just a manifestation 
of 2) are wxPython 2.6 bugs, not things that need to be, or even can be, 
changed in PythonCard.

Sample files:
wxchanges.py
---------------------------------------------
#!/usr/bin/python

"""
__version__ = "$Revision: 1.5 $"
__date__ = "$Date: 2004/04/30 16:26:12 $"
"""

from PythonCard import model

class MyBackground(model.Background):

    def on_initialize(self, event):
        # if you have any initialization
        # including sizer setup, do it here
        pass

    def on_mouseDown(self, event):
        ctlKey = event.ControlDown()
        print "mouseDown", ctlKey

    def on_Button_mouseDown(self, event):
        ctlKey = event.ControlDown()
        print "mouseDown", ctlKey

if __name__ == '__main__':
    app = model.Application(MyBackground)
    app.MainLoop()

-------------------------------------------
wxchanges.rsrc.py
------------------------------------------
{'application':{'type':'Application',
          'name':'Template',
    'backgrounds': [
    {'type':'Background',
          'name':'bgTemplate',
          'title':'Standard Template with File->Exit menu',
          'size':(400, 300),
          'style':['resizeable'],

        'menubar': {'type':'MenuBar',
         'menus': [
             {'type':'Menu',
             'name':'menuFile',
             'label':'&File',
             'items': [
                  {'type':'MenuItem',
                   'name':'menuFileExit',
                   'label':'E&xit',
                   'command':'exit',
                  },
              ]
             },
         ]
     },
         'components': [

{'type':'CheckBox',
    'name':'chkallowNameLabelVariation',
    'position':(149, 24),
    'size':(70, -1),
    'label':'Vary',
    },

{'type':'StaticText',
    'name':'Properties',
    'position':(214, 6),
    'text':'Properties',
    },

{'type':'StaticText',
    'name':'txtname',
    'position':(160, 24),
    'size':(84, -1),
    'alignment':'right',
    'text':'name',
    },

{'type':'ImageButton',
    'name':'ImageButton1',
    'position':(20, 20),
    'border':'transparent',
    'file':'image.png',
    },

] # end components
} # end background
] # end backgrounds
} }
--------------------------------------
image.png
This is the file resourceEditor/images/nudge_down.png, copied and 
renamed to image.png

but note that as it says in problem 3 above, if this file is missing you 
can see the problem.
-------------------------------------

-- 
Alex Tweedly       http://www.tweedly.net

-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.338 / Virus Database: 267.9.6/59 - Release Date: 27/07/2005

Hi there...

I found a solution, I inserted the follwing:

    def on_initialize(self,event):
        ....
        ....
        self.SetWindowStyle(wx.CAPTION | wx.CLOSE_BOX | wx.STAY_ON_TOP | 
wx.FRAME_TOOL_WINDOW | wx.CLOSE_BOX | wx.SYSTEM_MENU )
        self.Refresh()

/Stoons.

PS Pythoncard truly rules..!

----- Original Message ----- 
From: "Phil Edwards" <ph...@li...>
To: "Pythoncard-Users" <pyt...@li...>
Sent: Friday, July 29, 2005 10:42 AM
Subject: Re: [Pythoncard-users] Is "Toolbox" background possible to make...?

> On Wed, 2005-07-27 at 13:58 -0700, bri...@sy... wrote:
>> In the past I've hacked the styles for wx.Frame init in the file model.py
>> but that is kind of ugly
>> If you want to try, it has worked for many of the windows styles listed 
>> in
>> the wxWidgets help
>> for class wxFrame.
>>
>> I haven't done it for  recent wxWidgets/PythonCard versions.
>>
>> pyt...@li... wrote on 07/27/2005 01:29:18
>> PM:
>>
>> > Hi there.
>> >
>> > I was just wondering if there is any possibility to make a window
>> > with toolbox-look (you know: a a narrow titlebar with only a
>> close-button)...?
>> > If, so how...?
>> >
>
> I have just such a window in an appplication of mine. Put this code in
> your PythonCard application:
>
> -----begin code-----
> class MyMiniFrame(wx.MiniFrame):
>
>    def __init__(
>        self, parent, title, pos=wx.DefaultPosition, size=wx.DefaultSize,
>        style=wx.DEFAULT_FRAME_STYLE
>        ):
>
>        wx.MiniFrame.__init__(self, parent, -1, title, pos, size, style)
>        panel = wx.Panel(self, -1)
>        txt = wx.StaticText(self, -1, "Scanning, please wait...")
>        txt.SetPosition((20,10))
>
>        self.Bind(wx.EVT_CLOSE, self.OnCloseWindow)
>
>    def OnCloseWindow(self, event):
>        self.Destroy()
> ------end code------
>
> Then to make the window appear, the code I have is this:
>
> -----begin code-----
>    def on_scanBtn_mouseClick(self, event):
>        win = MyMiniFrame(self, "Wireless Network Scan",
>                          style=wx.DEFAULT_FRAME_STYLE | 
> wx.TINY_CAPTION_HORIZ)
>        win.SetSize((200, 60))
>        win.CenterOnParent(wx.BOTH)
>        win.Show(True)
>        win.Update()
>        win.Refresh()
>        wx.Yield()
>
>        cmd = '/sbin/iwlist %s scan' % self.iface
>        result = commands.getoutput(cmd)
>        win.Close()
> ------end code------
>
> Hope this helps.
>
>
>
>
>
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO 
> September
> 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Pythoncard-users mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/pythoncard-users
> 

I'm wondering about ways to allow users to customize the order of the 
columns
in a multicolumnlist.

I've seen wx demos in which ListCntrl columns were re-orderable by 
clicking
and dragging, but didn't see anything in the wx documentation on how to 
implement that.
(this may be a question for the wx list). 

Any thoughts would be appreciated. Thanks!

I just noticed that there is a component called ToggleButton in the 
Resource Editor's Components menu, and there is an example of ToggleButton 
in the Widgets sample. However, I don't see the difference between a 
toggle button and a normal button. It's also not documented anywhere on 
the PythonCard website.

I noticed it because I ran across a need for a button whose label might 
differ based on the value in a nearby field. For now, I'm just changing 
the label property when the user clicks it, but I'm wondering if there's a 
special PythonCard native manner of doing this.

Thanks!

"Kevin Altis" <al...@se...> wrote on 07/30/2005 07:38:07 PM:

> On the wxPython-dev list it was suggested that using
> 
> wx.SystemOptions.SetOptionInt("mac.textcontrol-use-mlte", 0)
> 
> might fix the problem if I read the description of current Mac wxPython 
> 2.6 behavior correctly. Also, it sounded like Robin might make this the 
> default in the next 2.6 build. I'll try this out after OSCON, but I'm 
> back on 2.5.x for this week.
> 

Thanks for checking into that...I did a search on the wxPython-dev
list archive, but had trouble finding the specific posting. I'm trying
to figure out the specific context in which that needs to be declared.
I tried it in my top-level script thinking it might apply globally,
but it didn't have any effect on the problem. I also tried it in
the on_initialize handler of an afflicted window, but it still didn't
help.

On the wxPython-dev list it was suggested that using

wx.SystemOptions.SetOptionInt("mac.textcontrol-use-mlte", 0)

might fix the problem if I read the description of current Mac wxPython 
2.6 behavior correctly. Also, it sounded like Robin might make this the 
default in the next 2.6 build. I'll try this out after OSCON, but I'm 
back on 2.5.x for this week.

ka
On Jul 30, 2005, at 5:05 PM, bra...@om... wrote:

>
> Kevin Altis wrote on 07/26/2005 01:36:01 PM:
>
>  > If you're using wxPython 2.6.x with the current release version of
>  > PythonCard or the version in cvs, please report any issues here. In
>  > particular, I would like to hear about differences from 2.5.x that
>  > you've had to workaround or that are simply broken and we need to
>  > address in the next release.
>
> The biggest problem I've noticed on the Mac (10.3/10.4) between 
> wxPython 2.5.3 and
>  2.6 is that sometimes TextField don't populate correctly on 2.6. They 
> appear
>  not to populate at all, but if you click in the field and drag left, 
> the
>  text will scroll into view. This problem doesn't happen on wxPython 
> 2.5.3.
>
> Note that these fields were created on Resource Editor running under 
> Windows.
> I'm not sure if that matters, but I notice there are some sizing 
> differences
> between the two platforms. It's almost as if the text is trying to 
> display
> on a field of a different size.
>
> This is the main reason I haven't upgraded any of our Mac users to
> Python 2.6 -- my PythonCard app doesn't have this problem under 
> wxPython2.5.3.

Kevin Altis wrote on 07/26/2005 01:36:01 PM:

> If you're using wxPython 2.6.x with the current release version of 
> PythonCard or the version in cvs, please report any issues here. In 
> particular, I would like to hear about differences from 2.5.x that 
> you've had to workaround or that are simply broken and we need to 
> address in the next release.

The biggest problem I've noticed on the Mac (10.3/10.4) between wxPython 
2.5.3 and 
2.6 is that sometimes TextField don't populate correctly on 2.6. They 
appear 
not to populate at all, but if you click in the field and drag left, the 
text will scroll into view. This problem doesn't happen on wxPython 2.5.3. 

Note that these fields were created on Resource Editor running under 
Windows.
I'm not sure if that matters, but I notice there are some sizing 
differences
between the two platforms. It's almost as if the text is trying to display
on a field of a different size.

This is the main reason I haven't upgraded any of our Mac users to
Python 2.6 -- my PythonCard app doesn't have this problem under 
wxPython2.5.3.

On Jul 30, 2005, at 1:38 AM, Mumtaz Ahmed wrote:

> on
> http://sourceforge.net/project/showfiles.php?group_id=19015
> there are two executable files for win32:
>
> PythonCard-0.8.1.FIXED.win32.exe    size: 1,536,194
> PythonCard-0.8.1.win32.exe          size: 1,756,103
>
> both are dated 19 october 2004.
>
> what was FIXED in the first one?
>
> [and now a somewhat foolish question] and which file
> should be used?
>
> M.
>

Use the FIXED version since the installer will work with both Python 
2.3 and Python 2.4, the larger file doesn't install the Startup menu 
items properly when used with Python 2.4. Other than that they should 
be identical.

ka

on
http://sourceforge.net/project/showfiles.php?group_id=19015
there are two executable files for win32:

PythonCard-0.8.1.FIXED.win32.exe    size: 1,536,194
PythonCard-0.8.1.win32.exe          size: 1,756,103 

both are dated 19 october 2004.

what was FIXED in the first one? 

[and now a somewhat foolish question] and which file
should be used?

M.

____________________________________________________
Start your day with Yahoo! - make it your home page 
http://www.yahoo.com/r/hs 

On Wed, 2005-07-27 at 13:58 -0700, bri...@sy... wrote:
> In the past I've hacked the styles for wx.Frame init in the file model.py
> but that is kind of ugly
> If you want to try, it has worked for many of the windows styles listed in
> the wxWidgets help
> for class wxFrame.
> 
> I haven't done it for  recent wxWidgets/PythonCard versions.
> 
> pyt...@li... wrote on 07/27/2005 01:29:18
> PM:
> 
> > Hi there.
> >
> > I was just wondering if there is any possibility to make a window
> > with toolbox-look (you know: a a narrow titlebar with only a
> close-button)...?
> > If, so how...?
> >

I have just such a window in an appplication of mine. Put this code in
your PythonCard application:

-----begin code-----
class MyMiniFrame(wx.MiniFrame):

    def __init__(
        self, parent, title, pos=wx.DefaultPosition, size=wx.DefaultSize,
        style=wx.DEFAULT_FRAME_STYLE 
        ):

        wx.MiniFrame.__init__(self, parent, -1, title, pos, size, style)
        panel = wx.Panel(self, -1)
        txt = wx.StaticText(self, -1, "Scanning, please wait...")
        txt.SetPosition((20,10))

        self.Bind(wx.EVT_CLOSE, self.OnCloseWindow)

    def OnCloseWindow(self, event):
        self.Destroy()
------end code------

Then to make the window appear, the code I have is this:

-----begin code-----
    def on_scanBtn_mouseClick(self, event):
        win = MyMiniFrame(self, "Wireless Network Scan",
                          style=wx.DEFAULT_FRAME_STYLE | wx.TINY_CAPTION_HORIZ)
        win.SetSize((200, 60))
        win.CenterOnParent(wx.BOTH)
        win.Show(True)
        win.Update()
        win.Refresh()
        wx.Yield()

        cmd = '/sbin/iwlist %s scan' % self.iface
        result = commands.getoutput(cmd)
        win.Close()
------end code------

Hope this helps.

2001	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug (116)	Sep (146)	Oct (78)	Nov (69)	Dec (70)
2002	Jan (188)	Feb (142)	Mar (143)	Apr (131)	May (97)	Jun (221)	Jul (127)	Aug (89)	Sep (83)	Oct (66)	Nov (47)	Dec (70)
2003	Jan (77)	Feb (91)	Mar (103)	Apr (98)	May (134)	Jun (47)	Jul (74)	Aug (71)	Sep (48)	Oct (23)	Nov (37)	Dec (13)
2004	Jan (24)	Feb (15)	Mar (52)	Apr (119)	May (49)	Jun (41)	Jul (34)	Aug (91)	Sep (169)	Oct (38)	Nov (32)	Dec (47)
2005	Jan (61)	Feb (47)	Mar (101)	Apr (130)	May (51)	Jun (65)	Jul (71)	Aug (96)	Sep (28)	Oct (20)	Nov (39)	Dec (62)
2006	Jan (13)	Feb (19)	Mar (18)	Apr (34)	May (39)	Jun (50)	Jul (63)	Aug (18)	Sep (37)	Oct (14)	Nov (56)	Dec (32)
2007	Jan (30)	Feb (13)	Mar (25)	Apr (3)	May (15)	Jun (42)	Jul (5)	Aug (17)	Sep (6)	Oct (25)	Nov (49)	Dec (10)
2008	Jan (12)	Feb	Mar (17)	Apr (18)	May (12)	Jun (2)	Jul (2)	Aug (6)	Sep (4)	Oct (15)	Nov (45)	Dec (9)
2009	Jan (1)	Feb (3)	Mar (18)	Apr (8)	May (3)	Jun	Jul (13)	Aug (2)	Sep (1)	Oct (9)	Nov (13)	Dec
2010	Jan (2)	Feb (3)	Mar (9)	Apr (10)	May	Jun (1)	Jul	Aug (3)	Sep	Oct	Nov (1)	Dec (4)
2011	Jan	Feb	Mar (10)	Apr (44)	May (9)	Jun (22)	Jul (2)	Aug	Sep	Oct (1)	Nov	Dec
2012	Jan	Feb (1)	Mar (2)	Apr (2)	May	Jun (5)	Jul	Aug	Sep (1)	Oct	Nov	Dec
2013	Jan	Feb	Mar (2)	Apr (1)	May (1)	Jun	Jul (3)	Aug (8)	Sep (3)	Oct	Nov	Dec
2014	Jan	Feb (4)	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2017	Jan	Feb	Mar	Apr	May (1)	Jun	Jul	Aug	Sep	Oct	Nov	Dec

pythoncard-users Mailing List for PythonCard (Page 49)

pythoncard-users — PythonCard Users and Developers