>
> When using Glade is it safe to repeatedly modify GUI windows and dialogs if
> application specific C code has been added?
If you don't modify any file with a message at the top telling you that
glade will regenerate the file then you should be pretty safe. IIRC there is
a check box in the project options in glade to keep it from over-writing
the main.c file.
Caveat: sometimes the code that adds to the callbacks.[ch]
files will insert extra function decl/defn's at the bottom. For example you
hook foo() up to the clicked signal on widget A, generate code,
edit the callback and otherwise go about your life. Later hook the same foo()
up to widget B and when you generate code an extra foo() decl and defn will
be added. The new ones are added at the bottom of the file so removing them
is easy.
If you are doing a LOT of edit/rebuild cycles without changing much in the way
of code you have added, then you might want to consider using libglade. It
may be used to create the widgets by reading the glade file in at runtime
instead of creating it via interface.c function calls.
> Where should the application specific C code be placed to prevent it from
> being modified or destroyed by later GUI builds? Or, should I make sure the
> GUI is close as possible to the final version and do manual modifications
> from that point on?
>
> Thanks in advance,
> WW
>
>
>
> +---------------------------------------------------------------------+
> To unsubscribe from this list, send a message to [EMAIL PROTECTED]
> with the line "unsubscribe glade-devel" in the body of the message.
>
+---------------------------------------------------------------------+
To unsubscribe from this list, send a message to [EMAIL PROTECTED]
with the line "unsubscribe glade-devel" in the body of the message.
