search for: evt_timer

...entire GUI freezes and looks like crap for about 5 seconds. Basically I''m looking for an easy way to avoid this so the end user doesnt freak out and think the program crashed or anything. I found this code in the thread mentioned above: def on_init t = Wx::Timer.new(self, 55) evt_timer(55) { Thread.pass } t.start(100) which would be used in the on_init of the main App. I understand what it is doing (creates a 100ms timer which calls Thread.pass every iteration), but I don''t understand how this can help the problem. I assume that if I do my processing in a new th...

Hey! I would need a popup window like this (not necessarily associated to a taskbaricon): http://www.venraiker.com/wp-content/uploads/2006/03/libnotifyvx.png I should be possible to show such a window for a certain time, displaying a certain message. Is a similar thing possible with wx? Are there oder options? thx ck -- Posted via http://www.ruby-forum.com/.

I''ve seen a few e-mails about multithreading with respect to wxruby but nothing recent. Unless I''m mistaken, and that may be, there still appear to be problems. The following code seems to hang my spawned thread in favor of the wxruby event loop: Thread.new do puts "in thread" loop do sleep 5 puts "looping" end end puts "main

These files implement the Timer. There''s also a patch to introduce EVT_TIMER Roy _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users

...nresponsive. (Similar problems with threads have been discussed previously on the wxRuby mailing list.) require ''rubygems'' require ''wx'' class MyApp < Wx::App def on_init #Animate every 33 milliseconds. t = Wx::Timer.new(self, 55) evt_timer(55) { Thread.pass } t.start(33) #Containing frame. frame = Wx::Frame.new(nil, :size => [300, 300]) frame.show #Offscreen drawing buffer. buffer = Wx::Bitmap.new(300, 300) #Displays drawing. window = Wx::Window.new(frame, :size => [300, 300])...

I have a WxRuby application that takes a few inputs from the user and uses that information to search through a large file for matches. The application works very well, with one exception. If I click anywhere in the frame while the application is searching through the long file, the application hangs. Has anyone experienced anything similar to this? Any suggestions on how I can fix this? Thanks

...dow = Wx::Window.new(frame, :size => [300, 300]) window.evt_paint do |event| update_window(window, buffer) end #Initialize drawing loop counter. @i = 0 #Animate periodically. timer_id = Wx::ID_HIGHEST + 1 t = Wx::Timer.new(self, timer_id) evt_timer(timer_id) do animate(window, buffer) #No effect. #self.dispatch #No effect. #self.dispatch while self.pending #No effect. #self.yield end t.start(33) end def animate(window, buffer) green_pen = Wx::Pen.new(Wx::Colou...

...regular time intervals. It appears that Wx::Timer should do the job, but I haven''t been able to figure out how to use in in wxruby. The documentation for this is still for C++. I''ve tried the following: (In my form class''s initialize method): @timer = Wx::Timer.new evt_timer(@timer.id) {|event| onTimer(event)} @timer.start(1000) Later in the form, I have the onTimer routine defined. The problem is that its never being called. Does anyone know how to use Wx::Timer? Thanks in advance ---Michael -- Posted via http://www.ruby-forum.com/.

...t;@@ -217,8 +217,8 @@ </span><span class="cx"> ["EVT_TASKBAR_MOVE", 1, "wxEVT_TASKBAR_MOVE"], </span><span class="cx"> ["EVT_KILL_FOCUS", 1, "wxEVT_KILL_FOCUS"], </span><span class="cx"> ["EVT_TIMER", 2, "wxEVT_TIMER"], </span><del>-["EVT_CREATE", 2, "wxEVT_CREATE"], -["EVT_DESTROY", 2, "wxEVT_DESTROY"], </del><ins>+["EVT_WINDOW_CREATE", 1, "wxEVT_CREATE"], +["EVT_WINDOW_DESTROY", 1, &q...

...VT_PAINT => Wx::PaintEvent, - Wx::EVT_ERASE_BACKGROUND => Wx::EraseEvent, - Wx::EVT_UPDATE_UI => Wx::UpdateUIEvent, - Wx::EVT_SIZE => Wx::SizeEvent, - Wx::EVT_SIZING => Wx::SizeEvent, - Wx::EVT_MOVE => Wx::MoveEvent, - Wx::EVT_MOVING => Wx::MoveEvent, - Wx::EVT_TIMER => Wx::TimerEvent, - Wx::EVT_CHAR => Wx::KeyEvent, - Wx::EVT_CHAR_HOOK => Wx::KeyEvent, - Wx::EVT_KEY_DOWN => Wx::KeyEvent, - Wx::EVT_KEY_UP => Wx::KeyEvent, - Wx::EVT_COMMAND_FIND => Wx::FindDialogEvent, - Wx::EVT_COMMAND_FIND_NEXT => Wx::FindDialogEvent, -...

...ot;, true, 0) set_selection(0) end end class MyApp < Wx::App def on_init frame = Wx::Frame.new(nil, :size => Wx::Size.new(686, 303), :title => "MultiTool") notebook = MainNB.new(frame, 0) t = Wx::Timer.new(self, 55) evt_timer(55) { Thread.pass } t.start(20) frame.show end end MyApp.new.main_loop --- END --- So that is where I create the timer and pass the thread... then the thread is actually created when a button is pressed on one of the panels in the notebook. The end result is that whatev...

....new( self, -1, 50, + Wx::Point.new(110, 140), Wx::Size.new(25,250), + Wx::GA_VERTICAL) + @g3.set_bezel_face(3) + @g3.set_shadow_width(3) + + # start a timer to move the gauges forward every 1/4 s + timer = Wx::Timer.new(self, 5001) + evt_timer(5001) { move_gauges } + timer.start(250) + end + + # advance the gauges + def move_gauges + @count +=1 + if @count > 50 + @count = 0 </ins><span class="cx"> end </span><ins>+ @g1.set_value(@count) + @g2.set_value(@count) + @g3.s...

...goto bail; + + udp_io->b = b; + + udp = (EFI_UDP4 *)b->this; + udp_io->Protocol_Udp4 = udp; + + socket->net.efi.context = udp_io; + + // + // Create the timer used to time out transmit, receive, and get map events + // + status = uefi_call_wrapper(BS->CreateEvent, 5, + EVT_TIMER, + TPL_CALLBACK, + NULL, + NULL, + &udp_io->Timeout_Timer + ); + if (EFI_ERROR (status)) + goto bail; + + // + // Create the event to signal when the send/receive callback function ends + // correctly. + // + status = uefi_call_wrapper(BS->Create...

...ot;, 2, "wxEVT_COMMAND_TREE_END_DRAG"], </span><span class="cx"> ["EVT_COMMAND_LEFT_CLICK", 2, "wxEVT_COMMAND_LEFT_CLICK"], </span><span class="lines">@@ -209,6 +219,15 @@ </span><span class="cx"> ["EVT_TIMER", 2, "wxEVT_TIMER"], </span><span class="cx"> ["EVT_CREATE", 2, "wxEVT_CREATE"], </span><span class="cx"> ["EVT_DESTROY", 2, "wxEVT_DESTROY"], </span><ins>+["EVT_SCROLL", 1, &quo...

The variable 'ok' is never used and generates a warning. Remove it. Also ntfssect.c is designed to be compiled in non Unicode mode when using MSVC compilers, so remove all ambiguity about it (LPCTSTR -> LPCSTR, use of 'A' API calls) so that it doesn't break when compiled in Unicode mode, which is what Rufus uses with MSVC. -------------- next part --------------

Hi, The last couple of days I''ve been trying to get back on the wxRuby-horse however I''ve ran into some problems while compiling/testing the subversion sources. Mind, the 1.9.2 official release works fine. Absolutely no problems whatsoever. The first hurdle was that the rake install target doesn''t work. It fails on rakewx.rb:145. Looking into it I found that

...t;@@ -207,6 +207,8 @@ </span><span class="cx"> ["EVT_TASKBAR_MOVE", 1, "wxEVT_TASKBAR_MOVE"], </span><span class="cx"> ["EVT_KILL_FOCUS", 1, "wxEVT_KILL_FOCUS"], </span><span class="cx"> ["EVT_TIMER", 2, "wxEVT_TIMER"], </span><ins>+["EVT_CREATE", 2, "wxEVT_CREATE"], +["EVT_DESTROY", 2, "wxEVT_DESTROY"], </ins><span class="cx"> ] </span><span class="cx"> </span><span class=&...

...t, + Wx::EVT_IDLE => Wx::IdleEvent, + Wx::EVT_PAINT => Wx::PaintEvent, + Wx::EVT_UPDATE_UI => Wx::UpdateUIEvent, + Wx::EVT_SIZE => Wx::SizeEvent, + Wx::EVT_SIZING => Wx::SizeEvent, + Wx::EVT_MOVE => Wx::MoveEvent, + Wx::EVT_MOVING => Wx::MoveEvent, + Wx::EVT_TIMER => Wx::TimerEvent, + Wx::EVT_CHAR => Wx::KeyEvent, + Wx::EVT_CHAR_HOOK => Wx::KeyEvent, + Wx::EVT_KEY_DOWN => Wx::KeyEvent, + Wx::EVT_KEY_UP => Wx::KeyEvent, + Wx::EVT_COMMAND_FIND => Wx::FindDialogEvent, + Wx::EVT_COMMAND_FIND_NEXT => Wx::FindDialogEvent, +...

paul.allton at uk.bnpparibas.com wrote: > I''m a big fan of automated UI testing (i.e. driving the UI from some robot API). I appreciate this > is potentially a whole new project, but does wxwidgets provide a method of clicking buttons, > typing into components ... if so, would it be technically possible to expose this in wxruby. I like automated UI testing too, but