Re: [Pythoncard-users] Can't drag buttons in resourceEditor

[Steve F. <sf...@ih...>]

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
> 
> 
>