InForm-PE

[TempodiBasic]

@KernelPanic
Hey man


this is what I get running the code posted at #119

If you follow my tips you'll get the same working calculation. The screenshot shows you also the only effective needed code!

About Aligning the output text on the right side of Textbox, I think you must manage it by your own with some code .
The Align and VAlign properties seem to be actvite only for Label control. So you must type your Format$ function by yourself !

[coder2999]

Is it possible to add a multi-line text box?

First of all, I'm very grateful for the author's work. This tool makes it easy for Windows developers to develop simple applications on macOS.

However, I've noticed that InForm-PE lacks a crucial multi-line text box control, preventing me from displaying large amounts of text in my application.

Therefore, I hope the author can add this functionality.

Thanks in advance.

[bplus]

I've successfully used a list box with associated string array to display multi-line text.

   

[TempodiBasic]

@coder9999
a multiline textbox control...
@Bplus shows you an excellent use of Listbox + string array
while here you  can see a my little workaround to show content of a source file code by using a Picturebox QB64pe SpeedBible.

But Have you tried an array of textboxes with invisible borders?

[TempodiBasic]

here a screenshot of a set of Textboxes 
as you can see  no escape sequence and no ASCII sequence  are managed for getting a CR/LF.
If you would show text in multiple lines , first you must project the printout area (area of output) and then fit it with textboxes.
At the end you assign a single line of text to each textbox.
 If you like to manage by code this set of textboxes, you need to create an array of textboxes so you can access in code using an index, otherwise you should build a fill_set_of_Textboxes with argument an array of text to assign them for output.
Well, if it is only an output show and not an editor, you should also manage the editing mode of textboxes...
It could be better to build a multiline text output area by yourself and showing it in a picturebox.






all these words for saying that Informpe is a RAD application with an engine for event driven coding model, but there is no object coding under the wood.
You cannot hope to do OOP with Informpe. Moreover you cannot substitute  method/procedure for changing the behaviour of components (NO override), you cannot make a copy of  a component and add new features or modify/delete original features, you cannot make a new component and add it to the original components for using in Informpe application. 
For example in my QB64pe SpeedBible application I had had to use a trick workaround to hack the Informpe engine and let Picturebox react to Keyboard input.
So at the end of this post it must be clear that Informpe is a Modular RAD application with engine projected for managing events of original components.

It is clear that they are components and no objects because no OOP here. I'm stressing this idea because I often see coders coming in touch with Informpe and working as it was VB of Microsoft. And after some times they claim Informpe doesn't work.
Yes it doesn't work like VB cause it is a MODULAR CODE Event driven engine with a RAD interface named UiEditor.

[PeebzNL]

Hi, I'm new here.

Just installed qb64pe (v4.2.0) on my MacBook Pro (M1, Sequoia 15.5), seems to work ok.
After that, downloaded (GitHub) and installed Inform-PE according to instruction. Compiling ok, no errors.

Starting UiEditor generates an error: libc++abi: terminating due to uncaught exception of type std::length_error: basic_string 
Recompiling didn't make a difference.

Any clues?

[TempodiBasic]

we need MAC users here! 

@PeebzNL
if you have problems also compiling .BAS within QB64pe you could find a solution here https://qb64phoenix.com/qb64wiki/index.p...nux,_macOS?
Q number 4

[Giano]

Hi, I'm new here.
Just installed qb64pe (v4.2.0) on my MacBook Pro (M1, Sequoia 15.5), seems to work ok.
After that, downloaded (GitHub) and installed Inform-PE according to instruction. Compiling ok, no errors.
Starting UiEditor generates an error: libc++abi: terminating due to uncaught exception of type std::length_error: basic_string 
Recompiling didn't make a difference.
Any clues?

Hello, I'm also new here. I have the same exact problem with my Macbook Pro M2 Max (Sequoia).
I tested a simple "Hello World", and it works without any problems.

How can I find out what causes UiEditor to crash?

[Unseen Machine]

Macbook 

Thatll do it! I am sooooo not the guy to actually answer this but Qb64 is mainly for windows, Linux and MacOS versions are tricky! dbox or steve will fill you in im sure but i the meantime, welcome onboard the Qb64 train!

john

[NakedApe]

Macbook 

Thatll do it! I am sooooo not the guy to actually answer this but Qb64 is mainly for windows, Linux and MacOS versions are tricky! dbox or steve will fill you in im sure but i the meantime, welcome onboard the Qb64 train!

john

I don't know about that, Unseen. I've been using QB64PE on Mac for a few years now and am loving it. Sure, there are several commands that are Windows only, but most everything works on MacOS. We have @a740g to look out for us Mac users.   Sometimes there are differences between Win and Mac and it's important to test programs on both systems to catch bugs. I know nothing about Linux, but many users here seem to have good luck with it...