And another thing...
Adding Controls to Existing Project
(...) your program automatically adds the new one to the DIM SHARED declarations.
I've made a choice to not try to mess with user's custom code when editing an existing project.
You see, the SELECT CASE blocks added when a project is first saved isn't really required. The user can manipulate the id that is received by the event sub in a many other ways. I could have tried to scan the existing code for the proper spot and then inject the new control, but it didn't feel worth the hassle.
All that considered I hope the message below (consider only what's in quotes) did show up in your edited .bas file after saving, along with the new DIM SHARED line:Code: QB64: [Select]
PRINT #TextFileNum, "': ---------------------------------------------------------------------------------"
If it didn't, that probably means you had previously removed the line that said:Code: QB64: [Select]
': External modules: ---------------------------------------------------------------
And you can see how hard it'd be to predict how to alter someone else's code programmatically.
Ah, Fellippe, I think that I have managed to fall at the first hurdle.
The program which I am creating requires _MAPTRIANGLE (3D) - at least I had hoped to do it with _MAPTRIANGLE (3D). But we found from Petr the other day that _MAPTRIANGLE (3D) requires hardware imaging. And we found yesterday that InForm images into a PictureBox must be software. I have verified this in my trial program: _MAPTRIANGLE (3D) does not work with InForm.
The program I'm creating is an updated version of an old SDL program of a general gravitation simulation. In that original program, I used my own method to convert the 3D coordinates into the 2D screen dimensions. It looks as if I'll have to use that method here - rather a pity as I had wanted to remove the conversion routine away from the calculations routine.
Your users always come up with impossible requirements.
Richard
A while back user Unseen Machine did some hacks to his local copy of InForm to be able to use OpenGL 3D statements in an InForm program. It was quite cool. I assume it could allow using hardware images as you need to.
It could also be something else entirely, and I'll be glad to investigate, but maybe he can come along and remind us what tweaks were required.