When you create an internal library, and “attach” it to your application, it attaches all the functions in that library to the bottom of each page of generated code.
So if you have to make a change to a function , you then have to regenerate each page that uses it.
Why can’t it work like a true Include page, where it looks to that page to find the function and run it.
The way it works now is a waste of space and time.
It’s a good suggestion. I use to do this way: When I change an internal library, I use the Generate source code In Project menu, and it takes all outdated applications in order to compile all of them.