LablTk

LablTk

[Fabien Fleutot]

I have two problems with LablTk :

- I want to prevent a window from being destroyed by the WM : it's a
pretty long to build window, and I'd like to hide it instead of actually
destroy it when the user clicks on the delete button of the window
manager. It's easy to do in some langages such as Java, but I can't find
the way to do it with Labltk.

- I want to use a button to destroy a window. But I can't do

Button.create win ~text:"Close" ~command:(fun _ -> destroy win)

since when the destroy function starts, the button, which belongs to
win, is in use and prevents to destroy its parent win. There is a
specific function (i.e. Tk_EventuallyFree) in Tcl/Tk to handle such
cases, but I don't know how to do with LablTk. What I'm currently doing
is to put the destroying function in a Timer callback, to destroy the
window .1s after the button has been released, but it's not very safe...

Re: LablTk

[Jacques Garrigue]

From: Fabien Fleutot <fabien.fleutot@inria.fr>

> I have two problems with LablTk :
> 
> - I want to prevent a window from being destroyed by the WM : it's a
> pretty long to build window, and I'd like to hide it instead of actually
> destroy it when the user clicks on the delete button of the window
> manager. It's easy to do in some langages such as Java, but I can't find
> the way to do it with Labltk.

I do not see anything to do that in Tcl/Tk. You can iconify a window,
using Wm.iconify, but not hide it.
If you really need this kind of power, you may consider switching to
GTK.

> - I want to use a button to destroy a window. But I can't do
> 
> Button.create win ~text:"Close" ~command:(fun _ -> destroy win)
> 
> since when the destroy function starts, the button, which belongs to
> win, is in use and prevents to destroy its parent win. There is a
> specific function (i.e. Tk_EventuallyFree) in Tcl/Tk to handle such
> cases, but I don't know how to do with LablTk. What I'm currently doing
> is to put the destroying function in a Timer callback, to destroy the
> window .1s after the button has been released, but it's not very safe...

I don't see why your above code wouldn't work. I'm doing it everywhere in
ocamlbrowser (Jg_button.create_destroyer).

        Jacques
---------------------------------------------------------------------------
Jacques Garrigue      Kyoto University     garrigue at kurims.kyoto-u.ac.jp
		<A HREF=http://wwwfun.kurims.kyoto-u.ac.jp/~garrigue/>JG</A>

Re: LablTk

[Fabien Fleutot]

   > - I want to prevent a window from being destroyed by the WM : it's a
   > pretty long to build window, and I'd like to hide it instead of actually
   > destroy it when the user clicks on the delete button of the window
   > manager. It's easy to do in some langages such as Java, but I can't find
   > the way to do it with Labltk.

   I do not see anything to do that in Tcl/Tk. You can iconify a window,
   using Wm.iconify, but not hide it.

One can do it with ``Wm.withdraw''. This function exists in Labltk; the problem
is to say it to use my own function rather than the standard delete function
when the window destruction is requested by the Wm.

   If you really need this kind of power, you may consider switching to
   GTK.

...as soon as it will be included in the standard OCaml distribution: I don't
want people to have to download and install dozens of libs before being able to
compile my soft, esp. on platforms other than linux.

Re: LablTk

[Jacques Garrigue]

From: Fabien Fleutot <fabien.fleutot@inria.fr>

>    > - I want to prevent a window from being destroyed by the WM : it's a
>    > pretty long to build window, and I'd like to hide it instead of actually
>    > destroy it when the user clicks on the delete button of the window
>    > manager. It's easy to do in some langages such as Java, but I can't find
>    > the way to do it with Labltk.
> 
>    I do not see anything to do that in Tcl/Tk. You can iconify a window,
>    using Wm.iconify, but not hide it.
> 
> One can do it with ``Wm.withdraw''. This function exists in Labltk;
> the problem is to say it to use my own function rather than the
> standard delete function when the window destruction is requested by
> the Wm.

My mistake.
So your problem is how to bind the Destroy event, avoiding its actual
execution. And I don't know how it can be done; break does not work in
that specific case. Strangely enough, the window is only destroyed
after the script was executed, which gives you time to say to the user
that he has done something wrong, but there is no way to stop it.
Actually I would like to know, since I have uses for it.

>    If you really need this kind of power, you may consider switching to
>    GTK.
>
> ...as soon as it will be included in the standard OCaml
> distribution: I don't want people to have to download and install
> dozens of libs before being able to compile my soft, esp. on
> platforms other than linux.

Then you will have to stick to Tk, which is available on most platforms.
Having moving APIs in the standard distribution does not sound nice, and
LablGTK's API is not stable yet.

---------------------------------------------------------------------------
Jacques Garrigue      Kyoto University     garrigue at kurims.kyoto-u.ac.jp
		<A HREF=http://wwwfun.kurims.kyoto-u.ac.jp/~garrigue/>JG</A>

Re: LablTk

[Axel Poigné]

Jacques Garrigue wrote:
> 
> From: Fabien Fleutot <fabien.fleutot@inria.fr>
> 
> > I have two problems with LablTk :
> >
> > - I want to prevent a window from being destroyed by the WM : it's a
> > pretty long to build window, and I'd like to hide it instead of actually
> > destroy it when the user clicks on the delete button of the window
> > manager. It's easy to do in some langages such as Java, but I can't find
> > the way to do it with Labltk.
> 
> I do not see anything to do that in Tcl/Tk. You can iconify a window,
> using Wm.iconify, but not hide it.

You hide it by moving the window somewhere outside of the screen.

Axel poigne

LablTk

[wester]

Hi, 

I would like to use LablTk together with Bigarrays in the toplevel. 
Can I make my own toplevel with both modules linked in? I know
how to make it for Bigarrays alone and I know that labltk.exe (Windows)
is the toplevel with LablTk already linked in. But I couldn't figure out
how to make a toplevel with both Bigarrays and LablTk.

Besides this I couldn't find information about the modules Imagebitmap 
and Imagephoto which might be interesting for me. I have Ousterhouts 
Tcl/Tk book but couldn't find anything about this two modules.

I'have read that float arrays aren't boxed. Does this also hold for integers?
Considering speed are Bigarrays preferable? 

I would be very appreciative for any answers to my questions. 

I'm working on a project where I have to develop software for image 
processing and pattern recognition. I considered to make this in C++ or Java
because I'm quite familiar with these languages and graphical output can quite 
easily be done with both. On the other hand I like OCaml's toplevel because it makes
rapid prototyping very easy and I also would like to learn OCaml in order to
extend my programming skills. But the project has to be executed succesfully,
so I'm still undecided. 

Thank you in advance.

With kind regards.

Rolf Wester   

-------------------------------------
Rolf Wester
wester@ilt.fhg.de

Re: LablTk

[Jacques Garrigue]

From: wester@ilt.fhg.de

> I would like to use LablTk together with Bigarrays in the toplevel. 
> Can I make my own toplevel with both modules linked in? I know
> how to make it for Bigarrays alone and I know that labltk.exe (Windows)
> is the toplevel with LablTk already linked in. But I couldn't figure out
> how to make a toplevel with both Bigarrays and LablTk.

This is just the standard way, but you have to write the labltk path:
     ocamlmktop -o ocamlbigtk bigarray.cma -I /ocaml/lib/labltk labltk.cma

> Besides this I couldn't find information about the modules Imagebitmap 
> and Imagephoto which might be interesting for me. I have Ousterhouts 
> Tcl/Tk book but couldn't find anything about this two modules.

They are different types of images. You should get info under the
image, bitmap and photo names.

> I'have read that float arrays aren't boxed. Does this also hold for integers?
> Considering speed are Bigarrays preferable? 

Not my speciality, but if I remember correctly, not only integer
arrays are unboxed (no reason to box integers anywhere), but to get
the best efficiency you must use Array.unsafe_get, and tell the
compiler that your array contains integers (arr : int array), if it
cannot infer it.

Cheers,

Jacques
---------------------------------------------------------------------------
Jacques Garrigue      Kyoto University     garrigue at kurims.kyoto-u.ac.jp
		<A HREF=http://wwwfun.kurims.kyoto-u.ac.jp/~garrigue/>JG</A>