WinFBE Suite 2.1.1 (April 14, 2020)

Started by Paul Squires, April 14, 2020, 04:14:42 PM

Previous topic - Next topic

Paul Squires

Version 2.1.1 (April 14, 2020)
Editor:
- Added: Brace highlight matching. Settings to enable/disable and to set colors for match and no match.
- Added: New Compiler setup option: "Disable successful compile sound".
- Added: Environment Options dialog now remembers last selected option and will display that option window on subsequent opens.
- Added: Shift+F7 as keyboard shortcut key for "Environment Options".
- Added: F6 Goto Definition will now find functions in class methods that are not prefixed with the "this" keyword.
- Added: Codetip popups will now find functions in class methods that are not prefixed with the "this" keyword.
- Changed: AutoInsert now correctly implements TABs for indentation if the editor option "Treat Tab as spaces" is unchecked.
- Fixed: Code Editor option called "Position searches to middle of screen" was not positioning in all envisioned scenarios.
- Fixed: The keyword "Chr" and "RTrim" were incorrectly mixed capitalized in the freebasic_keywords.txt settings file. Users will need to manually change that keyword to all lowercase "chr" and "rtrim" in order for keyword highlighting to be correct.
- Fixed: Corrected situation whereby non-project related notes could get reset when switching between non-project files and projects.
- Fixed: Logic error when saving project file names/paths to Most Recently Used list when the project resided on a drive different than the WinFBE application. This situation involved the incorrect application of the {CURDRIVE} parameter.

Visual Designer:
- Added: ToolBox window size and position is now saved and restored between sessions.
- Added: Error message displayed if using "Project Options" to add manifest and resource files but the WinFBE_manifest.xml and/or WinFB_resource.rc files are missing from WinFBE Settings folder.
- Fixed: Forms with BorderStyle property set to FormBorderStyle.SizeableToolWindow were incorrectly displayed in the visual designer.
- Fixed: Code generation error if last line of main code file does not have trailing CR/LF.

Download from:
https://github.com/PaulSquires/WinFBE/releases
Paul Squires
PlanetSquires Software

SeaVipe

Thanks, Paul, Brace Highlight Matching. On my machine, the colours are extremely faint. I have tried using the Default Theme (even without my sunglasses!) but still, the colours barely show. Using my Dark Theme (Black BG) setting the Brace colours to bright red and bright green or any colour still does not show. Removing the highlight row colour has no effect.
Clive Richey

Paul Squires

Thanks Clive, I wasn't sure what colors to use for brace highlighting. They look okay on my setup (light theme) but I doubt that I'll even use that feature because I find it more visually confusing than helpful. If you settle on any colors that you'd like to see as a default then just let me know. You can set the brace highlighting colors in the Environment Options dialog.
Paul Squires
PlanetSquires Software

SeaVipe

Hi Paul, I've monkeyed around with all sorts of combinations and I just can't get brace colours to really appear. I can see that they do slightly change BG colour but its very, very faint no matter what colours I select in Environment Options, including various themes. I think my choice would be Signal Green and Signal Red on Black - but that's just for my dark theme requirements and without being able to visualise it live I can't be too sure. I find Brace matching can be helpful.
Clive Richey

Paul Squires

The matching brace pair should show up when your caret/cursor is placed right before the brace. If there is no matching brace then it will appear in red, otherwise, green. I believe that this is the way that it works in other editors...not sure, because I have never used the feature in other editors.
Paul Squires
PlanetSquires Software

Paul Squires

I've added these lines after setting the brace colors in order to better emphasize and make them stand out. It is much much much more noticeable now.

                           SciExec( pDoc->hWndActiveScintilla, SCI_INDICSETOUTLINEALPHA, 8, 255 ) ' transparency of outline
                           SciExec( pDoc->hWndActiveScintilla, SCI_INDICSETALPHA, 8, 127 )        ' transparency of interior     
Paul Squires
PlanetSquires Software

SeaVipe

Transparency? That would account for it. Thanks.
Clive Richey