Can a Screen Be Resized by Code?

[Qwerkey]

After posting my updated Pelmanism Game in the regular Programs section, I realised that I could have made that an InForm game - would give it a more professional look.  But I would need to have three different screen sizes, and in InForm we are resricted to the Screen created by the UiEditor and we can, of course, only have the one screen.  If we could write some code which changed the Screen X- and Y- widths, that would do I think.  A User can do this with $RESIZE and _RESIZEWIDTH etc, but could the screen width/height be set by code commands?  From the Wiki, I think not.  A pity.

[FellippeHeitor]

Control(__UI_FormID).Width = (whatever width suits you)
Control(__UI_FormID).Height = (whatever height suits you)

Alternatively you can set a form's CanResize property to true so the user can freely resize the form. That will trigger the __UI_FormResize event from which you can adapt your interface according to the resulting Control(__UI_FormID).Width and Control(__UI_FormID).Height.

[Qwerkey]

Oh great!  That's mapped out my next project.

[Pete]

So when is the Inform WIKI going to go live? Don't you have a Clippy equivalent in Brazil? Maybe Senior Quippy?

You're living my dream of customization ability in programs. I've only written a handful of libraries that allow for easy changes like that.

Pete

[FellippeHeitor]

Bam: https://github.com/FellippeHeitor/InForm/wiki

As old as the project itself ;-)

[FellippeHeitor]

You're living my dream of customization ability in programs. I've only written a handful of libraries that allow for easy changes like that.

Pete

It's a project I'm really proud of :-)

[Qwerkey]

As one who has coded some InForm projects, I can attest that the InForm wiki was a great resource.  Fellippe, please do feel proud.

(And I only needed the tiniest amount of Fellippe's additional help to get going - probably not the most correct usage of the superlative of tiny!).

[Pete]

Nice job on the WIKI, too!

We don't need o stinkin' Quippy!

Pete :D

[Qwerkey]

Fellippe, I've started on Pelmanism InForm.  I've created a starting Form of a certain size, which will get resized (larger and smaller) during the program execution.  Will there be a problem if the Form size shrinks so that some of the controls are temporarily outside the new Form limits, or shall I have to temporarliy move everything inside the smaller Form?

[FellippeHeitor]

If they won't be needed when the form is smaller they can remain hidden, no problem. You may want to set their .Disabled property to True temporarily to prevent them from gaining focus if your user navigates the interface using Tab.

[Qwerkey]

Fellippe, I'm most of the way to preparing the InForm version of my Pelmanism program.  However, it is prone to crashing, either at compilation or some way through when running (unpredictable).  When you have some spare time, could you take a look?  I'm now using the 64-bit version of QB64 - could that be a problem?  Thanks, Richard

https://www.dropbox.com/s/p3oeqa30ytdq0qp/Pelmanism%20InForm.zip?dl=1

[FellippeHeitor]

I'll have a look at your code.

Edit: Just ran it with no issues, compiled with QB64 32bit (btw: flip card times are slooooooooooow). Could you confirm you also get these crashes using the 32bit version of QB64? There are quite a few API calls when InForm is running under Windows, and eventual crashing could be related to that.

[Qwerkey]

Fellippe, thanks for feedback.  Copied my project folder back to QB64 (32-bit) - how long ago that seems! - and initially got Crash Divide by Zero fails every time I clicked on "New Game".  Found out that this was due to _SCREENMOVE statements (I has wanted to reposition the screen for different window sizes).  With the _SCREENMOVE lines commented out, it looks like the 32-bit version runs OK, and I've doubled the speed of the turnovers (I'd made the game deliberately lazy).  The 64-bit version still crashes unreliably at any time.

There are quite a few API calls when InForm is running under Windows

No idea what an API call is: another gaping hole in my knowledge - if Steve stumbles across this post, he'll probably give me another large dose of tuition!  I'll just keep taking those tablets of wisdom.

[FellippeHeitor]

No idea what an API call is: another gaping hole in my knowledge - if Steve stumbles across this post, he'll probably give me another large dose of tuition!  I'll just keep taking those tablets of wisdom.

https://en.wikipedia.org/wiki/Application_programming_interface

When you use a system function Windows makes available via DLLs. The reason why we have http://www.qb64.org/wiki/DECLARE_DYNAMIC_LIBRARY

[Qwerkey]

With the _SCREENMOVE lines commented out, it looks like the 32-bit version runs OK

Oh, by the way, is there an InForm equivalent of _SCREENMOVE which I can use in the running code?  Clearly InForm doesn't like _SCREENMOVE after UI_OnLoad.