Opened 9 years ago

Closed 8 years ago

#34 closed defect (fixed)

Float Spin Control does not honor range limits set in WXGlade, and range limits cannot be changed

Reported by: dtodd Owned by:
Priority: minor Milestone:
Component: common Version:
Keywords: Cc:


If we check the Range option (in wxglade) for one of our custom float spin controls, this range will not be honored when scrolling through various numbers.

I used the "Tip Angle" float spin control in the Optimal Control (alpha version) and set the limit from 0 to 100. When I went down in value it went right past zero.

Also, when you change the upper, or lower, limit to anything other than 100.0, or 0.0, it reverts back to the original value... i.e. they cannot be changed.

These effects were observed on Linux 10.4 and on Windows.

Note: Brian mentioned that he sets the limits, and step size, for these widgets in "the code" and not in the widget.

Change History (2)

comment:1 Changed 8 years ago by flip

Fixed in r3467.

As observed, setting the range explicitly via floatspin.SetRange() works fine. Setting the range in wxGlade did not. That's fixed. I was never too concerned about this because it's better practice to set ranges and default values explicitly in the code rather than burying them in wxGlade where they just become magic numbers. Nevertheless, this feature should work, and now it does.

comment:2 Changed 8 years ago by flip

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.