[gnue] r8066 - trunk/gnue-forms

[johannes]

Author: johannes
Date: 2005-10-18 07:43:45 -0500 (Tue, 18 Oct 2005)
New Revision: 8066

Modified:
   trunk/gnue-forms/BUGS
Log:
Moved bugs to roundup


Modified: trunk/gnue-forms/BUGS
===================================================================
--- trunk/gnue-forms/BUGS       2005-10-18 09:44:35 UTC (rev 8065)
+++ trunk/gnue-forms/BUGS       2005-10-18 12:43:45 UTC (rev 8066)
@@ -1,64 +1,3 @@
-forms containing image widgets doesn't work if PIL not installed
-
-Really nasty:
-* calling clear() on a detail block (for example in a trigger) causes a new
-  detail recordset to be created that is not listed in the master's list of
-  cached detail recordset; so data entered into this recordset will never get
-  saved (probably calling clear() on a detail block should not be allowed at
-  all and raise an exception -- reinhard)
-* standing on last record in a grid, delete it then commit; the grid lines
-  get out of order, the number of lines is still as if no deletion occured.
-
-* Buttons cannot be used within a block having a rows-attribute
-
-* Doing a query in a multi block form posts a rollback to all blocks, but the
-  current empty record of other blocks stays there. This causes the backend
-  (in case of appserver) to get out of sync with the frontend and results in
-  a failure of saving some data from any of the other blocks later.
-  Reproduce: Appserver's sample.gfd, change to country tab, query, change to
-  person tab, enter anything, save.
-
-* There is no concept of "no record"; to display "nothing" (for example
-  when entering query mode or for the empty line in a dropdown), a new empty
-  record is created - and initialized. This shouldn't be.
-
-select text with mouse and cut doesn't work with wx driver
-
-tab key presses in dropdowns on Win32 are not correct with wx driver
-
-cursor placement went moving thru records is doing two refreshes.  Initialy
-it places the cursor at the front of the entry.  Then it correctly moves it
-to the end of the entry.
-
-it is not possible to dynamically disable a button
-
-it is not possible for a block to have *no* record loaded (record #-1);
-fields with a fk_source use record #-1 to indicate a NULL selection;
-consequently, the fk_source of a field cannot be used by a block.
-
-getParameter and setParameter in the trigger namespace do a string.lower()
-on the parameter name.  However the dict passed into a activateDialog is 
-case sensitive.  Removing the string.lower() calls make forms very slow.
-
-Dropdown problems:
-* if the list of allowed values for a dropdown contains an empty item (Python
-    None value), the text "None" is displayed in the dropdown
-* if a dropdown's FK description contains values with
-       length > the maxLength attribute of the entry, the 'long' value
-       cannot be selected
-
-win32 driver:
-* Multiline edits:
-  - if one enters text, presses return, backspace and return again, the cursor
-    position is no longer correct
-  - the up- and down-keys cannot be used to navigate *within* a multiline edit
-    and to move the focus if pressed on the first or last line (see gtk2)
-* Ctrl-Q does not work to close a form
-* Scrollbar: if scrolled donw to the last record, the scrolled up to the first
-  using the up-arrow, all visible rows of a block are filled with the first
-  record
-
-GTK2 Multiline edit is in select mode when entered, one can select the text
-  entered just by moving the mouse. After a mouseclick it returns to normal
-  mode. Being in select mode disables ability to click away from the control.
-  
+Please use our bug tracking system at
+http://www.gnuenterprise.org/roundup/gnue/ to get a list of outstanding bugs,
+features or wishes.