fxruby-users Mailing List for FXRuby (Page 10)

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Joel VanderWerf wrote:
> Something else that may help:

Or not... Now I realize that the OP was asking for "messages", not 
"methods".

ly...@kn... wrote:
> On Wed, 12 May 2004 04:16:06 -0700 (PDT), Vladislav Guzov
> <vl...@ya...> wrote :
> 
> 
>>Is it possible to get list of messages for a widget ?
> 
> 
> The documentation page for each widget lists the messages that it sends to
> its message target. For example, if you look at the docs for FXButton:
> 
>     http://www.fxruby.org/doc/api/classes/Fox/FXButton.html
> 
> you'll see that it sends the SEL_KEYPRESS, SEL_KEYRELEASE,
> SEL_LEFTBUTTONPRESS, SEL_LEFTBUTTONRELEASE and SEL_COMMAND messages to its
> target.

Something else that may help:

$ irb -r fox
irb(main):001:0> include Fox
=> Object
irb(main):002:0> FXWindow.instance_methods.grep /set/
=> ["setTarget", "setInitial", "setDNDData", "setKey", "setBackColor", 
"setSelector", "setShown", "setUserData", "setEnabled", "setX", "setY", 
"setWidth", "setHeight", "setDragCursor", "setDragRectangle", 
"instance_variable_set", "setLayoutHints", "setFocus", 
"setCursorPosition", "setAccelTable", "setVisual", "setDefault", 
"setDefaultCursor"]

On Wed, 12 May 2004 09:17:38 -0700, Bill Atkins <se...@ba...> wrote :

> Have you considered splitting fxruby.so into smaller .so files?

No.

On Wed, 12 May 2004 07:41:32 -0700 (PDT), Vladislav Guzov
<vl...@ya...> wrote :

> I know about documentation but a tool like GUI builder
> is not. Is it possible to get list using method or
> some other way?

No.

Just a small update:

* Fixed bug that allowed double-clicking of column header.
* Added methods to allow you to easily set an alternating row background 
color.
---------------------------------------------------------------------------------

What is listview?

Listview.rb is a module containing a class that can be used to create 
listviews (multi-column listboxes) in FXRuby.

Some of the features/advantages of listview over an FXIconList are:

* Clickable column headers that sort correctly based on data type.
* Left or right justified column data.
* Gridlines
* Alternating row colors.
* Custom sort arrow.
* Automatic commas and dollar sign for columns that you specify.

It is sub-classed from FXTable.  You can read more about listview at:

http://www.netpromi.com/listview.html

and download it at:

http://www.netpromi.com/files/listview_1.2.0.zip

Thanks, as always to Jeroen and Lyle!

Jamey Cribbs
jc...@tw...

On Wed, 12 May 2004 04:16:06 -0700 (PDT), Vladislav Guzov
<vl...@ya...> wrote :

> Is it possible to get list of messages for a widget ?

The documentation page for each widget lists the messages that it sends to
its message target. For example, if you look at the docs for FXButton:

    http://www.fxruby.org/doc/api/classes/Fox/FXButton.html

you'll see that it sends the SEL_KEYPRESS, SEL_KEYRELEASE,
SEL_LEFTBUTTONPRESS, SEL_LEFTBUTTONRELEASE and SEL_COMMAND messages to its
target.

Hope this helps,

Lyle

On May 11, 2004, at 8:36 PM, Bill Atkins wrote:

> Does FXRuby have any way to change fonts in a tree list on a per-item 
> basis?

Not an easy way. You should be able to subclass FXTreeItem and override 
its draw() method, but I don't have an example handy (anyone else done 
this?)

On May 11, 2004, at 8:29 PM, Bill Atkins wrote:

> I'd like to use FOX in one of my projects, but I'd also like to have 
> antialiased
> fonts eventually.  I've heard it mentioned that FOX 1.2 supports it, 
> but the
> FXRuby bindings don't yet work with 1.2.
>
> Is there any schedule for this to happen?  I don't need my app to have
> antialiasing immediately, but I'd like to make sure my toolkit will at 
> least
> have it in the near future.  I'd be willing to help code if it would 
> hasten the
> addition of antialiasing to FXRuby.

First of all, I sincerely appreciate your offer of help. But because I 
don't want FXRuby to significantly "fork" from FOX -- that is, the 
current stable version of FOX -- I really don't want to try to 
back-port FOX 1.2's support for antialiased fonts into FXRuby.

As for the larger question, "When will FXRuby work with FOX 1.2", I am 
still sticking to my vow that it won't be supported until FOX 1.2 has a 
stable API. This is not an arbitrary decision ;)

Some old-timers on the list may remember how things went with FXRuby 
before the FOX 1.0 API was officially "frozen". It was a serious 
dependency nightmare; FXRuby version 0.99.188 would only work with FOX 
version 0.99.188, and not any earlier or later versions. Just that one. 
It would be the same situation with the current development series. It 
is generally true that the FOX 1.1 API changes with each new release 
and that would necessitate a new FXRuby 1.1 specifically aimed at that 
one. I am too old and feeble-minded to keep up that pace. ;)

Hi, guys...

I abandoned work on Tycho about six weeks ago because of Fox problems I
couldn't seem to get around.

But after looking at GTK (which doesn't do MDI) and wxruby (which is
apparently based on GTK), I now think I may end up back in Foxville
after all.

Any help with these problems is appreciated...

Here's the link:

   http://rubyforge.org/frs/download.php/451/tycho-0.0.0.7.tgz

Here's a quick-start:

   tar zxvf tycho-0.0.0.7.tgz
   cd tycho
   mkdir -p exper/data   # Create dir manually, oops
   ruby mkdata.rb        # Create fake data tree
   ruby tycho.rb         # Now run the app

Now, there are two problems...

1. New notes (MDI children) don't show up immediately (and I *am*
    doing a #create, at least I think I am)

    To reproduce:
      a. Go into the tree, expand the "Work stuff" branch
      b. Click on the "Interesting work" topic
      c. Hit the "New note" button
      d. Give it any title when prompted
      e. Notice that an empty note does NOT appear on the right. Why??
      f. Now switch topics -- click on "Boring work"
      g. Now switch back to "Interesting work"
      h. Now the note is there and all is well.

2. Also: Clicking around in the tree gives me errors like
      FXRbGetRubyObj(this=0x08eff288) returns non-Qnil
    over and over -- once per click maybe? What's wrong here?

Thanks,
Hal Fulton

Thanks for the help! I figured the problem was along those lines, but
hadn't been successful as of then. Your code helped a lot, (though the
canvas had ended up being smaller than what the table needed, its size
depending on the number of rows and columns... I got that one fixed
though :) ).
Now to phase 2 - reimplement connect(...), and phase 3 - profit! 

On Mon, 10 May 2004 19:33:34 -0500, Lyle Johnson <ly...@kn...> wrote:
> 
> 
> On May 5, 2004, at 11:22 AM, Claus Spitzer wrote:
> 
> > However, I want to put the canvas in a FXScrollArea because eventually
> > it will be larger than the screen... and that's what I'm having
> > trouble with.
> 
> Please see the question "Why Can't I Place a Fixed-Size FXCanvas inside
> an FXScrollwindow?" near the bottom of this page:
> 
>         http://www.fox-toolkit.net/cgi-bin/wiki.pl?FAQ
> 
> For your example program, I replaced these lines:
> 
>         @scroller = FXScrollArea.new(...)
>         @canvas = FXCanvas.new( @scroller, nil, 0, LAYOUT_FILL_X|LAYOUT_FILL_Y
> )
> 
> with these:
> 
>         @scroller = FXScrollWindow.new( self, LAYOUT_FILL_X|LAYOUT_FILL_Y )
>         canvasFrame = FXVerticalFrame.new( @scroller,
> LAYOUT_FILL_X|LAYOUT_FILL_Y )
>         @canvas = FXCanvas.new( canvasFrame, nil, 0,
> LAYOUT_FIX_WIDTH|LAYOUT_FIX_HEIGHT, 0, 0, 600, 400 )
> 
> and I get what looks reasonable. It draws a pretty picture, anyways ;)
> 
> Hope this helps,
> 
> Lyle
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by Sleepycat Software
> Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
> higher performing products faster, at low TCO.
> http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
> _______________________________________________
> Fxruby-users mailing list
> Fxr...@li...
> https://lists.sourceforge.net/lists/listinfo/fxruby-users
>

On May 5, 2004, at 11:22 AM, Claus Spitzer wrote:

> However, I want to put the canvas in a FXScrollArea because eventually
> it will be larger than the screen... and that's what I'm having
> trouble with.

Please see the question "Why Can't I Place a Fixed-Size FXCanvas inside 
an FXScrollwindow?" near the bottom of this page:

	http://www.fox-toolkit.net/cgi-bin/wiki.pl?FAQ

For your example program, I replaced these lines:

	@scroller = FXScrollArea.new(...)
	@canvas = FXCanvas.new( @scroller, nil, 0, LAYOUT_FILL_X|LAYOUT_FILL_Y 
)

with these:

	@scroller = FXScrollWindow.new( self, LAYOUT_FILL_X|LAYOUT_FILL_Y )
	canvasFrame = FXVerticalFrame.new( @scroller, 
LAYOUT_FILL_X|LAYOUT_FILL_Y )
	@canvas = FXCanvas.new( canvasFrame, nil, 0, 
LAYOUT_FIX_WIDTH|LAYOUT_FIX_HEIGHT, 0, 0, 600, 400 )

and I get what looks reasonable. It draws a pretty picture, anyways ;)

Hope this helps,

Lyle

Begin forwarded message:

> From: jeroen <je...@fo...>
> Date: May 7, 2004 7:50:04 PM CDT
> To: FOX Announce <fox...@li...>
> Cc: FOX Users <fox...@li...>
> Subject: [Foxgui-users]FOX toolkit site news...
> Reply-To: je...@fo...
>
>
> Hello,
>
> FOX Toolkit is in the process of (1) changing IP number and (2)  
> changing
> DNS registry.  During the coming week, the site may be flaky.
>
>
>
>
> Regards,
>
> 		- Jeroen
>
>
>
> --  
> +---------------------------------------------------------------------- 
> ------+
> | Copyright (C) 23:50 12/11/2003 Jeroen van der Zijp.   All Rights  
> Reserved. |
> +---------------------------------------------------------------------- 
> ------+

I have just recently started using FXRuby (~1 month), and up until
this last week I was working mostly with FXTable... However, because
FXTable doesn't let me individually set the color of FXTableItems, I
tried to rewrite my programs using an FXCanvas and drawing the items
myself. I started with the 'bounce.rbw' example that comes with the
Ruby installer (using 1.8.0-10). I got the drawing part sorted out.
However, I want to put the canvas in a FXScrollArea because eventually
it will be larger than the screen... and that's what I'm having
trouble with. I assume that I'm probably missing out on something...
the program that I started with uses an FXImage to draw the actual
image, then puts it on the canvas (or so I understand... please
correct me if I'm wrong). I thought that if I put the ScrollArea in
the MainWindow and then use it as the parent for the canvas I could
scroll the canvas, but something seems to have gon ehorribly wrong
along the way. I am unsure as to how the backbuffer (FXImage) part
operates. I'd appreciate if someone could enlighten me on this.
Attached is the tarball with my program. The part that I'm having
problems with starts on line 185. Thank you in advance for any
assistance...
   -CWS

On Monday 03 May 2004 09:22 pm, Lyle Johnson wrote:
> On May 3, 2004, at 8:46 PM, Claus Spitzer wrote:
> > Greetings!
>
> Wow, a post from a GMail account! How glamorous ;)
>
> > Is there a way to use gradients with FXDC::FillRectangle? Are there
> > other ways of implementing gradients in FXRuby? I couldn't find
> > anything relevant in the api docs. FXDC fill styles don't mention it,
> > but I wonder how this is implemented in the color wheel, and if there
> > are methods other than FXDC to implement this.
>
> [You might also want to post this question to the foxgui-users mailing
> list, since it's not FXRuby-specific.]
>
> I'm pretty sure that the disk used for the FXColorWheel is an FXImage
> with dithering turned on, and that's what's creating the gradient-like
> effect. Other than that, I don't think there was much support for
> painting with gradients in FOX 1.0. FOX 1.2 (available sometime in the
> future) will have better support for this, I think, but that's still a
> ways off, I think.

The support that Lyle is talking about is in FXImage, not in FXDC; in other
words, you have to generate a gradient into the image, then draw the image.

You can try drawing a gradient using many small rectangles, each filled
with uniform color.

I used the following code to do it:

#define MAXSTEPS 128

...

      r1=FXREDVAL(fill.lower);   r2=FXREDVAL(fill.upper);   dr=r2-r1;
      g1=FXGREENVAL(fill.lower); g2=FXGREENVAL(fill.upper); dg=g2-g1;
      b1=FXBLUEVAL(fill.lower);  b2=FXBLUEVAL(fill.upper);  db=b2-b1;

      n=FXABS(dr);
      if((t=FXABS(dg))>n) n=t;
      if((t=FXABS(db))>n) n=t;

      n++;
      if(n>width) n=width;
      if(n>MAXSTEPS) n=MAXSTEPS;

      rr=(r1<<16)+32767;
      gg=(g1<<16)+32767;
      bb=(b1<<16)+32767;
      xx=32767;

      dr=(dr<<16)/n;
      dg=(dg<<16)/n;
      db=(db<<16)/n;
      dx=(width<<16)/n;

      do{
        xl=xx>>16;
        xx+=dx;
        xr=xx>>16;
        dc.setForeground(FXRGB(rr>>16,gg>>16,bb>>16));
        dc.fillRectangle(xl,0,xr-xl,height);
        rr+=dr;
        gg+=dg;
        bb+=db;
        }
      while(xr<width);

The rationale of this code is as follows:

	1) The number of rectangles is determined by the
	   variation of the largest color-component.

	2) We draw no more rectangles than pixels (duh!)

	3) We draw no more than MAXSTEPS rectangles, if (1) and (2)
	   would exceed this threshold.

	4) All the math is evaluated in fixed-point (16.16) precision;
	   rounding is necessary to ensure that you're not off-by-one
	   near the borders.

On 24 bit color systems, the approach works pretty well, and in many
cases the color variations are not so dramatic so it can be pretty
fast.

The downside is that its not easy to draw gradients at an angle.

Anyway, this may make it into FXDC as an API one day; especially
if I manage to generalize it beyond drawing rectangles somehow.

Regards,

		Jeroen

-- 
+----------------------------------------------------------------------------+
| Copyright (C) 23:50 12/11/2003 Jeroen van der Zijp.   All Rights Reserved. |
+----------------------------------------------------------------------------+

On May 3, 2004, at 8:46 PM, Claus Spitzer wrote:

> Greetings!

Wow, a post from a GMail account! How glamorous ;)

> Is there a way to use gradients with FXDC::FillRectangle? Are there
> other ways of implementing gradients in FXRuby? I couldn't find
> anything relevant in the api docs. FXDC fill styles don't mention it,
> but I wonder how this is implemented in the color wheel, and if there
> are methods other than FXDC to implement this.

[You might also want to post this question to the foxgui-users mailing 
list, since it's not FXRuby-specific.]

I'm pretty sure that the disk used for the FXColorWheel is an FXImage 
with dithering turned on, and that's what's creating the gradient-like 
effect. Other than that, I don't think there was much support for 
painting with gradients in FOX 1.0. FOX 1.2 (available sometime in the 
future) will have better support for this, I think, but that's still a 
ways off, I think.

Greetings!
Is there a way to use gradients with FXDC::FillRectangle? Are there
other ways of implementing gradients in FXRuby? I couldn't find
anything relevant in the api docs. FXDC fill styles don't mention it,
but I wonder how this is implemented in the color wheel, and if there
are methods other than FXDC to implement this. Cheers
   -CWS

Aha, that is nice to know...thanks!  I will now enjoy deleting this code
from my program.

Oliver Smith

> -----Original Message-----
> From: fxr...@li...
> [mailto:fxr...@li...]On Behalf Of Gilles
> Filippini
> Sent: Sunday, April 25, 2004 3:32 PM
> To: fxr...@li...
> Subject: Re: [Fxruby-users] segfault in GC::start after accessing
> verticalScrollbar.position from overloaded moveContents
>
>
> Oliver Smith a écrit :
> > (sorry Lyle, forgot to switch addresses the first time :)
> >
> > Hello,
> >
> > I'm trying to bypass a bug in FXScintilla which causes the
> widget to scroll
> > up forever when you try
> > to scroll with a mouse wheel, and I figured out through trial
> and error that
>
> This bug is fixed in the FXScintilla CVS repository.
> _gilles.
>
> >
> [snip]
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
> For a limited time only, get FREE Ground shipping on all orders of $35
> or more. Hurry up and shop folks, this offer expires April 30th!
> http://www.thinkgeek.com/freeshipping/?cpg297
> _______________________________________________
> Fxruby-users mailing list
> Fxr...@li...
> https://lists.sourceforge.net/lists/listinfo/fxruby-users
>

Oliver Smith a =E9crit :
> (sorry Lyle, forgot to switch addresses the first time :)
>=20
> Hello,
>=20
> I'm trying to bypass a bug in FXScintilla which causes the widget to sc=
roll
> up forever when you try
> to scroll with a mouse wheel, and I figured out through trial and error=
 that

This bug is fixed in the FXScintilla CVS repository.
_gilles.

>=20
[snip]

(sorry Lyle, forgot to switch addresses the first time :)

Hello,

I'm trying to bypass a bug in FXScintilla which causes the widget to scroll
up forever when you try
to scroll with a mouse wheel, and I figured out through trial and error that
if I subclass FXScintilla (which is a subclass of FXScrollArea), overload
moveContents and reimplement it with the following:

def moveContents(new_x, new_y)
	old_position = verticalScrollbar.position
	super
	verticalScrollbar.position = old_position
end

the erratic behavior goes away.  I thought I was pretty clever for a while,
but now it turns out that I'm getting a weird segfault when I initiate
garbage collection later in my program.  I can play around with the code in
other ways to make it appear or disappear, but it seems to be pretty hard to
pin down.  I'm guessing that the ruby garbage collector thinks it needs to
free verticalScrollbar, and the segfault occurs because the C++ destructor
has already taken care of it?  If I comment out the two lines that access
verticalScrollbar, it starts working.  If I call the same two lines outside
of the overloaded moveContents, no segfault (but of course the original bug
is still there).

Any ideas?  If I'm not supposed to be overloading moveContents or accessing
verticalScrollbar.position, is there another way to accomplish the same
effect?

Thanks,

Oliver Smith

On Apr 18, 2004, at 8:40 PM, John Reed wrote:

> I=92m trying to put a workable hyperlink on my FXDialogBox screen. =
Have=20
> you done anything like this?

I haven't done anything like this, but if I were going to I think I'd=20
use an FXButton widget as a jumping-off point. The default frame=20
options for an FXButton cause it to be drawn with a "raised" and=20
"thick" border (i.e. the FRAME_RAISED and FRAME_THICK options). If you=20=

change these settings, either at construction time:

	flatButton =3D FXButton.new(parent, text, tgt, sel,=20
JUSTIFY_NORMAL|ICON_BEFORE_TEXT, ...)

or after:

	flatButton =3D FXButton.new(...)
	flatButton.frameStyle =3D FRAME_NONE

you'll get a button that looks like an FXLabel, but is still clickable.=20=

You could then wire-up the command handler for the button to launch a=20
web browser (or whatever):

	flatButton.connect(SEL_COMMAND) {
		system("mozilla")
	}

What I'm not sure about is whether there's a way to draw the label text=20=

underlined, so that it will look like a traditional hyperlink.

Hope this helps,

Lyle

On Apr 9, 2004, at 9:25 AM, Richard wrote:

> I've looked around a little (admittedly not a lot), but I can't find
> any reference to minimizing an application to the taskbar in windows
> (win2000/XP)...

<snip>

> Any suggestions?

I don't know the answer, and it doesn't appear that anyone else does 
either ;) You might follow-up on the foxgui-users mailing list (or 
search their archives) to see if there are any hints...

On Apr 9, 2004, at 9:19 AM, Richard wrote:

> I'm trying to figure out how to get the method 'handle' to work.

You call handle() on a FOX object to send a FOX message to that object, 
e.g.

	obj.handle(sender, message, message_data)

> I've done something similar to:
> test_handle=FXButton.new(mainwin_reference,"Text for button").connect
> (SEL_COMMAND) { |sen,sel,data|
>    puts "You've pressed me"
>    puts sen
>    puts sel
>    puts data
> }

OK. You call connect() on a FOX object to register a message handler 
for a particular message type that the object sends to its target. In 
this case, you know that the FXButton sends a SEL_COMMAND message to 
its message target whenever it (the button) is pressed, and you're 
designating a special, hidden FOX object to handle that message that 
the button sends. You can imagine it going something like this:

	button = FXButton.new(...)
	connectedObject = FXObject.new
	button.target = connectedObject

The "connectedObject" is wired-up to listen for the SEL_COMMAND message 
and execute the block you passed in. Of course, there's more to it than 
that, but that's the basic idea ;)

> Then using that same information I call 'handle' using the button as a
> reference, but it doesn't trigger the "You've pressed me" statement
> (I don't have the code infront of me and I'd be afraid I'd mess it
> up.).

OK. You should do something like this:

	button.handle(sender, MKUINT(0, SEL_COMMAND), null)

This sends the message to the button first. The button then forwards 
the message to its target (the "connectedObject" that actually stores 
your message-handler block).

> I know I'm using 'handle' semi-correctly, since I can get the button
> to look 'pressed' (and not released) I think it was ID_CHECKED or
> something like that (I went through all of the ID_WHATEVERS from the
> RDoc page on FXWindow), but I can't get the "You've pressed me"
> handler to fire.
>
> Thanks in advance for any help I get... What am I doing wrong?

Sounds like you're close; just use a zero for the first argument to 
MKUINT() and I think you'll get the effect you're after.

Hope this helps,

Lyle

On Apr 17, 2004, at 10:59 PM, John Reed wrote:

> 	1.  	If I put a line of code in my FXDialogBox initialize def =
that=20
> sets the focus to the first field, then my Ctrl-C menu command which=20=

> executes ID_CANCEL doesn=92t work without pressing the tab to go to =
the=20
> next field. Without the set focus on the 1st widget, the Ctrl-C works=20=

> fine. Is there something else that I need to do in my code?

I know that the text field widget (FXTextField) catches Ctrl+C (for=20
"Copy") and so it doesn't surprise me that it never executes the=20
ID_CANCEL for the focused text field (e.g. in the first case). I am=20
actually surprised that it *does* work when you tab to the next field,=20=

assuming that that widget is also a text field.

> 	2.  	When a message box event gets fired from my FXDialogBox, =
the=20
> focus doesn=92t return to the FXDialogBox after I close the message =
box=20
> unless I click on it. Is there an event that I can fire that will=20
> automatically do this?

What happens if you do:

           self.handle(self, MKUINT(0, SEL_FOCUS_SELF), null)

where here, "self" is a reference to the dialog box?

> Thanks for your help.

No problem, hope this helps.

Lyle

Jordan, Tom wrote:

>Hi Jamey:
>
>However, if you double click on the column
>header portion of the control, the containing
>window gets called for double click.
>
>Is there anyway to ignore double clicks on the
>listview header and do the call back only when
>double clicking on an item?
>  
>
Tom, thanks for the bug report.  I have fixed it and will include it in 
the next version of FXListview.  If you need the bug fix immediately, 
send me an email and I can get the fix to you ASAP.

Jamey

On Wed, 14 Apr 2004 16:18:40 -0400, "Jens Wessling" <wes...@so...>
wrote :

> I am using several listboxes, but when I select an item from one listbox,
> often another listbox will de-select.  Why?  How do I make all of the
> listboxes stay selected?

Are all of the listboxes are hooked up to the same target object (perhaps
the same data target)? That's what it sounds like. Other than that, there's
no reason (and indeed no way) that separate listboxes would have any control
over each other.

2003	Jan	Feb	Mar	Apr	May	Jun (75)	Jul (90)	Aug (61)	Sep (56)	Oct (56)	Nov (39)	Dec (83)
2004	Jan (56)	Feb (45)	Mar (61)	Apr (40)	May (95)	Jun (79)	Jul (63)	Aug	Sep (4)	Oct	Nov	Dec

fxruby-users Mailing List for FXRuby (Page 10)

fxruby-users — General-purpose discussion list for FXRuby