[Pythoncard-cvs] PythonCard/tools/resourceEditor readme.txt,1.11,1.12

[Alex T. <ale...@us...>]

Update of /cvsroot/pythoncard/PythonCard/tools/resourceEditor
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv19488

Modified Files:
	readme.txt 
Log Message:
Minor changes to bring it up to date (largely to get the date to look recent, 
and hence avoid giving the impression that nothing is happening).


Index: readme.txt
===================================================================
RCS file: /cvsroot/pythoncard/PythonCard/tools/resourceEditor/readme.txt,v
retrieving revision 1.11
retrieving revision 1.12
diff -C2 -d -r1.11 -r1.12
*** readme.txt	13 Apr 2002 16:57:44 -0000	1.11
--- readme.txt	9 Aug 2005 13:52:20 -0000	1.12
***************
*** 1,3 ****
! Last updated: 2002-04-13
  
  This represents the beginnings of a GUI resource (layout) editor for PythonCard.
--- 1,3 ----
! Last updated: 2005-08-09
  
  This represents the beginnings of a GUI resource (layout) editor for PythonCard.
***************
*** 6,10 ****
  
  Known Bugs and Issues:
! There are no constraints applied when the shift key is held down, but there is there a grid for the widgets to "snap to".
  
  You can only select one widget at a time.
--- 6,10 ----
  
  Known Bugs and Issues:
! There are no constraints applied when the shift key is held down, but there is a grid for the widgets to "snap to".
  
  You can only select one widget at a time.
***************
*** 14,20 ****
  Some of the components don't move or resize correctly all the time, you should report problems to the mailing list. The Choice component seems prone to this movement problem. If a component is difficult to select or move, you can always select it via the Property Editor and then change its position attribute via the Property Editor rather than trying to drag the control itself; the sizing handles should also work.
  
- There is a bug that causes the top three sizing handles to appear incorrectly, usually when the widget y position is at -1. I am trying to determine if this is actually a problem with wxPython or some rare interaction in the resourceEditor code. [I think this is fixed as of release 0.6.2 -ka]
- 
  When editing a dialog or other window that doesn't have a menubar, you'll probably need to increase the vertical size of the window by 20 or 30 pixels to compensate for the resourceEditor menubar. Once your layout looks the way you want it you can subtract the pixel padding you added earlier. On Microsoft Windows, the menubar may wrap if the width of the window is not wide enough, in which case you'll need to add even more padding.
  
! The next revision of the resourceEditor will use a separate window for doing layout so that the size of a window is always accurate and shows the menubar of the app you're editing.
--- 14,18 ----
  Some of the components don't move or resize correctly all the time, you should report problems to the mailing list. The Choice component seems prone to this movement problem. If a component is difficult to select or move, you can always select it via the Property Editor and then change its position attribute via the Property Editor rather than trying to drag the control itself; the sizing handles should also work.
  
  When editing a dialog or other window that doesn't have a menubar, you'll probably need to increase the vertical size of the window by 20 or 30 pixels to compensate for the resourceEditor menubar. Once your layout looks the way you want it you can subtract the pixel padding you added earlier. On Microsoft Windows, the menubar may wrap if the width of the window is not wide enough, in which case you'll need to add even more padding.
  
! Some future revision of the resourceEditor will use a separate window for doing layout so that the size of a window is always accurate and shows the menubar of the app you're editing.