From: kong y. <ko...@vi...> - 2000-08-22 05:22:33
|
subscribe |
From: Glen C. <gl...@ca...> - 2000-11-22 03:58:45
|
subscribe -- Sign here X______________________ |
From: Dr. G. T. <gt...@sc...> - 2000-12-22 10:46:39
|
confirm 496573 |
From: ADY J. <jo...@eu...> - 2001-01-10 13:59:25
|
subscribe |
From: Luciano <dre...@ho...> - 2001-01-24 10:00:33
|
From: Dan P. <da...@ee...> - 2001-02-08 18:25:01
|
subscribe |
From: Rui F. <Rui...@cl...> - 2001-03-21 02:03:38
|
Hello. Is it possible to have right click even in TabBook Item? I tried to substitute SEL_COMMAND with SEL_RIGHTBUTTONPRESS in the = TabBook Sample but the event is trigered when pointing outside the tabs. How can I have right click even on the tabs? Thanks |
From: Anthony B. <ab...@ub...> - 2001-03-22 07:32:50
|
subscribe |
From: Rarkov <gaz...@vi...> - 2001-03-22 13:21:41
|
subscribe |
From: Shinichiro H. <hi...@ge...> - 2001-04-25 02:44:42
|
subscribe |
From: John B. <jo...@su...> - 2001-05-11 22:10:09
|
Hi. I've been trying to compile FOX using mingw and Cygwin. run through the instructions up and have had success in compiling up until this point: In file included from /usr/include/jpeglib.h:26, from fxjpegio.cpp:53: /usr/include/jmorecfg.h:222: conflicting types for `typedef long int INT32' /usr/include/w32api/basetsd.h:8: previous declaration as `typedef int INT32' make[1]: *** [fxjpegio.lo] Error 1 make: *** [all-recursive] Error 1 Can somebody tell me what to do to get FOX to continue compiling? Thanks. |
From: Lyle J. <ljo...@re...> - 2001-05-14 14:15:51
|
> Hi. I've been trying to compile FOX using mingw and Cygwin. run through > the instructions up and have had success in compiling up until this point: > > In file included from /usr/include/jpeglib.h:26, > from fxjpegio.cpp:53: > /usr/include/jmorecfg.h:222: conflicting types for `typedef long > int INT32' > /usr/include/w32api/basetsd.h:8: previous declaration as `typedef > int INT32' > make[1]: *** [fxjpegio.lo] Error 1 > make: *** [all-recursive] Error 1 > > Can somebody tell me what to do to get FOX to continue compiling? Yes, this is an unfortunate error in the JPEG sources (it has nothing to do with FOX). It has been reported but don't hold your breath waiting for a fix ;) The quickest fix I've found is to just comment out that line in jmorecfg.h. |
From: Panagiotis A. <ap...@th...> - 2001-05-23 13:02:40
|
I am an EiffelFox user, and i tried to compile the scribble example. The EiffelFox scribble program is a direct Eiffel conversion of the Fox C++ test program. Both versions have the same behavior. I noticed that whenever a paint event is triggered, the rectangle that is specified by the paint event is repainted to the color of the background. This means that if you have painted something on the canvas and you place another window on the canvas surface, the rectangle that is considered to be dirty is repainted. In this way the drawn figure is lost. Is it possible to store the information ( data bits ) that are represented on the canvas in order to refresh the canvas by using the saved information as the source of repainting ? Panagiotis Arapakis |
From: Lyle J. <ljo...@re...> - 2001-05-23 13:54:09
|
> I am an EiffelFox user, and i tried to compile the scribble > example. The EiffelFox scribble > program is a direct Eiffel conversion of the Fox C++ test > program. Both versions have the > same behavior. > I noticed that whenever a paint event is triggered, the rectangle > that is specified by the paint > event is repainted to the color of the background. This means > that if you have painted > something on the canvas and you place another window on the > canvas surface, the rectangle > that is considered to be dirty is repainted. In this way the > drawn figure is lost. > Is it possible to store the information ( data bits ) that are > represented on the canvas in order > to refresh the canvas by using the saved information as the > source of repainting ? I haven't worked with the EiffelFox bindings, but generally speaking you have at least a couple of options: 1. Instead of drawing directly into the FXCanvas, draw into an offscreen buffer (i.e. an FXImage object that is the same size as your canvas) and then copy that image to the canvas using FXDC::drawImage(). 2. As you draw a new line segment during a mouse motion event, save its coordinates in a list of some kind so that you can programmatically reproduce the drawing later by looping over the segments in that list and calling FXDC::drawLine(). Hope this helps, Lyle |
From: Jeroen <jv...@cf...> - 2001-05-23 14:08:14
|
On Wednesday 23 May 2001 08:02, you wrote: > I am an EiffelFox user, and i tried to compile the scribble example. The > EiffelFox scribble program is a direct Eiffel conversion of the Fox C++ > test program. Both versions have the same behavior. > I noticed that whenever a paint event is triggered, the rectangle that is > specified by the paint event is repainted to the color of the background. > This means that if you have painted something on the canvas and you place > another window on the canvas surface, the rectangle that is considered to > be dirty is repainted. In this way the drawn figure is lost. Is it possible > to store the information ( data bits ) that are represented on the canvas > in order to refresh the canvas by using the saved information as the source > of repainting ? > > Panagiotis Arapakis Scribble was meant to be a very simple example. If you actually want to make a paint program (and I highly encourage that!) then you'd want to draw into an offscreen FXImage. There are a couple of advantages: 1) Whenever the window is clobbered you can simply BLIT the image back. 2) FXImage has facility to read back the pixels into a client-side buffer, after which this can be saved to a variety of imagefile formats. Currently, FOX supports GIF, BMP, PCX, JPEG, PNG, XPM image formats. There are tentative plans to add TIFF and PPM (the latter because its so easy I have no excuse not to, and PPM can be piped into the pbm utilitis for the more esoteric formats). - Jeroen -- +-------------------------------+--------------------------------------------+ | E-Mail : jv...@cf... | The FOX Platform Independent GUI Toolkit: | | USMail : 215 Wynn Drive, | | | Huntsville, AL 35805 | Official Site: | | Phone : (256) 726-4820 | http://www.cfdrc.com/FOX/fox.html | | Fax : (256) 726-4806 | ftp://ftp.cfdrc.com/pub/FOX | | WWW : http://www.cfdrc.com | | +-------------------------------+--------------------------------------------+ | Copyright (C) 07:20 05/23/2001 Jeroen van der Zijp. All Rights Reserved. | +----------------------------------------------------------------------------+ |
From: Hartmut S. <har...@fi...> - 2001-06-20 23:39:08
|
I have the following problem: I want to show a dialog with a FXIconList and 3 editable text fields: /-----------------------------------------/ / Name | Company | Age / /-----------------------------------------/ / xxxx xxx xxxx / / xxxx xxx xxxx / / xxxx xxx xxxx / / xxxx xxx xxxx / /-----------------------------------------/ Name: ------------------------- Company: --------------------- Age: --------------------- The text fields always shows the values of the current item of FXIconList. So you can edit these. But how can i catch an error. The validity of the text fields should be checked when the dialog is closed or the current item in the list is moved. So i tried to catch SEL_CHANGED from the list and do the checking in my handler. If something went wrong i display a message and want to set the current item back to the old value. That's not working. So shouldn't this changed so that we can call "setCurrentItem" from a SEL_CHANGED handler ? (I have workaround and set a chore in which i do the things, i normally want to do in the handler. But thats not very nice.) Is there any rule about the actions that you can do inside a handler. TK for examples has a lot of code to minimize those side effects. Calling the destructor seems also a bad idea in a handler. Perhaps someone who knows more about this can write a few lines on the FAQ or the FOX tutorial page. ______________________________________________________ http://firemail.fireball.de - Ihr Briefkasten im Web. Einfach, schnell, sicher. |
From: FOX D. <dev...@fo...> - 2001-06-22 02:49:04
|
On Wednesday 20 June 2001 18:38, you wrote: > I have the following problem: > I want to show a dialog with a FXIconList and > 3 editable text fields: > > /-----------------------------------------/ > / Name | Company | Age / > /-----------------------------------------/ > / xxxx xxx xxxx / > / xxxx xxx xxxx / > / xxxx xxx xxxx / > / xxxx xxx xxxx / > /-----------------------------------------/ > > Name: ------------------------- > Company: --------------------- > Age: --------------------- > > > The text fields always shows the values > of the current item of FXIconList. > So you can edit these. > > But how can i catch an error. The validity > of the text fields should be checked when > the dialog is closed or the current item in > the list is moved. > So i tried to catch SEL_CHANGED from the list > and do the checking in my handler. If something > went wrong i display a message and want to > set the current item back to the old value. > > That's not working. > So shouldn't this changed so that we can call > "setCurrentItem" from a SEL_CHANGED handler ? I suggest using SEL_UPDATE, which is more or less made for this situation:- updating the widget so its reflecting the state of the application. Calling setCurrentItem() from withing SEL_CHANGED could lead to infinite recursion, esp. because setCurrentItem optionally generates another SEL_CHANGED ..... I have not gone over all widgets to determine whether what you want is safe or not; for that reason I would recommend against it. Note the SEL_UPDATE mechanism is OK because SEL_UPDATE messages are not being sent during interaction with the widget. > (I have workaround and set a chore in which i > do the things, i normally want to do in the > handler. But thats not very nice.) > > Is there any rule about the actions that you > can do inside a handler. TK for examples has > a lot of code to minimize those side effects. > Calling the destructor seems also a bad idea > in a handler. Most things are safe when handling SEL_COMMAND; low level handlers like SEL_LEFTBUTTONPRESS are more picky about what can be done. > Perhaps someone who knows more about this > can write a few lines on the FAQ or the FOX > tutorial page. In Motif, it was very easy to get into a mutual recursion situation; I fixed that (to the extent possible) by a simple rule: when you programmatically change the state of a widget, no callbacks are generated (unless explicitly enabled by passing notify=TRUE); only when the user manipulates something do you get a callback message. This makes it very easy for one widget to change another and vice versa. Hope this helps, Jeroen |
From: root <ro...@fi...> - 2001-06-26 16:15:41
|
test |
From: Christian U. <Chr...@al...> - 2001-06-29 15:51:57
Attachments:
Christian.Uhrig.vcf
|
subscribe |
From: Jeroen <jv...@cf...> - 2001-07-05 18:51:17
|
subscribe |
From: Igor <ish...@ya...> - 2001-07-05 19:10:58
|
How to catch SEL_LEFTBUTTONPRESS message for FXOptionMenu? I need to do some validation every time user is trying to change the menu selection. Thanks __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail http://personal.mail.yahoo.com/ |
From: Josua G. <fra...@gm...> - 2001-08-19 17:09:51
|
unsubscribe |
From: Elbers, H.P. <H.P...@bo...> - 2001-08-28 07:38:47
|
Hi, When using FRAME_LINE only the left and top sides of the frame are drawn. Is this intentional? example: new FXLabel(this, "Hello", 0, FRAME_LINE); Context: fox 174 on linux -- Hans elbers Work: h.p.elbers<AT>boskalis.nl Home: elbers<AT>dsv.nl |
From: Jeroen <jv...@cf...> - 2001-08-28 14:55:55
|
On Tuesday 28 August 2001 02:35, you wrote: > Hi, > > When using FRAME_LINE only the left and top sides of the frame are drawn. > Is this intentional? > > example: new FXLabel(this, "Hello", 0, FRAME_LINE); > > Context: fox 174 on linux You're right, it was off by one in width/height. I fixed it. Thanks, - Jeroen -- +-------------------------------+--------------------------------------------+ | E-Mail : jv...@cf... | The FOX Platform Independent GUI Toolkit: | | USMail : 215 Wynn Drive, | | | Huntsville, AL 35805 | Official Site: | | Phone : (256) 726-4820 | http://www.fox-toolkit.org | | Fax : (256) 726-4806 | ftp://ftp.fox-toolkit.org/pub | | WWW : http://www.cfdrc.com | | +-------------------------------+--------------------------------------------+ | Copyright (C) 09:40 08/28/2001 Jeroen van der Zijp. All Rights Reserved. | +----------------------------------------------------------------------------+ |
From: Tait, R. <Rog...@ia...> - 2001-09-04 11:29:52
|
Hello I am new to FOX and I wonder if anyone can help me? To pratice my skills I have implemented both a parent and a child window, each window consists of a single spinner. Can anyone tell me how I can continuously update the spinner in the child window to match the value shown by the spinner in the parent window. At present both spinners consist of independant FXDataTarget's that are public: data memebers of each class. Where do I start? Thanks Roger FXIMPLEMENT(FXChildWindow,FXTopWindow,NULL,0) FXChildWindow::FXChildWindow(FXWindow* owner):FXTopWindow(owner,"Child Window",NULL,NULL,DECOR_ALL,0,0,0,0,0,0) { child_int = 0; new FXLabel(this,"Child Window",NULL,LAYOUT_TOP|JUSTIFY_LEFT); child_target = new FXDataTarget(child_int); FXMatrix* matrix=new FXMatrix(this,2,FRAME_RAISED|LAYOUT_TOP|LAYOUT_FILL_X|LAYOUT_FILL_Y); child_spinner = new FXSpinner(matrix,5,child_target,FXDataTarget::ID_VALUE,FRAME_SUNKEN|FRAME_TH ICK|LAYOUT_CENTER_Y|LAYOUT_FILL_ROW); child_spinner->setMinMax(0,35); } FXDEFMAP(FXParentWindow) FXParentWindowMap[]= { FXMAPFUNC(SEL_COMMAND, FXParentWindow::ID_SHOWCHILD, FXParentWindow::onCmdShowDialog), }; FXIMPLEMENT(FXParentWindow,FXMainWindow,FXParentWindowMap,ARRAYNUMBER(FXPare ntWindowMap)) FXParentWindow::FXParentWindow(FXApp* a):FXMainWindow(a,"Parent Window",NULL,NULL,DECOR_ALL,0,0,0,0) { parent_int = 0; child=new FXChildWindow(this); parent_target = new FXDataTarget(parent_int); FXMatrix* matrix=new FXMatrix(this,3,FRAME_RAISED|LAYOUT_TOP|LAYOUT_FILL_X|LAYOUT_FILL_Y); new FXLabel(matrix,"Parent Window",NULL,LAYOUT_TOP|JUSTIFY_LEFT); new FXButton(matrix,"Child Window",NULL,this,ID_SHOWCHILD,FRAME_RAISED|FRAME_THICK|LAYOUT_CENTER_X|LAYO UT_CENTER_Y); parent_spinner = new FXSpinner(matrix,5,parent_target,FXDataTarget::ID_VALUE,FRAME_SUNKEN|FRAME_T HICK|LAYOUT_CENTER_Y|LAYOUT_FILL_ROW); parent_spinner->setMinMax(0,35); } |