🚀 go-pugleaf

The resource question asked lately reminded me of a problem (bug ?)
I had encountered using GEM, about a year or longer ago.

Using the resource functions (notably rsrc_load(), rsrc_gaddr(),
rsrc_free()) I can load resources that, for instance, contain object
trees like  forms and menus.  Nice.

Using fsel_input() I have a standard way for the user to search and
specify a pathname (directory and filename). Also nice.

But trying to use both in the same program failed; when an fsel_input()
was done after a rsrc_load() the resource tree contained garbage.
It looks as if fsel_input() uses the rsrc_load() function itself, and
since a program can only have one resource file loaded at a time (am I
correct ?), it put its own resource on top of mine.

I worked around it by saving the relevant data (button states) and
restoring them after the fsel_input() and a new rsrc_load(), but it
didn't seem very nice to me (having to reread the resource file, saving
/ restoring states etc.).

Anyone familiar with this particular problem? Is it a known bug /
restriction?  Any chance for it to get fixed in a new GEM version?

			  Leo.