search for: hogbaysoftware

...rent Status: Open Resolution: None Priority: 3 Submitted By: Nobody (None) Assigned to: Nobody (None) Summary: Wx::STAY_ON_TOP and Wx::NO_BORDER messes with Sizer layouts. Initial Comment: I am making a full-screen app that I want to stay on top (to re-create something similiar to this app: http://hogbaysoftware.com/products/writeroom for a multi-platform use.) however, I am running into a strange issue. If I use this: def on_init x = Wx::SystemSettings.get_metric(Wx::SYS_SCREEN_X) y = Wx::SystemSettings.get_metric(Wx::SYS_SCREEN_Y) @frame = Wx::Frame.new(nil, -1, APP_NAME, [0, 0], [x, y], Wx:...

I have a Topic that has_many comments. In the search results only want Topics to show up, but I want them to include the text of the comments that they have when they are indexed. To do this I''ve added a :comments_text field for acts_as_ferret and the comments_text method gathers the text from all comments up into a string that can be indexed. The trick is that when comments are added,

I''m not really sure if this is a bug, but it makes my search results look a bit strange. I have an acts_as_ferret declaration that looks like: acts_as_ferret :store_class_name => true, :remote => true, :fields => { :ferret_name => { :store => :yes, :boost => 2 }, :ferret_content => { :store => :yes } } I store both fields so that I

I''m having a problem where the DRb server seems to be disappearing (crashing?) and I don''t know how to track down the cause or work around the problem. Unfortunately I haven''t found a way to reproduce the problem, but it seems to happen fairly often (maybe once a day). Other then that ferret seems to be working well. I can''t seem to find any trace of the