WinFBE Suite 1.7.2 (August 3, 2018)

[Paul Squires]

Version 1.7.2 (August 3, 2018)
- Added: Completed ListBox control documentation and tips.
- Fixed: Regression from 1.7.1 preventing text input into PropertyList items (Name, Text, etc).

https://github.com/PaulSquires/WinFBE/releases

[Joerg B.]

Good morning Paul and José

First of all, thank you so much for investing your time so that hobby programmers like me don't have to fight with all the shoals of WinApi and so on.
Without your work, the transition would be much harder.

I just love your WinFBE together with José's WinFBX.

I have previously created small programs with PowerBasic.
And now I want to create the programs with Freebasic in the future.

While playing around with WinFBE I noticed that in a text box no texts are wrapped that already exist in the source code.
All values that have to do with this are set accordingly in the properties.
For example (AcceptsReturn = True, Multiline = True, WordWrap = True) Or do I have a thinking error?

Furthermore there are error messages which I can't understand.
I have a button to stop the progrann. I definitely haven't changed the ImageAlign property and yet I get the following error message.
Setting the property ImageAlign = ImageLayout.None does not change anything.

FreeBASIC compiler - version 1.06.0 (07-03-2018), built for win64 (64bit)
Copyright (C) 2004-2016 The FreeBASIC development team.
standalone
target: win64, x86-64, 64bit
compiling: G:\WinFBE_Suite\Sample_Projects\Test_Projekt\Fenster.bas -o G:\WinFBE_Suite\Sample_Projects\Test_Projekt\Fenster.c (main module)
G:\WinFBE_Suite\Sample_Projects\Test_Projects\Window.bas(424) error 18: Element not defined, ImageAlign

Somtimes, if I re-create all files, it creates multiple entries and the compiler aborts.

This behavior occurs with all versions so far.

Maybe you can check this out when you get the chance.

[Paul Squires]

Hi Joerg, thanks very much for testing. I will look at the multiline textbox and see what the problem is. Not sure about the ImageAlign error. That seems to imply that you are using the latest WinFormsX include files.

Are you using the "WinFBE_Suite" download from the GitHub releases page?  https://github.com/PaulSquires/WinFBE/releases/download/1.7.2/WinFBE_Suite.rar
That download contains all of the latest WinFBE, WinFBX and WinFormsX code needed to compile.

[Joerg B.]

Hi Paul

I am using the latest WinFBE Suite version 1.7.2. 

[Paul Squires]

I have a button to stop the progrann. I definitely haven't changed the ImageAlign property and yet I get the following error message.
Setting the property ImageAlign = ImageLayout.None does not change anything.

FreeBASIC compiler - version 1.06.0 (07-03-2018), built for win64 (64bit)
Copyright (C) 2004-2016 The FreeBASIC development team.
standalone
target: win64, x86-64, 64bit
compiling: G:\WinFBE_Suite\Sample_Projects\Test_Projekt\Fenster.bas -o G:\WinFBE_Suite\Sample_Projects\Test_Projekt\Fenster.c (main module)
G:\WinFBE_Suite\Sample_Projects\Test_Projects\Window.bas(424) error 18: Element not defined, ImageAlign

Ok, this one is now fixed. There were some properties in the PropertyList that are now fully implemented (such as images, etc) so they had the possibility to cause a compile time error. I have temporarily removed those types of properties until I get them written.

[Paul Squires]

While playing around with WinFBE I noticed that in a text box no texts are wrapped that already exist in the source code.
All values that have to do with this are set accordingly in the properties.
For example (AcceptsReturn = True, Multiline = True, WordWrap = True) Or do I have a thinking error?

This is now fixed. Blame this one on "Paul being stupid" 

[Paul Squires]

I ended up fixing several TextBox related problems:

- Fixed: TextBox WordWrap property was coded incorrectly.
- Fixed: TextBox HideSelection property was coded incorrectly.
- Fixed: TextBox CharacterCasing property not correctly referencing the CharacterCase Enum.
- Fixed: TextBox TextScrollBars property changes not reflected visually in the visual designer.
- Fixed: TextBox AcceptTab property was not fully implemented.

[Joerg B.]

Hi Paul

This is now fixed. Blame this one on "Paul being stupid" 

Come on, don't be too hard on yourself. 

[Joerg B.]

Hi Paul
One question.
Have you already uploaded WinFBE with the changes to the TextBox properties, or do you need to add or change anything else? 

[Paul Squires]

I was working on the issue where the compiler error output listview does not show the accurate line number. For form source code files, the line number needs to be adjusted to account for all of the hidden lines of metadata that exists in a form file. I will do my best to get a new upload to GitHub tomorrow. It is a holiday here today and I've been invited out for a dinner party 

[Joerg B.]

Good morning Paul

Looks like I'm whining about a toy like a little kid. 

That's right, it is. 

But it is certainly good for my development to practice patience. 

That's off topic now, but I had to tell myself that.

[SeaVipe]

Hi Paul,A few observations that may not be relevant or important or you've likely dealt with them already but here's some things I've discovered so far:
- No button_down text property. (Although this can be accomplished programmatically)
- Bookmarks are not global. Could be optional.
- Bookmark colours fixed at White with black circle. The setting in Colors and Fonts is ignored.
- Project history always blank at program start. Unless the first project is the supplied Visual Designer test project, but never more than 1 project in the Recent list at startup.
- Open Project.
    After selecting via Double Clicking file name, Open Project file open dlg box opens a second time. Select Cancel and the project opens correctly.
    Selecting the file a second time results in only a partial Project being loaded. Some files must be added to the project.    This behavior is only repeatable after rebooting machine.
- Certain font types don't display properly or at all (replaced with what looks like Segoe UI). On either of my Windows 10 machines the offending fonts are bitmap fonts ".fon". TrueType work correctly. This is could be a Windows setting.
- Label. TextAlign. (Properties in Designer) Any use of "Middle" settings ignores a CR and/or CRLF in the text . Any "Center" setting works properly.    Middle setting displays on 1 line Center setting displays on 2 lines.

Code Select Expand

.Text = "This is line 1" & CRLF & "This is line 2"
' Result
' Middle:
' This is line 1This is line 2
' Not Middle:
This is line 1
This is line 2

- New functions are created with left bracket "( " plus a space, then a right bracket ")" only at the end of the function:    Function frmMain_btnExit_Click( ByRef sender As wfxButton, ByRef e As EventArgs) As LRESULT. I know, cosmetic.
I hope this is of some use.
Clive

[Paul Squires]

Thanks Clive! I will look at these and see what I can do for the next update

[Paul Squires]

- Bookmarks are not global. Could be optional.

Hi Clive,

What do you mean by this? Bookmarks are saved and restored for files that comprise a Project. Is it that you want to traverse from bookmark to bookmark between all open documents rather than just within the current focused document (as is the case now)?

[Paul Squires]

- No button_down text property. (Although this can be accomplished programmatically)

I doubt that I'll add this as a Property. It would not be used very often and is best left to do programmatically like you are currently doing.

- Bookmark colours fixed at White with black circle. The setting in Colors and Fonts is ignored.

I have removed Bookmarks, and WinAPI Keywords from the color options. I can not find a way to set the Bookmark colors and WinAPI keywords are colored the same as regular keywords because I do not want to implement a change to the Scintilla lexer to handle additional lists.

- Project history always blank at program start. Unless the first project is the supplied Visual Designer test project, but never more than 1 project in the Recent list at startup.

I have not been able to replicate this yet.

- Open Project.
    After selecting via Double Clicking file name, Open Project file open dlg box opens a second time. Select Cancel and the project opens correctly.
    Selecting the file a second time results in only a partial Project being loaded. Some files must be added to the project.    This behavior is only repeatable after rebooting machine.

I will test this one tonight to see if I can replicate it.

- Certain font types don't display properly or at all (replaced with what looks like Segoe UI). On either of my Windows 10 machines the offending fonts are bitmap fonts ".fon". TrueType work correctly. This is could be a Windows setting.

I remember you saying that you have a special bitmap font .fon that you like. I googled for an answer and this response (which is related to the Sublime editor but could be relevant). https://github.com/SublimeTextIssues/Core/issues/1801

WinFBE uses the following code that may be interfering with your font:

      ''
      ''  FONT QUALITY
      SciMsg( m_pSci(i), SCI_SETFONTQUALITY, SC_EFF_QUALITY_DEFAULT, 0 )
      'SC_EFF_QUALITY_DEFAULT (backward compatible), SC_EFF_QUALITY_NON_ANTIALIASED,
      'SC_EFF_QUALITY_ANTIALIASED, SC_EFF_QUALITY_LCD_OPTIMIZED
     
      SciMsg( m_pSci(i), SCI_SETTECHNOLOGY, SC_TECHNOLOGY_DIRECTWRITE, 0 )
      SciMsg( m_pSci(i), SCI_SETBUFFEREDDRAW, 0, 0 ) ' turn off b/c we are using Vista+ Direct Draw

Have you tried the Notepad++ Editor? That editor also uses Scintilla for its editing component. I would be interested to know if your font works with that editor. If it does, then I will remove the above code to see if the font will then work in WinFBE.

- Label. TextAlign. (Properties in Designer) Any use of "Middle" settings ignores a CR and/or CRLF in the text . Any "Center" setting works properly.    Middle setting displays on 1 line Center setting displays on 2 lines.

Code Select Expand

.Text = "This is line 1" & CRLF & "This is line 2"
' Result
' Middle:
' This is line 1This is line 2
' Not Middle:
This is line 1
This is line 2


I haven't tested this yet.

- New functions are created with left bracket "( " plus a space, then a right bracket ")" only at the end of the function:    Function frmMain_btnExit_Click( ByRef sender As wfxButton, ByRef e As EventArgs) As LRESULT. I know, cosmetic.

I have added an additional space at the end.   My habit has long been to have a space at the beginning and none at the end. That's a holdover from when the PB editor would not correctly recognize the start of a word if it immediately followed an open parenthesis making using CTRL+ARROW navigation a pain in the butt.

I hope this is of some use.
Clive

Excellent use. I thank you for taking the time and effort for creating the list and letting me know.