I thought I would list some fdesign bugs I found, in case they aren't already
known. I'd also like to say the the spec editing is great, it makes it so
much easier to set things in fdesign rather than in the C code.
If the snap size is changed to less than 10, and the form is made a size that
is not a multiple of ten, it will be rounded down after quiting fdesign and
re-opening the fd file. Object in the form don't get rounded, but the form
itself does.
The return type for sliders (end & changed, changed, always, etc.) doesn't
get saved in the FD file or appear in the C code.
The menu for return type for counters is the same as the one for sliders in
fdesign, but in the manual they are different. counters have TRUE and FALSE,
while sliders have END_CHANGED and so on.
For valsliders, the increment value is rounded down to the precision. So if
you set the increment value to say .0625 and have a precision of 2 digits, it
gets saved in the C code and FD file as .06. I was under the impression that
precision only effected the displayed values, and that internally everything
kept full float precision.
|Gazing up to the breeze of the heavens \ on a quest, meaning, reason |
|came to be, how it begun \ all alone in the family of the sun |
|curiosity teasing everyone \ on our home, third stone from the sun. |
|Trent Piepho (xyzzy@u.washington.edu) -- Metallica |
_________________________________________________
To unsubscribe, send the message "unsubscribe" to
xforms-request@bob.usuf2.usuhs.mil or see
http://bob.usuf2.usuhs.mil/mailserv/xforms.html
Xforms Home Page: http://bragg.phys.uwm.edu/xforms
List Archive: http://bob.usuf2.usuhs.mil/mailserv/list-archives/