You can subscribe to this list here.
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
|
From: <kc1...@ya...> - 2006-09-21 17:38:55
|
To ka (and others): Thanks for the answer. Yes, event.skip() was the answer I was looking for. What I needed to do has something to do with overriding the default behavior of how menuitem check marks are done in Pythoncard (or wxPython, I guess). What I do now is to have a handler for the gainFocus event of the window, and in there do what I need to do and when I am done, make a event.skip() call to pass the event back to the underlying system. Thanks everybody for the help. -- John Henry |
From: Alex T. <al...@tw...> - 2006-09-21 09:37:06
|
Winston Wolff wrote: >Hi Alex- > >A while back you were working on a version of PythonCard that >included Sizers. Has that work been incorporated back into the main >PythonCard CVS repository? Would you recommend using your "snap 1.1" >version from June, or the CVS version? > > > It hasn't been incorporated into CVS. The snapshot includes support only for BoxSizers, not for GridBagSizers, and until that's done it won't be ready for CVS. I started adding Gridbag support, but didn't like the way it turned out, so have taken it out ready to try again - but as yet, I haven't found time to do that. I'm afraid it's going to be a while before it's done. For now, it has to be the "snap 1.1" to get sizer support. -- Alex Tweedly al...@tw... http://www.tweedly.net -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.405 / Virus Database: 268.12.6/453 - Release Date: 20/09/2006 |
From: Kevin A. <al...@se...> - 2006-09-20 23:52:58
|
On Sep 20, 2006, at 4:09 PM, kc1...@ya... wrote: > If that's the case, may be I can accomplish what I > need to do by getting the gainFocus event of the main > window. > > I did try that before but the problem is that if I > capture the event by doing an on_mybgWindow_gainFocus, > a lot of things no long works (like list objects don't > scroll open anymore). I am suspecting that when I > capture the gainFocus event and do some processing, I > need to send the same event back to the system > somehow. In other words, I need to "sandwich" my code > into the event queue - rather then "robbing" the > event. (That's what needs to be done in other GUI > packages I used to use). > > How do I do that in PythonCard? > > Thanks, In general, when you want to do something not obviously supported in PythonCard you probably have to fall back on wxPython events. At that point it is time to look at the wxPython demo and wxWindows reference help and possibly post to the wxPython-users mailing list. It is also helpful to provide a description of what you're trying to accomplish, so nobody makes assumptions about what you need. I'm still not sure based on what you've posted what exactly you want to do. Are you needing to update a menu or menu item when the user clicks on a menu? Whenever you intercept an event like gainFocus, you are probably going to need to call event.skip() so that the underlying event system gets a chance to process the event as well. Also while your event handler is processing no other processing is going on, so unless you make explicit calls to force refreshes of controls don't expect to see any updates if you make changes. Finally, due to the way the underlying systems work, beware of menu bar trickery if you want it to work cross-platform. ka |
From: <kc1...@ya...> - 2006-09-20 23:09:15
|
If that's the case, may be I can accomplish what I need to do by getting the gainFocus event of the main window. I did try that before but the problem is that if I capture the event by doing an on_mybgWindow_gainFocus, a lot of things no long works (like list objects don't scroll open anymore). I am suspecting that when I capture the gainFocus event and do some processing, I need to send the same event back to the system somehow. In other words, I need to "sandwich" my code into the event queue - rather then "robbing" the event. (That's what needs to be done in other GUI packages I used to use). How do I do that in PythonCard? Thanks, Alex Tweedly wrote: > kc1...@ya... wrote: > >> Thanks for the reply. >> >> No, I know how to get it when an menuItem is clicked. >> >> I need it when the menu itself is clicked. >> >> >> >> > I don't think it is possible - certainly nothing shows up in the MessageWatcher. > > It may be possible to use some wxPython facility directly - but I didn't see anything helpful in a quick scan through the wxPython docs. > -- John Henry |
From: Ed L. <ed...@le...> - 2006-09-20 22:51:50
|
On Sep 20, 2006, at 6:06 PM, Alex Tweedly wrote: >> No, I know how to get it when an menuItem is clicked. >> >> I need it when the menu itself is clicked. >> >> > I don't think it is possible - certainly nothing shows up in the > MessageWatcher. > > It may be possible to use some wxPython facility directly - but I > didn't > see anything helpful in a quick scan through the wxPython docs. Check out wx.EVT_MENU_OPEN and wx.EVT_MENU_CLOSE - they should do what you need, although in my experience, they are flaky in Windows. -- Ed Leafe -- http://leafe.com -- http://dabodev.com |
From: Winston W. <win...@st...> - 2006-09-20 22:07:59
|
Hi Alex- A while back you were working on a version of PythonCard that =20 included Sizers. Has that work been incorporated back into the main =20 PythonCard CVS repository? Would you recommend using your "snap 1.1" =20= version from June, or the CVS version? -Winston On Jun 4, 2006, at 12:43 PM, Winston Wolff wrote: > Alex- > > Here are my comments on the layout editor. Also attached are some =20 > screenshots so you know what it looks like on the Mac. > <TestingTheSizer.png> > <SizerEditorAndProperties.png> > > PythonCard 1.1 > -------------- > > Comments > -------- > =95 It works on the MAC. It's great. > =95 Dragging of components in SizerEditor works very intuitively. > > > Suggestions > ----------- > > =95 Edit Properties of the sizer is very common. Add a button for it =20= > in the Sizer > Editor. > > =95 Alternatively, use the existing Property Editor window instead of =20= > a new Sizer > Editor window. That will minimize window clutter. > > =95 Perhaps you can also put the SizerEditor into the list of =20 > components in the > PropertyEditor, thereby getting all the functionality into one =20 > window. > > =95 When you select a component in your window, it should also be =20 > selected in the tree view. > > > > ______________________________________________________ > winston wolff - (646) 827-2242 - http://www.stratolab.com > learning by creating - video game courses for kids in new york > > ______________________________________________________ winston wolff - (646) 827-2242 - http://www.stratolab.com learning by creating - video game courses for kids in new york |
From: Alex T. <al...@tw...> - 2006-09-20 22:06:37
|
kc1...@ya... wrote: >Thanks for the reply. > >No, I know how to get it when an menuItem is clicked. > >I need it when the menu itself is clicked. > > > > I don't think it is possible - certainly nothing shows up in the MessageWatcher. It may be possible to use some wxPython facility directly - but I didn't see anything helpful in a quick scan through the wxPython docs. -- Alex Tweedly al...@tw... http://www.tweedly.net -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.405 / Virus Database: 268.12.5/451 - Release Date: 19/09/2006 |
From: <kc1...@ya...> - 2006-09-20 21:36:03
|
Thanks for the reply. No, I know how to get it when an menuItem is clicked. I need it when the menu itself is clicked. kc106_2005-pythoncard@[...].com wrote: > Hi list, > > I am not receiving any event when clicking on the menu > bar. > > Is there a way to do that? > > Thanks, > > -- > > John Hen Is this what you mean? -Cullen Newsom def on_doHelpAbout_command(self, event): self.addConsoleText("Add an About Box Someday.") {'type':'Menu', 'name':'menuHelp', 'label':'&Help', 'items': [ {'type':'MenuItem', 'name':'menuHelpAbout', 'label':'&About ...', 'command':'doHelpAbout', }, -- John Henry |
From: Cullen N. <cn...@sa...> - 2006-09-20 20:11:11
|
kc1...@ya... wrote: > Hi list, > > I am not receiving any event when clicking on the menu > bar. > > Is there a way to do that? > > Thanks, > > -- > > John Hen Is this what you mean? -Cullen Newsom def on_doHelpAbout_command(self, event): self.addConsoleText("Add an About Box Someday.") {'type':'Menu', 'name':'menuHelp', 'label':'&Help', 'items': [ {'type':'MenuItem', 'name':'menuHelpAbout', 'label':'&About ...', 'command':'doHelpAbout', }, |
From: <kc1...@ya...> - 2006-09-20 17:17:04
|
Hi list, I am not receiving any event when clicking on the menu bar. Is there a way to do that? Thanks, -- John Henry |
From: Ade <sk...@bl...> - 2006-09-19 19:51:56
|
Thanks for the info, Jussi. From your text i went through the wx documentation for TreeControl (i hadn't even thought of thw wx stuff) I found that the thing I was looking in my blinkered way after some trial and error was the tree.SetPyDataItem and tree.GetPyDataItem. This means that each node in the tree can be associated with an element in, say, a list which is the real data I want to get returned. I like your way by kind of recursing back to the root getting all the text of all the branches between the node selected and the root. Thank you very much :) Adrian From: Jussi Salmela <jussi.salmela@pp...> Re: Tree control 2006-09-17 06:12 This is for Ade to answer the question on Sep 11, 2006 No-one has answered your question. I don't know if it is because they thought you should be able to figure out yourself. After investigating your problem, I at least think so because it took me under a hour from the problem to the solution and I've never used the treecontrol nor looked at its demos nor the souce code nor the documentation. Here's what I did and what I think you should have done also: 1. I looked at the Pythoncard treecontrol demo and its source code. The events handled by PythonCard are listed at the beginning of the minimaltree code 2. I looked at the wxPython demo finding the treecontrol demo, running it and browsing its source code. I found out that the event generated by clicking the item text is OnSelChanged. 3. But your original headache was how to find the path to the root. Well I had the third and last help item left: wxWidgets documentation. There I browsed the wxTreeCtrl documentation looking for something with Parent in it. Found GetParent with a note to use GetItemParent instead. 4. Copied the minimaltree example to my own directory and started modifying and debuggin it to get what I/you wanted. Copied the on_tree_itemExpanding method and modified it to become (after 3-4 iterations): code <snip> I think this is near enough the thing you wanted, isn't it? About SourceForge.net About OSTG Privacy Statement Terms of Use Advertise Get Support RSS Powered by the SourceForge® collaborative development environment from VA Software ©Copyright 2006 - OSTG Open Source Technology Group, All Rights Reserved -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ |
From: Kevin A. <al...@se...> - 2006-09-17 19:30:13
|
On Sep 17, 2006, at 2:25 AM, Jussi Salmela wrote: > And the plot thickens... > > I've been playing a little with the multipropertyEditor changing the > place in question to look like this: > <snip> I checked in a new version of propertyEditor.py for the resourceEditor at: http://pythoncard.cvs.sourceforge.net/pythoncard/PythonCard/tools/ resourceEditor/modules/propertyEditor.py?view=log You can see the diffs with: http://pythoncard.cvs.sourceforge.net/pythoncard/PythonCard/tools/ resourceEditor/modules/propertyEditor.py? view=diff&r1=text&tr1=1.57&r2=text&tr2=1.56&diff_format=h This change may not totally solve the problem and I moved the discussion to pythoncard-devel for a more elaborate fix. In addition, Alex will need to roll these same kinds of changes into his multipropertyEditor. The basic idea is that attributes which are supposed to be strings such as command shouldn't get an eval() anymore, while attributes that are numbers, lists, tuples, etc. should be handled by eval. All attributes that are edited in a text field must be converted to strings before they can be displayed and edited by the user, so eval or an explicit conversion based on expected type must be done when the user is done editing. I did very little testing of this "fix" so feedback from anyone that wants to try it would be appreciated. ka |
From: Jussi S. <jus...@pp...> - 2006-09-17 13:12:35
|
This is for Ade to answer the question on Sep 11, 2006 No-one has answered your question. I don't know if it is because they thought you should be able to figure out yourself. After investigating your problem, I at least think so because it took me under a hour from the problem to the solution and I've never used the treecontrol nor looked at its demos nor the souce code nor the documentation. Here's what I did and what I think you should have done also: 1. I looked at the Pythoncard treecontrol demo and its source code. The events handled by PythonCard are listed at the beginning of the minimaltree code 2. I looked at the wxPython demo finding the treecontrol demo, running it and browsing its source code. I found out that the event generated by clicking the item text is OnSelChanged. 3. But your original headache was how to find the path to the root. Well I had the third and last help item left: wxWidgets documentation. There I browsed the wxTreeCtrl documentation looking for something with Parent in it. Found GetParent with a note to use GetItemParent instead. 4. Copied the minimaltree example to my own directory and started modifying and debuggin it to get what I/you wanted. Copied the on_tree_itemExpanding method and modified it to become (after 3-4 iterations): def on_tree_selectionChanged(self, event): tree = self.components.tree item=event.item #obj = int(tree.getItemText(item)) #print 'selChanged', obj if item != self.root: listToRoot = [] while item: listToRoot.append(tree.getItemText(item)) item = tree.GetItemParent(item) #print item listToRoot.reverse() print '_'.join(listToRoot) event.skip() I think this is near enough the thing you wanted, isn't it? |
From: Jussi S. <jus...@pp...> - 2006-09-17 09:25:46
|
And the plot thickens... I've been playing a little with the multipropertyEditor changing the place in question to look like this: print '===========================' if propName in self.checkItems: print 'propName:', propName, ' in checkItems' value = self.components["chk"+propName].checked elif propName in self.popItems: print 'propName:', propName, ' in popItems' value = self.components["pop"+propName].stringSelection elif propName in ('items', 'userdata') or (wClass == 'TextArea' and propName == 'text'): print 'propName:', propName, ' in items, userdata or ...' value = self.components["fld"+propName].text else: print 'propName:', propName, ' in else:' value = self.components["fld"+propName].text print 'value, type:', value, type(value) if propName == "textArea": propName = 'text' if propName not in ['name', 'label', 'stringSelection', 'text', 'toolTip', 'userdata']: try: value = eval(value) print '===> evaluated value, type:', value, type(value) except: print "===> Unexpected error:", sys.exc_info()[0] pass I then inserted a few component types and tried changing their properties just to get a feel of what's going on. 1. A checkbox, for example. Trying to change its Checked property on and off. Here's the result: =========================== propName: checked in checkItems value, type: True <type 'bool'> ===> Unexpected error: exceptions.TypeError =========================== propName: checked in checkItems value, type: False <type 'bool'> ===> Unexpected error: exceptions.TypeError This is because eval expects a string and it gets a boolean. The error was shadowed earlier by pass that 'handles' the exception. I've been wondering in general about the true reason for this value=eval(value) thing for a couple hours now and I think it could be done (a) for validity checking, (b) for getting a useful value evaluated or (c) for both. But in the particular case of checkItems, the layouteditor itself has chosen either False or True as the value so where is the additional value that it gets by checking&evaluating this value? What I mean is that Checked, Visible and Enabled properties, which all are booleans, should be listed in the not-in-check also. 2. A button, for example. If I enter (in the command field) the word open (as I so innocently did before), click update, change open to value, click update, change value to startTransfer and click update, I get: =========================== propName: command in else: value, type: open <type 'str'> ===> evaluated value, type: <type 'file'> <type 'type'> =========================== propName: command in else: value, type: value <type 'str'> ===> evaluated value, type: value <type 'str'> =========================== propName: command in else: value, type: startTransfer <type 'str'> ===> Unexpected error: exceptions.NameError I understand the reason for the last exception, but I think it's logically wrong in this situation. The validity check for the string entered in the command field, say xyz for example, to my mind is that the construction on_xyz_command has to be a legal form of a Python method name. So what I'm saying is that I think the command string should not be checked here at all but that it should undergo the same check done for the name property a few lines later. The incidence that started this thread (the first case above) is another kind of reason for leaving the command checking out of this context. What I don' understand at all is the result of the middle one of my experiments. I think I should have gotten an exception but instead value evaluates to value?!? All in all: I can't see the value of this feature in layouteditor. The evaluation is done in the editor's environment and I fail to see the usefulness of having the possibility of using the values of the editor entities in painting my application window! Well, this was my 2 cents' worth. I'm no Python wizard and this was the first time ever, that I've looked the resourceEditor under the cover. Thus, what I'd like to hear would be KEA's (who's signatures throughout the code make me believe he's the one who knows) explanation for this eval. Maybe after that I would think differently about the matter. Cheers, Jussi Salmela http://personal.inet.fi/cool/operator Alex Tweedly kirjoitti: > Jussi Salmela wrote: > >> Hello all and particularly Alex Tweedly, I guess! >> >> I'm using Python 2.4.3, wxPython 2.3.0, PythonCard 0.8.2 and its >> Resource Editor on Win XP SP2. >> >> 1. I have an ImageButton and a bunch of other components on my page. >> 2. I enter >> open >> into the command field of the ImageButton component in the Property >> Editor. >> 3. I click some other component(s) active and then click ImageButton >> active again. >> 4. The command field now contains >> <type 'file'> >> instead of the open I entered earlier. >> 5. If I now run my program I get an error, so not only the display is >> erroneous but also the resource file. >> 6. If I retype open in the command field, save and run, everything >> works as expected. >> >> > Hmmmm - very interesting. > > 1. It's not unique to ImageButton - happens with any component. > 2. It's (probably) not unique to the 'command' attribute - should > happen to some others, but I haven't tried too hard to see which ones > it happens with. > > It's caused by the following snippet of code in > modules/propertyEditor.py (and /multipropertyEditor,.py): > >> if propName not in ['label', 'stringSelection', 'text', >> 'toolTip', 'userdata']: >> try: >> value = eval(value) >> except: >> pass > > I'm not 100% sure why this was wanted. It does let you do interesting > things - e.g. you can enter a string such as > 3+8 > and it will be evaluated to 11 for you. You can enter a string like > [20+3*15, 17] > and it will be evaluated (to [65,17]) for, say, the position value. > And various other more strange possibilities > (e.g. enter self.position and you get the current co-ords of > the property editor window !!) > > But I'm not clear on what the *useful* purpose of this eval is. > > In any case, the two oddities I know about are 'open' and 'file' > which both eval to <type 'file'> (though there may be others). > > Suggestions (please comment): > > 1. short term - just avoid either open or file as command names :-) > > 2. figure out an exhaustive list of strings which eval to something > they "shouldn't", and explicitly check for them (??) > > 3. decide that you never want to eval the user-entered value to > produce a Python type, so add a test something like > if not isinstance(eval(value), types.TypeType) : > before resetting the variable 'value', thus > if propName not in ['label', 'stringSelection', 'text', 'toolTip', > 'userdata']: > try: > if not isinstance(eval(value), types.TypeType) : value > = eval(value) > except: > pass > > 4. decide whether there is real purpose in doing an 'eval' here at > all, and if there is, limiting the use to those cases, somehow. > > > |
From: Alex T. <al...@tw...> - 2006-09-15 12:13:08
|
Jussi Salmela wrote: >Hello all and particularly Alex Tweedly, I guess! > >I'm using Python 2.4.3, wxPython 2.3.0, PythonCard 0.8.2 and its >Resource Editor on Win XP SP2. > >1. I have an ImageButton and a bunch of other components on my page. >2. I enter > open >into the command field of the ImageButton component in the Property Editor. >3. I click some other component(s) active and then click ImageButton >active again. >4. The command field now contains > <type 'file'> >instead of the open I entered earlier. >5. If I now run my program I get an error, so not only the display is >erroneous but also the resource file. >6. If I retype open in the command field, save and run, everything works >as expected. > > Hmmmm - very interesting. 1. It's not unique to ImageButton - happens with any component. 2. It's (probably) not unique to the 'command' attribute - should happen to some others, but I haven't tried too hard to see which ones it happens with. It's caused by the following snippet of code in modules/propertyEditor.py (and /multipropertyEditor,.py): > if propName not in ['label', 'stringSelection', 'text', > 'toolTip', 'userdata']: > try: > value = eval(value) > except: > pass I'm not 100% sure why this was wanted. It does let you do interesting things - e.g. you can enter a string such as 3+8 and it will be evaluated to 11 for you. You can enter a string like [20+3*15, 17] and it will be evaluated (to [65,17]) for, say, the position value. And various other more strange possibilities (e.g. enter self.position and you get the current co-ords of the property editor window !!) But I'm not clear on what the *useful* purpose of this eval is. In any case, the two oddities I know about are 'open' and 'file' which both eval to <type 'file'> (though there may be others). Suggestions (please comment): 1. short term - just avoid either open or file as command names :-) 2. figure out an exhaustive list of strings which eval to something they "shouldn't", and explicitly check for them (??) 3. decide that you never want to eval the user-entered value to produce a Python type, so add a test something like if not isinstance(eval(value), types.TypeType) : before resetting the variable 'value', thus if propName not in ['label', 'stringSelection', 'text', 'toolTip', 'userdata']: try: if not isinstance(eval(value), types.TypeType) : value = eval(value) except: pass 4. decide whether there is real purpose in doing an 'eval' here at all, and if there is, limiting the use to those cases, somehow. -- Alex Tweedly al...@tw... http://www.tweedly.net -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.405 / Virus Database: 268.12.4/448 - Release Date: 14/09/2006 |
From: Alex T. <al...@tw...> - 2006-09-15 09:15:51
|
Jussi Salmela wrote: >Hello all and particularly Alex Tweedly, I guess! > >I'm using Python 2.4.3, wxPython 2.3.0, PythonCard 0.8.2 and its >Resource Editor on Win XP SP2. > >1. I have an ImageButton and a bunch of other components on my page. >2. I enter > open >into the command field of the ImageButton component in the Property Editor. >3. I click some other component(s) active and then click ImageButton >active again. >4. The command field now contains > <type 'file'> >instead of the open I entered earlier. >5. If I now run my program I get an error, so not only the display is >erroneous but also the resource file. >6. If I retype open in the command field, save and run, everything works >as expected. > > > That is pretty weird ! Good news is I can reproduce it easily, so with luck it should be easy to track it down - with (lots of) luck I'll find something today - otherwise I'm travelling without net access or computer for the weekend, so it'll be some time mid-week before I get another chance to try .... Thanks for such a clear report of the problem. -- Alex Tweedly al...@tw... http://www.tweedly.net -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.405 / Virus Database: 268.12.4/448 - Release Date: 14/09/2006 |
From: Jussi S. <jus...@pp...> - 2006-09-14 18:30:53
|
Hello all and particularly Alex Tweedly, I guess! I'm using Python 2.4.3, wxPython 2.3.0, PythonCard 0.8.2 and its Resource Editor on Win XP SP2. 1. I have an ImageButton and a bunch of other components on my page. 2. I enter open into the command field of the ImageButton component in the Property Editor. 3. I click some other component(s) active and then click ImageButton active again. 4. The command field now contains <type 'file'> instead of the open I entered earlier. 5. If I now run my program I get an error, so not only the display is erroneous but also the resource file. 6. If I retype open in the command field, save and run, everything works as expected. Cheers, Jussi Salmela http://personal.inet.fi/cool/operator |
From: Ade <sk...@bl...> - 2006-09-11 20:13:10
|
Hello, I an having a real problem with a tree control. I can generate tree for a set of infomation like: = ROOT | ----a ----b | | | ----click | ----drop | ----d | ----click = and the set is a break down of a lines of code like this : Root_b_drop or Root_b_click but I can not for the life of me see how to recreate the line of code or hold a pointer so that clicking the 'click' or 'drop' item in the tree gives me the full line back. If I click on 'click' then the only text returned is 'click' which is not unique for looking up in a list. Does the item you click on have to be unique so you can look up the answer in a list? A pointer is returned with event.GetItem() but i have not been able to use this as a unique reference to anything I get errors, which is odd= since I can use the pointer to store a list or dictionary as in new1 =3D tree.AppendItem(new1, "tabControlMain") s.dict[new1] =3D "tabControlMain" but on the 'activate Item' I get the 'expected type' errors I have searched the net and it seems only concerned with getting data into a tree and not out again. Please show me how I should be referencing the return values on say the 'item_Activated' function. Thankyou Adrian Smith -- = Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ |
From: Steve F. <sf...@ih...> - 2006-09-11 11:22:02
|
> Did you take a look at the Linux installation instructions; > > http://pythoncard.sourceforge.net/linux_installation.html > > If you're on a distribution that supports RPM package installation like > Red Hat or one that supports deb packages like Ubuntu you don't need to > perform an installation from source. We ought to change the Debian-oriented installation instructions on that web page because the Debian package has been orphaned (or is in process of becoming so) and is out of date. I exchanged emails with the former (still listed?) maintainer, and he said he didn't have time to do it any longer. Of course, a body who wants to maintain the Debian package is preferable to amending the Debian instrucs to read "sudo python setup.py install", but if wishes were horses blah blah. Steve |
From: Andy T. <an...@ha...> - 2006-09-11 11:01:28
|
Carl Wenrich wrote: > I've just unzipped PythonCard on a linux box. I can't find a configure > script, or any other instructions about how to install it, other than > simply placing the directory under site-packages, but that won't make it > visible. > > Please advise, > > Carl > > Did you take a look at the Linux installation instructions; http://pythoncard.sourceforge.net/linux_installation.html If you're on a distribution that supports RPM package installation like Red Hat or one that supports deb packages like Ubuntu you don't need to perform an installation from source. I do note that we don't have any instructions on installing from source though, I'll see what I can do to fix that. Regards, Andy -- -------------------------------------------------------------------------------- From the desk of Andrew J Todd esq - http://www.halfcooked.com/ |
From: Carl W. <car...@ya...> - 2006-09-09 23:04:59
|
The grid lines don't appear in the resourceEditor (after clicking Options > Show Grid Lines) under linux (which works fine under windows). is this a bug or am i missing something? |
From: Steve F. <sf...@ih...> - 2006-09-09 21:40:44
|
cd into the PythonCard directory. Then: python setup.py build sudo python setup.py install IIRC, that is. :-) On Sat, 2006-09-09 at 13:52 -0700, Carl Wenrich wrote: > I've just unzipped PythonCard on a linux box. I can't find a configure > script, or any other instructions about how to install it, other than > simply placing the directory under site-packages, but that won't make > it visible. > > Please advise, > > Carl > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ Pythoncard-users mailing list Pyt...@li... https://lists.sourceforge.net/lists/listinfo/pythoncard-users |
From: Carl W. <car...@ya...> - 2006-09-09 20:52:51
|
I've just unzipped PythonCard on a linux box. I can't find a configure script, or any other instructions about how to install it, other than simply placing the directory under site-packages, but that won't make it visible. Please advise, Carl |
From: Alex T. <al...@tw...> - 2006-09-04 14:01:34
|
hwphillips wrote: >I have an interesting window problem. My pcard rsrc sets the window size >at 700x500. When the program runs it it maximized to full screen >(1152x864). So it seems to ignore the program setting. This seems to be >related to other programs, because it has worked before, but does not >work after running some other programs. Why doesn't the pcard routine >control the window size like it's supposed too? > > Could you send the rsrc file (direct to me at al...@tw..., or to the list) ? Which version PythonCard (and for the heck of it, Python, wxPython, etc) ? OS ? If you reboot and run this app before other apps (that might change some system setting), does it work ? Thanks, -- Alex Tweedly al...@tw... http://www.tweedly.net -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.405 / Virus Database: 268.11.7/436 - Release Date: 01/09/2006 |
From: hwphillips <bu...@ya...> - 2006-09-04 12:37:41
|
hwphillips wrote: > I have an interesting window problem. My pcard rsrc sets the window size > at 700x500. When the program runs it it maximized to full screen > (1152x864). So it seems to ignore the program setting. This seems to be > related to other programs, because it has worked before, but does not > work after running some other programs. Why doesn't the pcard routine > control the window size like it's supposed too? > > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 I found the culprit program. It is RapidSVN. If I leave it maximized and exit, the pcard program mentioned above will be maximized. Very wierd. I noticed that RApidSVN uses wxWidgets. Maybe some connection here. |