search for: set_range

...pan class="cx"> A gauge is a horizontal or vertical bar which shows a quantity (often time). </span><ins>+ +Gauge supports two working modes: determinate and indeterminate progress. + +The first is the usual working mode (see "set_value":#Gauge_setvalue +and "set_range":#Gauge_setrange) while the second can be used when +the program is doing some processing but you don''t know how much progress is +being done. +In this case, you can periodically call the "Pulse":gaugepulse.html +function to make the progress bar switch to indeterminate mode...

...arent, -1) - @log = log - @count = 0 - - Wx::StaticText.new(self, -1, "This example uses the Wx::SpinCtrl control.", Wx::Point.new(45,15)) - - sc = Wx::SpinCtrl.new(self, -1, "", Wx::Point.new(30, 50), Wx::Size.new(80, -1)) - sc.set_range(1,100) - sc.set_value(5) - # sc.enable(false) - end </del><ins>+ def initialize(parent, log) + super(parent, -1) + @log = log + @count = 0 + + Wx::StaticText.new(self, -1, + "This example uses the Wx::SpinCtrl control."...

...xception. I changed the typemap to construct a Ruby DateTime object when it is out of range. 3. DatePickerCtrl#get_range Looking at the DatePickerCtrl methods faced another problem: the #get_range method. It should be able to get the min and max date accepted by the control (if previously set by #set_range). But the method signature was bad, even swig''ed it still was: Boolean get_range(dt1, dt2) dt1 and dt2 were supposed to be out values (in C++ they are pointers) but swig handles them as input references. So i re-implemented the get_range method to return an two cells array containing the...

I''ve addressed all (I think/hope) of the review comments. The main change is to expose the guest virtual platform (e.g. memory layout and interrupt usage etc) to the toolstack via the public interface. This is then used during FDT generation. I have just codified the current defacto standard layout, it''s probably not the best layout but any change can be a separate patch/series.

Biggest change is to switch the new DTB node to /xen-core-devices instead of /xen at Stefano''s request. I also dropped the few patches title HACK etc which weren''t supposed to be there and fixed up some bits and pieces which folks commented on. George, WRT the freeze I think this is functionality which we cannot ship Xen 4.4 without. The impact is entirely constrained to the