On 10/11/2018 8:09 PM, Jeyron A.C wrote:
Hello. Receive a greeting from me.
To tell the truth I need someone who knows in general how to work the
interface in rackert, in my case what I would like to explain to me is
how to efficiently use the menubar in racket. The idea is to create a
menubar (which I already did) and that it calls different windows and
that the main window closes and opens the next window, just as if in
the next window it can be closed and call back to the principal. The
problem is that I am having errors when calling those other windows,
since the menubar, when I have an item, I can not call the next window.
In the same way I would like to know if it is possible to go sailing
from window to window. In other words, to close and open new windows.
Call others etc.
Beforehand I appreciate the help and information. Thanks group!
Closing the main window normally causes the program to exit ... likely
the source of your problem. You can hide the main window instead of
closing it, but that makes handling the main window a special case. Or
you can hide the main window from the start and move from child to child
via controls in the child windows. But either situation makes for an
What you (seem to) want to do is quite different from how an application
typically would be structured. Normally the main window stays open
(visible), and menu choices either cause other (child) windows to be
opened or cause actions to be performed within the open window(s). A
menu in window X can perform an action in window Y [there is no
restriction to the window containing the menu], and child windows can
have their own menus. But you would normally either close a child to
return to the parent window, or (if the windows logically should be
considered peers, or floating control panels) you would leave the child
open and go [back] to the main window simply by clicking on (activating) it.
[There are some few applications that use the peer window approach. A
somewhat larger percentage do use persistent child windows as floating
control panels. But the vast majority use the obvious parent/child
structure, open children temporarily for some operation and close them
when the operation is finished (while the main window remains open).]
May I ask what is the use case?
You received this message because you are subscribed to the Google Groups "Racket
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.