similar to: Bug: FXTable: programmatic deselection doesn't work as expected.

I''m using an RXTable in my application and I would like to be able to select a row and then press the Delete key to delete the selected row. This does not seem to work, however, as apparently keypresses are not initially recognized. In my FXTable derived class I have: connect(SEL_KEYRELEASE) do |sender, selector, event| puts "code = #{''%X'' %

Hi, I''m using FXRuby 1.6.13 under Windows XP / Ruby 1.8.6. I''ve noticed something strange when copying-pasting things between FXTable cells, and FXTextfields. ---------------------------------------------- 1) When copying the content of an FXTextfield, and pasting it into an FXTable cell, everything works fine. 2) When selecting an FXTable cell, issuing a "copy"

Hi, I''m trying to accomplish the following task: 1) Query database for records 2) Populate FXTable with first 50 records from cursor 3) Populate more rows as the table scrolls down To accomplish this I subclassed FXTable (class Table < FXTable) and defined the initialize method as shown below: def initialize(parent) super(parent,

Is there a way to make an FXTable''s column widths (and row heights) unchangeable by the user? By experimentation it looks to me like leaving out TABLE_COL_SIZABLE and TABLE_ROW_SIZABLE from the options field in FXTable.new() has no effect. I can still drag the intersection between two column heading buttons to change the column width. The code I''m using to test this is

Hi, Is it possible to wrap text inside an FXTable cell, just like it is possible with an FXText object? I''d like to display and edit multi-line text inside an FXTable cell. Thanks! Philippe

I have an application that uses an FXTable widget, and when the contents of a cell is being edited, I want to anticipate what the user wishes to enter (by matching the text with a previous entry), and present that for completion. (This is similar to how Excel works.) I''ve attempted to do this by using the FXTable getItem(currentRow, currentColumn).text method when a SEL_KEYRELEASE

On Fri, 22 Oct 2004 13:39:06 -0700, Bob Sidebotham <bob@windsong.bc.ca> wrote: > In 1.2 FXTable, numColumns is documented as numCols, but should be > numColumns, I think. Also the examples/table.rb app uses numCols, and > should use numColumns. Yes, you''re right. I''ve added both of these bugs to the FXRuby bug list, found here:

On Wed, 18 May 2005 23:12:03 +0400, Pavel Sokolov <elgato@rambler.ru> wrote : > I am still learning to deal with FOX and playing with different > widgets. I have encountered strange behavior of FXTable with regard to > style options. FXTable allows to resize rows and columns both w/ and > w/o options TABLE_ROW_SIZABLE, TABLE_COL_SIZABLE. This bug in FOX 1.2 was

When I empty and refill an FXTable multiple times with a large data set (10,000 rows x 1 column in the example below, around 1000 rows x 6 columns in a more complicated app), the application eventually fails with a segmentation fault. The number of repetitions required to produce the segfault is rather random, ranging from just a couple reps to 15 or 20 in some trials. The program disappears

On May 17, 2008, at 6:54 AM, David Toll wrote: > I tried to submit the following message to the "fxruby-users" > message board (I clicked the link to send it as an email to fxruby-users at rubyforge.org > , but the message did not appear). I conclude I do not know how to > submit questions to this message board. You need to be subscribed to the mailing list before you

On Feb 2, 2005, at 5:47 PM, dragoncity wrote: > am having problems with FXRuby 1.2 setting a cells color, > In the following code snippet, the variables rcnt & FLDFilename > are progam controlled, the two lines before the "puts" execute OK, > neither of > the setCellColor versions execute , both fail with > > `setCellColor'': table row out of bounds ,

I''m trying to set attributes of widgets in subclasses like the following. class PersonTable < FXTable def initialize(owner) options = TABLE_COL_SIZEABLE super(owner, nil, 0, options) visibleRows = 5 ... end end visibleRows doesn''t get set. However, if I do this self.visibleRows = 5 then it does. Shouldn''t it work without "self."?

Helmut, If I understand what you''re asking, I think the solution is to call create() on ic2 before using it: ic2.create @table.getItem(1, 1).icon = ic2 If this does not solve your problem, please try to express your question more clearly. Hope this helps, Lyle On Apr 24, 2006, at 1:36 AM, Helmut Hagemann wrote: > High > ? > i have trouble with FXTable > >

Hi all, Here is an excerpt of code (with the new syntax from upcoming wxRuby 1.9.2) : evt_checklistbox(my_checklist, :on_checklistbox) evt_listbox(my_checklist, :on_listbox) evt_listbox(my_list, :on_listbox) def on_checklistbox(event) checklist = event.event_object # puts "listbox - event : item[#{event.int}] checked : #{event.checked?}" puts "listbox -

Hi Lars, people. I''ve realized that currently the gem(version 1.6.26) doesn''t work with Ruby 2.0.0 in Windows 32 bits, neither the 64 bits version, I''m talking about the versions listed here: http://rubyinstaller.org/downloads/ . There you can see both versions of Ruby and also the both versions of the DevKit: mingw64-32 and mingw64-64. I''ve tested with both

I''m using a table in an application, and it worked in 1.0 - but in 1.2 this line: @result_table.getItem(0,j).button=true gives this error: main.rb:91:in `display_result'': undefined method `setButton='' for Id:Fox::FXTableItem (NoMethodError) What am I doing wrong?? (Plus - it''s not in the RDoc anymore... where did it go?) -Rich

All, A couple of new build platforms have come into the picture since the last FXRuby release and I''m trying to make sure they''re supported. That is to say, I want to be able to provide precompiled binary gems so that users on those platforms don''t have to build everything from source. I think I''m there, but I could use your help testing if you have

I just noticed that MDIClient windows do not automatically become current when they receive a mouse click, but only do so if the click happens inside of an enabled widget. This may very well be correct, but if so then what is the right way to handle it, if you want a more familiar window-manager behavior (click to focus)? For example, if you change the mditest.rb example like so... ---

Hello everyone and season's greetings. I have an array that looks like that R<-c(1,2,3,4,5,6). Is it possible to select all the elements but except one? For example to not select the third element and get back (1,2,4,5,6)? How can I do that? I would like to thank you in advance for your help Best Regards Alex [[alternative HTML version deleted]]

Hi there, Sorry I''m not sure if this is the correct mailing list for this question - I already tried tools and didn''t get any replies - please let me know if I should repost somewhere else. Anyways, I''ve been using some of the API''s in libxc to look at memory of a guest using the *xc_interface functions. I was wondering - is there a way using libxc or