InForm-PE

[Kernelpanic]

@a740g - Thank you for your effort! Your version works.
I had previously tried to use your advice, but the result was that the entire computer froze.    I just got out of there with a reboot.
Then I deleted the entire program and recreated it. But that didn't lead to anything, the program didn't work. Then I used your version and it worked. There is something I didn't understand.

To understand how it works I tried to create a new program with two output fields. But that's where I got stuck. I do not understand the whole structure of InForm. Either it's my fault or it's because the program is so complicated.

The new attempt. . . and the program in VB.


OK. The program itself is a great achievement. Really! When it works it comes very close to VisualBasic. And how many developers did they have there?

[GareBear]

a740g,

I get the start up screen, it says "Loading fonts list ..." and does nothing. Do I need to wait for so long or is there something else that I missed?

[a740g]

a740g,

I get the start up screen, it says "Loading fonts list ..." and does nothing. Do I need to wait for so long or is there something else that I missed?

Are you on Windows?

UiEditor enumerates systems fonts when loading and if the system has a lot of fonts, then it may take some time.
If you are on Windows, can you check how many fonts you have in following registry path: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts

Another reason I can think of is, RegEnumValueA() returning a funny value here which locks up LoadFontList() in an infinite loop.

I'll take a look into this over the weekend. Thank you for reporting.

[GareBear]

a740g.

I use linux for an os. The fonts I downloaded is in the same folder as QB64PE. The flavor of linux I use is Slackware 15.0.

Update:

I did what you said and waited for it to read the fonts to load. Sorry about the false bug. I will try to be more careful test more next time.
It is running with Form1, Color mixer, Toolbox.. Etc. You know it is doing normally. Thank you for your help.

[a740g]

a740g.

I use linux for an os. The fonts I downloaded is in the same folder as QB64PE. The flavor if linux I use is Slackware 15.0.

Ok. Thank you for the update.

In that case, it is looking for the fonts in /usr/share/fonts (see here) and I think something weird is going on inside idezfilelist$() and idezpathlist$().

[GareBear]

Update:

I did what you said and waited for it to read the fonts to load. Sorry about the false bug. I will try to be more careful test more next time.
It is running with Form1, Color mixer, Toolbox.. Etc. You know it is doing normally. Thank you for your help.

[a740g]

Tiny update:

• InForm-PE UiEditor now uses the OS common dialogs for open and save actions.
  
• Re-wrote font handling code (UiEditor now uses FontMgr).
  
• Restored all lost wiki images (https://github.com/a740g/InForm-PE/wiki).
  

Get the latest using the links in the first post. Please report bugs and other quirks.

Cheers!

[atl068]

Tiny update:

• InForm-PE UiEditor now uses the OS common dialogs for open and save actions.
  
• Re-wrote font handling code (UiEditor now uses FontMgr).
  
• Restored all lost wiki images (https://github.com/a740g/InForm-PE/wiki).
  

Get the latest using the links in the first post. Please report bugs and other quirks.

Cheers!

Bug: In the dropdown list (and list), if I try to specify the items at design time, and I have multiple items, if I use "\n" as per the wiki ( https://github.com/a740g/InForm-PE/wiki/List ), it will claim that it is "invalid value". This is definitely a new bug because in my previous projects written and working in the old QB64 and old Inform... I can load it and it would also complain of the same "invalid value"

[a740g]

@atl068 Thanks for reporting. I'll take a look. But just to clarify, are you saying that the old InForm + QB64 has the same issue?

[bplus]

This is definitely a new bug because in my previous projects written and working in the old QB64 and old Inform... I can load it and it would also complain of the same "invalid value"

yeah looks like a NOT is missing, This definitely NOT a new bug... it would also complain of the same "invalid value"