Alright, arleady done that.
I will stick to this idea.
Thanks :)
-
П.П. Избра ли вече име за твоя сайт? Хайде, пазим място за него!Ела на
www.superhosting.bg и вземи с до –50% отстъпка!
https://www.superhosting.bg/promo/webhosting?utm_source=mail.bg&utm_
The point of using the container as a placeholder is to eliminate the
deletion of the entire tab.
You create each tab with a container as its child, and then add() your
child to the tab's container rather than directly to the tab. When you
later remove() your child and add() it to a different
I will still need to do a lot of expensive work to remove add and
reconfigure all the child widgets (which are a lot), also
I will need to be doing even more work to define the switch-tab behavior,
which will involve keeping track of the latest tab content (to know where
to remove the child widg
Why not make the tab's child a GtkContainer, then change the contents of
the container with remove()/add()?
On 01/30/2018 10:17 AM, psp...@mail.bg wrote:
I am making a text editor in GTK, whereas each new file is loaded into a
new tab.
I don't want to create and initialize the same content
I am making a text editor in GTK, whereas each new file is loaded into a
new tab.
I don't want to create and initialize the same content (which happens to be
huge) over again on all tabs (especially since only a GtkTextBuffer is to
be different), so I decided to use gtk_notebook_detach_tab() t
