El jueves, 11 de octubre de 2018, 19:07:04 (UTC-6), gneuner2 escribió: > > > 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 > atypical application. > > 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? > > George >
Ok I understand that part of wanting to close the windows. And the truth is that I do not need to complicate myself so much. Even so I have another doubt, and it is like using the menu bar in a simple and useful way. I have my code: (define menu-volunteers (new menu% [label "& Volunteers"] [parent menu-bar])) (define my_item_agregar_volun (new menu-item% [label "& Add"] [parent menu-volunteers] "Here goes the callback" )) Exactly where the callback goes, is where I have that big doubt. That has to go in that section. The idea is to call a new window where you can add data, which are necessary. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.