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: Steve F. <sf...@ih...> - 2006-07-06 04:29:06
|
Great, thanks for the tip. That's interesting. Before I discovered singleItemExpandingSizerLayout() (say that five times fast), I was using on_size() to adjust the size of StaticBox1 when the window size changed, but the redraws weren't coming through. Until, that is, I added event.skip(). So it seems like for proper handling of most general events (IOW, events not aimed at specific components), calling event.skip() at the end of the function is a good idea, no? Steve On Thu, 2006-07-06 at 00:59 +0100, Alex Tweedly wrote: > Steve Freitas wrote: > > >Hi, > > > >For debugging let's say I put a method "on_size(self, event)" in my > >class, and it prints some stuff. Well, I noticed when playing with > >model.Background.singleItemExpandingSizerLayout(), if I provide an > >on_size(), then the resizing doesn't happen. So I tried... > > > >class Test(model.Background): > > def on_initialize(self, event): > > self.singleItemExpandingSizerLayout() > > > > def on_size(self, event): > > print self.size, self.c.StaticBox1.size > > super(Test, self).on_size(self, event) # This didn't work > > model.Background.on_size(self, event) # Nor this > > > > > > >So when I want to respond to an event but then toss the event back up > >afterward for normal handling, how do I do that? > > > > > > > def on_size(self, event): > print self.size, self.c.StaticBox1.size > event.skip() > > Actually, event.Skip() also seems to work - not 100% sure which is "correct" :-) > > > > -- > Alex Tweedly http://www.tweedly.net > > > |
From: Alex T. <al...@tw...> - 2006-07-05 23:59:57
|
Steve Freitas wrote: >Hi, > >For debugging let's say I put a method "on_size(self, event)" in my >class, and it prints some stuff. Well, I noticed when playing with >model.Background.singleItemExpandingSizerLayout(), if I provide an >on_size(), then the resizing doesn't happen. So I tried... > >class Test(model.Background): > def on_initialize(self, event): > self.singleItemExpandingSizerLayout() > > def on_size(self, event): > print self.size, self.c.StaticBox1.size > super(Test, self).on_size(self, event) # This didn't work > model.Background.on_size(self, event) # Nor this > > >So when I want to respond to an event but then toss the event back up >afterward for normal handling, how do I do that? > > > def on_size(self, event): print self.size, self.c.StaticBox1.size event.skip() Actually, event.Skip() also seems to work - not 100% sure which is "correct" :-) -- Alex Tweedly http://www.tweedly.net -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.9.8/380 - Release Date: 30/06/2006 |
From: Steve F. <sf...@ih...> - 2006-07-05 23:36:25
|
Hi, For debugging let's say I put a method "on_size(self, event)" in my class, and it prints some stuff. Well, I noticed when playing with model.Background.singleItemExpandingSizerLayout(), if I provide an on_size(), then the resizing doesn't happen. So I tried... class Test(model.Background): def on_initialize(self, event): self.singleItemExpandingSizerLayout() def on_size(self, event): print self.size, self.c.StaticBox1.size super(Test, self).on_size(self, event) # This didn't work model.Background.on_size(self, event) # Nor this The exception for either approach is this: Traceback (most recent call last): File "/usr/lib/python2.3/site-packages/PythonCard/model.py", line 884, in _dispatch handler(background, aWxEvent) File "test.py", line 16, in on_size super(Test, self).on_size(self, event) AttributeError: 'super' object has no attribute 'on_size' And I guess that's because the superclass handles events by means other than prefab methods? So when I want to respond to an event but then toss the event back up afterward for normal handling, how do I do that? Thanks! Steve |
From: Steve F. <sf...@ih...> - 2006-07-04 22:04:30
|
On Tue, 2006-07-04 at 12:43 -0500, Brad Allen wrote: > I have encountered one problem with this approach, though. > If the user closes the window while the cursor is still in one > of the fields, that field never fires on_closeField. Using > on_loseFocus never occurred to me; I'll try it and see if > that eliminates the problem. Thanks for the tips. on_loseFocus does get called when the window closes, at least for me under Linux. Steve |
From: Kevin A. <al...@se...> - 2006-07-04 19:10:03
|
On Jul 4, 2006, at 10:43 AM, Brad Allen wrote: > > At 12:24 AM -0700 7/4/06, Steve Freitas wrote: >> Ah ha! That'd be on_loseFocus(). >> >> Heh, thanks for such a nice framework. > > There is also on_closeField; here is how I do it: > > def on_closeField (self, event): > component = event.target > > This handler usually goes into a custom event mixin class which > all my Background and PageBackground classes inherit from. > > I have encountered one problem with this approach, though. > If the user closes the window while the cursor is still in one > of the fields, that field never fires on_closeField. Using > on_loseFocus never occurred to me; I'll try it and see if > that eliminates the problem. > > For a workaround, I handle on_close in my event mixin class, > and check each field for the given window to see if it differs > from the associated 'model' object. Sadly, when an application is exiting is troublesome time for event dispatch due to race conditions and wanting to avoid crashes due to referencing C++ objects that have already been destroyed. In addition, the order of events is probably still slightly different on the three platforms, so extensive testing is needed if you want to work everywhere. There is a testevents sample application that you can muck around with to get a better feel for what events happens when. Due to how events are bound and unbound at application startup and exit, the message watcher doesn't work very well for these special cases so you're best off just printing to the console. ka |
From: Brad A. <bra...@ma...> - 2006-07-04 17:43:25
|
At 12:24 AM -0700 7/4/06, Steve Freitas wrote: >Ah ha! That'd be on_loseFocus(). > >Heh, thanks for such a nice framework. There is also on_closeField; here is how I do it: def on_closeField (self, event): component = event.target This handler usually goes into a custom event mixin class which all my Background and PageBackground classes inherit from. I have encountered one problem with this approach, though. If the user closes the window while the cursor is still in one of the fields, that field never fires on_closeField. Using on_loseFocus never occurred to me; I'll try it and see if that eliminates the problem. For a workaround, I handle on_close in my event mixin class, and check each field for the given window to see if it differs from the associated 'model' object. |
From: Steve F. <sf...@ih...> - 2006-07-04 07:24:06
|
Ah ha! That'd be on_loseFocus(). Heh, thanks for such a nice framework. Steve On Mon, 2006-07-03 at 23:57 -0700, Steve Freitas wrote: > Hi, > > I've got to put together a number of pages with a lot of text fields, > the contents of which need to be saved as soon as they're changed, and > I'd like to avoid writing a lot of boilerplate > on_textFieldName_loseFocus() events. > > So I'd like to modify the event dispatch so that whenever a text field > loses focus, PythonCard will call a single, particular function within > the page's object with that event, such as > handleAllTextFieldsLosingFocus(self, event). Then at that point I can > inspect the field using event.target and do my saving. > > Is there a better way of doing this then mucking around with the event > dispatch system? Otherwise I'd guess subclassing Scriptable is probably > the right direction? > > Any help would be appreciated. Thanks. > > Steve > > > 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: Steve F. <sf...@ih...> - 2006-07-04 06:57:17
|
Hi, I've got to put together a number of pages with a lot of text fields, the contents of which need to be saved as soon as they're changed, and I'd like to avoid writing a lot of boilerplate on_textFieldName_loseFocus() events. So I'd like to modify the event dispatch so that whenever a text field loses focus, PythonCard will call a single, particular function within the page's object with that event, such as handleAllTextFieldsLosingFocus(self, event). Then at that point I can inspect the field using event.target and do my saving. Is there a better way of doing this then mucking around with the event dispatch system? Otherwise I'd guess subclassing Scriptable is probably the right direction? Any help would be appreciated. Thanks. Steve |
From: <kc1...@ya...> - 2006-06-30 18:35:05
|
Alex Tweedly wrote: > I don't think so. As far as I can see, PythonCard simply calls the > wxPython function AppendItems, which in turn simply calls the wxWidgets > (i.e. c++) function of the same name - so unless I'm misreading it, > there's nothing obvious to be done. > > Obligatory annoying question : is a UI with 10000 items in a ComboBox > really usable ? > I am just being lazy about it. There are obviously better ways of designing the UI to rearrange things. But I didn't think 10000 items is such a big task for today's machines. > Only slightly less annoying question : could you use a List instead of a > ComboBox ? > (10000 elements in a list takes < 1 sec on my slow laptop) > Thanks, I will try that. That's the kind of performance I would have expected. > > kc1...@ya... wrote: > >> Hi list, >> >> I have a need to set up a selection list and I am >> using a simple statement like: >> >> self.components.cbxMyComboBox.items=items >> >> where items is a list of selection items. >> >> The problem is that when the size of items gets to be >> very large (like 10000), it takes *forever* to run. However, a >> non-pythoncard type assign takes no time at >> all (like abc_list = items). >> >> I am assuming that Pythoncard needs to actually *copy* >> the list whereas the simple assignment is only an >> address assignment (alas pointer). >> >> Is there anyway to improve the performance? >> >> -- John Henry |
From: Alex T. <al...@tw...> - 2006-06-30 18:22:39
|
kc1...@ya... wrote: >Hi list, > >I have a need to set up a selection list and I am >using a simple statement like: > >self.components.cbxMyComboBox.items=items > >where items is a list of selection items. > >The problem is that when the size of items gets to be >very large (like 10000), it takes *forever* to run. >However, a non-pythoncard type assign takes no time at >all (like abc_list = items). > >I am assuming that Pythoncard needs to actually *copy* >the list whereas the simple assignment is only an >address assignment (alas pointer). > >Is there anyway to improve the performance? > > I don't think so. As far as I can see, PythonCard simply calls the wxPython function AppendItems, which in turn simply calls the wxWidgets (i.e. c++) function of the same name - so unless I'm misreading it, there's nothing obvious to be done. Obligatory annoying question : is a UI with 10000 items in a ComboBox really usable ? Only slightly less annoying question : could you use a List instead of a ComboBox ? (10000 elements in a list takes < 1 sec on my slow laptop) -- Alex Tweedly http://www.tweedly.net -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.9.7/379 - Release Date: 29/06/2006 |
From: <kc1...@ya...> - 2006-06-30 15:29:39
|
Hi list, I have a need to set up a selection list and I am using a simple statement like: self.components.cbxMyComboBox.items=items where items is a list of selection items. The problem is that when the size of items gets to be very large (like 10000), it takes *forever* to run. However, a non-pythoncard type assign takes no time at all (like abc_list = items). I am assuming that Pythoncard needs to actually *copy* the list whereas the simple assignment is only an address assignment (alas pointer). Is there anyway to improve the performance? Regards, -- John Henry |
From: Phil E. <ph...@li...> - 2006-06-30 08:17:21
|
On Tuesday 27 Jun 2006 21:24, KC wrote: > Hi all, > > How do I activate the tools (such as the message > watcehr)? The on-line doc at > http://pythoncard.sourceforge.net/framework/runtime_tools.html > only says "command-line switch in parens" with no > example code on how to activate them. > > Could somebody please help? > Hi John: If you open up the resourceEditor and click File --> Run options, you'll see the available command-line switches. You can either select one or more of these from within the resource editor and they will be applied when you click File --> Run, or you can use them on a regular command line. So, in your specific example, you would use something like this on the command line: python helloworld.py -m Hope this helps. > Thanks, > > -- > John Henry > > 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 -- Regards Phil Edwards Brighton, UK |
From: Lance H. <lh...@ha...> - 2006-06-29 09:53:30
|
Hi Alex > If it were me, I'd try adding the line > print self.selected, self.components.serverList.items > immediately before line 111, and see what that tells me. Is the index > reasonable ? Are all the list items you expected in there ? yes I do have a "0" in front of the list but otherwise the list shows up fine. > If that doesn't help, feel free to send the code to me at > al...@tw... and I'll take a look. > Thanks I will. > btw - why "int()" in > self.components.serverList._setSelection(int(self.selected)) ? > Whatever is in self.selected ought to be an integer index already > before this call can work ? I remove the int section and it was redundant thanks for noticing. > > Come to think of it, why call _setSelection directly ? > Would it not be better to do self.components.serverList.selection = > self.selected It probably would be. 99% of the code in this app was reused code from the custdb example that Juergen Rauch wrote. I just manipulated the code to do what I wanted. So probably it is not right for what I want to do. I appreciate the help. Thanks Lance |
From: Alex T. <al...@tw...> - 2006-06-29 09:15:30
|
Lance Haig wrote: > Hi, > > I get the attached error when I click on the button to create a new > server. > > I am willing to share the code if it will help diagnose this problem > and show my bad code:-) > If it were me, I'd try adding the line print self.selected, self.components.serverList.items immediately before line 111, and see what that tells me. Is the index reasonable ? Are all the list items you expected in there ? If that doesn't help, feel free to send the code to me at al...@tw... and I'll take a look. btw - why "int()" in self.components.serverList._setSelection(int(self.selected)) ? Whatever is in self.selected ought to be an integer index already before this call can work ? Come to think of it, why call _setSelection directly ? Would it not be better to do self.components.serverList.selection = self.selected -- Alex Tweedly http://www.tweedly.net -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.9.6/378 - Release Date: 28/06/2006 |
From: Lance H. <lh...@ha...> - 2006-06-29 08:11:18
|
Hi, I get the attached error when I click on the button to create a new server. I am willing to share the code if it will help diagnose this problem and show my bad code:-) Lance |
From: Luis M. G. <lu...@gm...> - 2006-06-29 02:19:39
|
Thank you Alex! As you said, I got a lot of error messages until I included every single = component in "from Pythoncard.components import...". If anyone is in the same situation, please bear in mind that all the = components must be writen in lowercase in the import statement (it's = "staticbox", not "StaticBox"). For example: from PythonCard.components import statictext, imagebutton, = textfield, textarea, list, etc... Now it works! Thanks again! I'm so happy... Luis ----- Original Message -----=20 From: Alex Tweedly=20 To: Luis M. Gonzalez=20 Cc: pyt...@li...=20 Sent: Wednesday, June 28, 2006 9:42 PM Subject: Re: [Pythoncard-users] py2exe error Luis M. Gonzalez wrote:=20 Hi there, I want to build an ".exe" for a Pythoncard app, but I always get the = following log: Traceback (most recent call last): File "imc.pyw", line 43, in ? File "PythonCard\model.pyc", line 337, in __init__ File "PythonCard\resource.pyc", line 48, in getResource File "PythonCard\resource.pyc", line 86, in __init__ File "PythonCard\resource.pyc", line 91, in __init__ File "PythonCard\resource.pyc", line 91, in __init__ File "PythonCard\resource.pyc", line 96, in __init__ File "PythonCard\resource.pyc", line 139, in enforceSpec File "PythonCard\resource.pyc", line 30, in loadComponentModule ImportError: cannot import module 'image I tried using the option "--excludes=3DImage", but the problem = persists. What else can I do? The problem is that your app uses the PythonCard 'image' component - = but py2exe hasn't realized that the component was needed. py2exe tries = to figure out which files are imported in order to include them - but = won't succeed with PythonCard components because they are not imported = directly, but rather through the resource.py and the resource file. (that may not be a perfect explanation - see the section on "Resolving = import errors" in http://pythoncard.sourceforge.net/standalone.html ) easiest fix is to add =20 from PythonCard.components import image to your app's main .py file. That will almost certainly then result in = a similar error message, for each of the rest of the component types = used - so you could short-circuit that by making it be from PythonCard.components import image, button, textfield, ... listing all the component types used in your resource file. --=20 Alex Tweedly http://www.tweedly.net -------------------------------------------------------------------------= ----- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.9.5/377 - Release Date: = 27/06/2006 |
From: Alex T. <al...@tw...> - 2006-06-29 00:42:55
|
No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.9.5/377 - Release Date: 27/06/2006 |
From: Luis M. G. <lu...@gm...> - 2006-06-29 00:18:26
|
Hi there, I want to build an ".exe" for a Pythoncard app, but I always get the = following log: Traceback (most recent call last): File "imc.pyw", line 43, in ? File "PythonCard\model.pyc", line 337, in __init__ File "PythonCard\resource.pyc", line 48, in getResource File "PythonCard\resource.pyc", line 86, in __init__ File "PythonCard\resource.pyc", line 91, in __init__ File "PythonCard\resource.pyc", line 91, in __init__ File "PythonCard\resource.pyc", line 96, in __init__ File "PythonCard\resource.pyc", line 139, in enforceSpec File "PythonCard\resource.pyc", line 30, in loadComponentModule ImportError: cannot import module 'image I tried using the option "--excludes=3DImage", but the problem persists. What else can I do? Luis |
From: Alex T. <al...@tw...> - 2006-06-28 11:01:47
|
No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.9.5/377 - Release Date: 27/06/2006 |
From: Steve F. <sf...@ih...> - 2006-06-28 03:08:22
|
Phil's reply summed it up quite well. I've done some more experimentation and my results match his. Based on your note I tried layoutEditor, but for some reason the keys don't work in there, though the manual move control (the four buttoms arranged like a compass) seems to work just fine. I'll just press on with whatever tools work for whatever editor I'm using. :-) Thanks. Steve On Tue, 2006-06-27 at 11:04 +0100, Alex Tweedly wrote: > Steve Freitas wrote: > > >Hi all, > > > >I apologize if this is a known issue, but after some Googling I haven't > >been able to find any mention of it. For some reason I can't seem to > >drag buttons around in the resourceEditor. I'm in the tutorial stage so > >I'm only using TextFields besides, but they drag fine. So with buttons > >I'm forced to use the resize controls to put them where I want, ouch. > >Any suggestions would be appreciated. I'm using 0.8.2 with Python 2.3 on > >Debian Sid. > > > > > No, it's not a known issue - you should be able to drag buttons (and > indeed all components around). > > Unfortunately I don't have access to any Linux, so can't check them (it > does work OK on WinXP and OSX). > Can you tell me exactly what does happen when you try to drag a button ? > > For example, on Win XP, it is .... > position the mouse (ok, the cursor) inside the button > depress the left button > (the sizing handles disappear) > move the mouse > (the dashed-line rectangle outline appears and moves with the mouse) > release the left button > (rectangle disappears, button itself + sizing handles is drawn > in new location > > Do your see the sizing handles disappear ? > > Do you have the same problem with other component types ? > Other Linux users - do you see the same problem ? > > > btw Steve, although the tutorial still uses the (old) resourceEditor, > there is also a newer version called layoutEditor) in the same > directory. It has a number of useful new features (all fairly apparent > and obvious) , so you may want to switch to it at some point. I wouldn't > expect it to help with this problem though - the component moving code > is, as far as I remember, pretty much unchanged. > > Also, until we get to the bottom of it, it may be easier to use the > arrow keys to move the buttons - arrow keys should move the component by > 1 pixel, shift-arrow should move it by "grid-size" pixels > > -- > Alex Tweedly http://www.tweedly.net > > > |
From: KC <kim...@ya...> - 2006-06-27 20:24:21
|
Hi all, How do I activate the tools (such as the message watcehr)? The on-line doc at http://pythoncard.sourceforge.net/framework/runtime_tools.html only says "command-line switch in parens" with no example code on how to activate them. Could somebody please help? Thanks, -- John Henry |
From: Phil E. <ph...@li...> - 2006-06-27 11:29:42
|
On Tuesday 27 Jun 2006 11:04, Alex Tweedly wrote: > >Any suggestions would be appreciated. I'm using 0.8.2 with Python 2.3 on > >Debian Sid. > > No, it's not a known issue - you should be able to drag buttons (and > indeed all components around). > I seem to recall Kevin and I trying to figure this out a while ago. We didn't get very far, other than to work out that the drag events were being generated, but nothing else was happening with them within wx. Kevin exchanged some e-mails with Robin and it all went quiet after that. This is all from memory, so that may not be the whole story... :-) I tend to use the cursor keys to move components around in the resourceEditor, so not being able to drag buttons doesn't cause me personally any huge problems. To be honest, I've got so used to doing this now, I don't even think about it any more. > Unfortunately I don't have access to any Linux, so can't check them (it > does work OK on WinXP and OSX). Alex, if it would help, I *may* be able to get you set up with a Linux machine you can access remotely if you want to look into this, I guess it depends on how comfortable you are in a Linux/UNIX environment. > Can you tell me exactly what does happen when you try to drag a button ? > > For example, on Win XP, it is .... > position the mouse (ok, the cursor) inside the button > depress the left button > (the sizing handles disappear) > move the mouse > (the dashed-line rectangle outline appears and moves with the > mouse) release the left button > (rectangle disappears, button itself + sizing handles is drawn > in new location > On my laptop (Mandriva Linux LE2005, Python 2.4, wxPython 2.6.1.0, Pythoncard 0.8.2) I see the following: Position the mouse inside the button Depress left mouse button, sizing handles don't appear Release left mouse button, sizing handles appear Depress left mouse button, sizing handles disappear, dashed-line outline appears move mouse with left button held down, mouse pointer moves outside of the button, dashed-line outline is still visible, button doesn't move > Do your see the sizing handles disappear ? > > Do you have the same problem with other component types ? > Other Linux users - do you see the same problem ? > Components that can be dragged: bitmapcanvas calendar codeeditor combobox floatcanvas gauge htmlwindow image multicolumnlist notebook passwordfield radiogroup slider spinner staticbox staticline statictext textarea textfield tree Components that can't be dragged: button checkbox choice imagebutton list [* see note below] togglebutton With the list component, I find that I can't click to select it within the resource editor. The sizing handles do not appear, and the only way to select it (i.e. to make the sizing handles appear) is by using the resource editor property window. -- Regards Phil Edwards Brighton, UK |
From: Alex T. <al...@tw...> - 2006-06-27 10:04:52
|
Steve Freitas wrote: >Hi all, > >I apologize if this is a known issue, but after some Googling I haven't >been able to find any mention of it. For some reason I can't seem to >drag buttons around in the resourceEditor. I'm in the tutorial stage so >I'm only using TextFields besides, but they drag fine. So with buttons >I'm forced to use the resize controls to put them where I want, ouch. >Any suggestions would be appreciated. I'm using 0.8.2 with Python 2.3 on >Debian Sid. > > No, it's not a known issue - you should be able to drag buttons (and indeed all components around). Unfortunately I don't have access to any Linux, so can't check them (it does work OK on WinXP and OSX). Can you tell me exactly what does happen when you try to drag a button ? For example, on Win XP, it is .... position the mouse (ok, the cursor) inside the button depress the left button (the sizing handles disappear) move the mouse (the dashed-line rectangle outline appears and moves with the mouse) release the left button (rectangle disappears, button itself + sizing handles is drawn in new location Do your see the sizing handles disappear ? Do you have the same problem with other component types ? Other Linux users - do you see the same problem ? btw Steve, although the tutorial still uses the (old) resourceEditor, there is also a newer version called layoutEditor) in the same directory. It has a number of useful new features (all fairly apparent and obvious) , so you may want to switch to it at some point. I wouldn't expect it to help with this problem though - the component moving code is, as far as I remember, pretty much unchanged. Also, until we get to the bottom of it, it may be easier to use the arrow keys to move the buttons - arrow keys should move the component by 1 pixel, shift-arrow should move it by "grid-size" pixels -- Alex Tweedly http://www.tweedly.net -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.9.5/376 - Release Date: 26/06/2006 |
From: Steve F. <sf...@ih...> - 2006-06-27 01:18:42
|
Hi all, I apologize if this is a known issue, but after some Googling I haven't been able to find any mention of it. For some reason I can't seem to drag buttons around in the resourceEditor. I'm in the tutorial stage so I'm only using TextFields besides, but they drag fine. So with buttons I'm forced to use the resize controls to put them where I want, ouch. Any suggestions would be appreciated. I'm using 0.8.2 with Python 2.3 on Debian Sid. Thanks, Steve |
From: Alex T. <al...@tw...> - 2006-06-18 22:42:24
|
No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.9.0/368 - Release Date: 16/06/2006 |