cbruce wrote: ↑Jan 26, 2022 3:19
Paul, I already owe you a huge amount of thanks for WinFBE; I would not be productive in FreeBASIC without it.... And now you increase your good karma by making WinFBE even better and enabling this GUI nerd to finally be able to do something useful on Linux! (And that is a nice looking UI also!)
Awesome thanks! I am looking forward to getting the new version out. As Munair points out, yes the editor is WinAPI based so the visual designer may not be a hit on Linux, but the designer is just one part of the editor. Sure, I doubt that many Linux users will give WinFBE a try on Linux because they already have their favorite native Linux editor. That makes sense. Maybe the whole Linux/Wine thing will eventually just serve as a personal learning experience for myself. I'm good with that.
An indicator for a file's current EOL type would be handy. Maybe [Edit][End of Line Character Conversion] that looks like [Edit][File Encoding] instead of the current [Convert to ???] selections. The user gets the choice of EOL format with an indicator dot that shows the current EOL in use for that file.
I have the line encoding moved to the statusbar (bottom right corner) and a popup menu will show when clicked on that allows you to change the file's line ending encoding. The current encoding is selected "with an indicator dot" on the popup menu.
Find/replace would be stronger if the textboxes were replaced with single line combo boxes with pulldowns that each kept their last 15 or 20 items available for selection. (And keep that data across sessions?)
Good idea. I have made a note of this and will implement it. VSCode handles this sort of thing by simply using your up/down arrow keys to cycle through the find/replace history (rather than dropdown comboboxes). I'll see what I can do.
(bug?) - Replace currently ignores [in selection] when doing [replace all] and just replaces all occurrences in the file.
A. It would also be proper if [replace next] would respect the limits of [in selection].
Most likely bug. I totally rewrote the whole find and find/replace code related to Selections. The logic when a selection would be active was wrong. All fixed now.
It would be nice if an active [Find] did *NOT* automatically jump into a file when switching tabs to another file - (I lose my spots in files (and train of thought) ALL the time!)).
Interesting. I thought that the automatic search would be a nice feature rather than a problem when switching edit windows. I can certainly disable this type of behaviour.
I use bookmarks a lot. It would be really nice if the positioning of the retrieved bookmark lines was consistent... ie. when I hit next/prev bookmark, that line is always positioned as first row on screen, or middle row on screen. That way, I'm not scanning the screen looking for where the bookmark is each time. Also, it comes in very handy to "overlay", and allow for visual compare of, a couple of pieces of code.
I'll check this. If I remember correctly, I wanted the edit control to position as needed especially if the bookmark was already visually on the screen. I can certainly reposition the screen to a consistent location when a bookmark is invoked.
Bookmarks could also be made much more useful if I had a picker for my current bookmarks (line# and initial text from that line).
I had never thought of this. I will take a look to see what I can implement.
]7. If [clear bookmarks] only affects the current file, then it would be good to also keep bookmarks across sessions.... If changes were made outside of WinFBE that invalidated the bookmark positions - I could just clear them for that file.
The new load/save sessions feature saves and restores bookmark positions. Projects have always saved/restored bookmarks.
I use the [file list] and [function list] combobox pulldowns *ALL* the time to jump around quickly.
Those are gone now. I have centralized in one place (Function List). It was previously in 3 different places. I will have several different ways to display the files and functions (sorted/unsorted, etc) as well as a search box.
That little combobox that displays (and allows me to choose) the current build configuration has saved me a *lot* of time. I often switch builds for different reasons, and sometimes... well, the only thing that has saved me a lot of troubleshooting at times is *seeing* the current build and going, "Whoa!"... set the correct build for the current purpose and get back to work. It would be good (for me) if that was still a visible item in the main UI of the new version.
It's still there, albeit now located in the bottom left of the statusbar. Clicking on it allows you to change the build configuration.
(bug?) - Syntax highlighting on a line fails for all keywords/characters after occurrence of a "#" used as a file reference. Examples:
put_result = put(#f, ,gCtxt())
print #dump_tables_fnum, hex(ibyt, 2); "trash string"
Yes, this is a limitation of the previous Scintilla lexer. I now have a dedicated lexer that I can tweak in order to fix things like this.
Thanks a *LOT* !!!
You're very welcome :-) I'm sure that there will be lots of discussion once the new version is released and then further changes and tweaks made based on feedback.