PlanetSquires Forums

Support Forums => PlanetSquires Software => Topic started by: Paul Squires on July 06, 2016, 03:32:42 PM

Title: WinFBE on GitHub (July 6, 2016)
Post by: Paul Squires on July 06, 2016, 03:32:42 PM
New code just uploaded to the repository.

Here are some of the highlights:

- Changed the folder structure. Much better organization now.

- Fixed regression whereby cut, copy, paste not working for right click menu in code editor.

- Added Function List. Assigned it F4 accelerator key (toggles show/hide).

- Reassigned Project Manager to F9 key (toggles show/hide).

- Added Show/Hide Compile Results and assigned it F7 key (toggles show/hide).

- Reworked frmTemplates for loading template file descriptions. Speed improvement.

- Added a toolbar dropdown for Open File. Displays list of most recently used files.

Jose, a few new strings added to the Spanish language file.  :)
Title: Re: WinFBE on GitHub (July 6, 2016)
Post by: Paul Squires on July 06, 2016, 06:42:44 PM
Uploaded code for "Sub/Function Definition" and "Last Position". However, the editor is not smart enough yet to find instances of subs/functions that are derived from instances of class types. That will involve eventually implemented and fuller code parser for each document.
Title: Re: WinFBE on GitHub (July 6, 2016)
Post by: Paul Squires on July 06, 2016, 08:04:03 PM
a few more additions/changes:

- Project Manager will now only automatically show on project load if it is a New Project.

- DELETE key will now remove selected file from Project Manager.

- Added another Project Manager popup menu when no line is selected. Options to Add Files to Project, and Project Options.
Title: Re: WinFBE on GitHub (July 6, 2016)
Post by: Paul Squires on July 06, 2016, 09:52:35 PM
Another good addition:

Enhanced the project save file (*.wfbe) to save more state information. The position of documents loaded into the top Tab Control are saved. The visual displayed top line and position of caret is saved/restored for each document. Finally, the active tab is set once the project is loaded. The goal is to be able to save and then restore the editing environment of the project to you can pick up right where you left off.
Title: Re: WinFBE on GitHub (July 6, 2016)
Post by: Paul Squires on July 07, 2016, 12:28:37 AM
Updated code:

- Most recently used Projects will now also display on the "Open" toolbar dropdown arrow popup menu.

- Dramatically reduced screen flicker by handling the WM_ERASEBKGRND message and only redrawing application background when no tabs are active.
Title: Re: WinFBE on GitHub (July 6, 2016)
Post by: Marc Pons on July 07, 2016, 09:10:13 AM
hi Paul,

just to say , i've tried to use your new editor to test it, (win32 in xp-sp3) but was not able to launch it

error message : QueryFullProcessImageNameW not found in Kernel32.dll

problem with XP ?

i've also compiled it , but infortunatly got the same result . :'(

Marc
Title: Re: WinFBE on GitHub (July 6, 2016)
Post by: Paul Squires on July 07, 2016, 10:30:38 AM
The editor does not work on WinXP. Never will. It is designed for technology for Windows Vista or higher.

Time for you to upgrade your OS ?
Title: Re: WinFBE on GitHub (July 6, 2016)
Post by: Paul Squires on July 07, 2016, 10:35:16 AM
I know that a lot of people still use WinXP but it has been deprecated by Microsoft and it is about time that people move on, especially programmers. WinXP was released on August 24, 2001, that's almost 15 years ago!
Title: Re: WinFBE on GitHub (July 6, 2016)
Post by: José Roca on July 07, 2016, 01:53:08 PM
Even Windows 7 is becoming too outdated. There was a time when Microsoft provided updates to maintain backward compability, but now it refuses to do it as a way to force us to update to its new OSes.
Title: Re: WinFBE on GitHub (July 6, 2016)
Post by: José Roca on July 07, 2016, 04:13:12 PM
For example, from Windows 8.1, it provides new APIs related with DPI awareness. Right now, I would need to use the GetProcessDpiAwareness function, because I want to know if an application is running virtualized or not. If I find its handle and try to get the DPI, it tells me that is running at the DPI of mi monitor, but it isn't true; and if I call GetWindowRect to get its dimensions, it returns its real dimensions at 96 DPI, not the scaled ones. Of course, Windows knows if the application is DPI aware or not, but it won't tell you unless you're using at least version 8.1. Many years ago, they would have released a service pack to update Vista and Windows 7 with these features, but no longer.

Windows XP does not even support High DPI, so its use is not adequate to these times of High DPI monitors.

Title: Re: WinFBE on GitHub (July 6, 2016)
Post by: José Roca on July 07, 2016, 04:30:26 PM
There is also the opposite problem of tools and custom controls running happily in Windows XP or even 2000, but unusable with High DPI monitors because they don't scale according the DPI setting.

And what about these programmers working with a tall monitor that don't consider that when used with a full HD monitor his big dialogs will go outside the working area and there is no way to see and click the buttoms at the bottom? There is a know PBer that always uses 300, 300 for the x, y coordinates of his DTT dialogs in all the code that he posts. Full HD is widely used by home users.

Title: Re: WinFBE on GitHub (July 6, 2016)
Post by: José Roca on July 07, 2016, 05:08:13 PM
> Jose, a few new strings added to the Spanish language file.  :)

New language file.
Title: Re: WinFBE on GitHub (July 6, 2016)
Post by: Paul Squires on July 07, 2016, 05:45:51 PM
Quote from: Jose Roca on July 07, 2016, 05:08:13 PM
> Jose, a few new strings added to the Spanish language file.  :)

New language file.

Thanks Jose!
Title: Re: WinFBE on GitHub (July 6, 2016)
Post by: Paul Squires on July 07, 2016, 07:58:07 PM
Code updated;

- Finally added the code to load WinFBE projects or source code files from the command line.

- Updated the folder layouts one more time. Placed the Language files and Settings files into separate subfolders.
Title: Re: WinFBE on GitHub (July 6, 2016)
Post by: Paul Squires on July 07, 2016, 09:17:20 PM
Code updated:

- Added option to "Clear this list" for MRU Files and MRU Projects.
Title: Re: WinFBE on GitHub (July 6, 2016)
Post by: Paul Squires on July 07, 2016, 09:23:39 PM
.... I have now switched from JellyFB to WinFBE for actually writing WinFBE. This now means that WinFBE is used to write itself. I now remember the feeling I had the first time that I used FireFly to compile FireFly.  :)
Title: Re: WinFBE on GitHub (July 6, 2016)
Post by: José Roca on July 07, 2016, 11:08:21 PM
We write tools to make programming easier, but we could not do it if we weren't able to write these tools by hand.
Title: Re: WinFBE on GitHub (July 6, 2016)
Post by: José Roca on July 08, 2016, 09:24:48 PM
Something weird has happened with the .lang files, e.g.

' WinFBE localization file for ENGLISH language
਍✀ഀഀ
' The first element to exist must be called "MAXIMUM" and needs to be set to
਍✀ 琀栀攀 瘀愀氀甀攀 漀昀 琀栀攀 氀愀猀琀 欀攀礀 椀渀 琀栀椀猀 昀椀氀攀⸀ ഀഀ
'
਍✀ 吀栀椀猀 昀椀氀攀 猀栀漀甀氀搀 戀攀 挀爀攀愀琀攀搀 愀渀搀 猀愀瘀攀搀 甀猀椀渀最 唀吀䘀ⴀ㄀㘀 攀渀挀漀搀椀渀最 ⠀甀渀椀挀漀搀攀⤀⸀ഀഀ
'
਍✀ 䔀愀挀栀 氀椀渀攀 爀攀瀀爀攀猀攀渀琀猀 愀 欀攀礀⼀瘀愀氀甀攀 瀀愀椀爀 搀攀猀挀爀椀戀椀渀最 琀栀攀 瀀漀猀椀琀椀漀渀 琀漀 猀琀漀爀攀 琀栀攀ഀഀ
' localized word/phrase into the localization array used by winFBE. Simple.
਍ഀഀ
MAXIMUM:230
਍ഀഀ
00000:&OK
਍    ㄀㨀☀䌀愀渀挀攀氀ഀഀ
00002:&File
਍    ㌀㨀☀一攀眀ഀഀ
Title: Re: WinFBE on GitHub (July 6, 2016)
Post by: José Roca on July 08, 2016, 09:39:42 PM
WinFBE 64 bit as GPFed one after cheking the option "Confine caret to text" and clicking OK. Can't reproduce it again. Maybe something wrong in the packaged .ini file?
Title: Re: WinFBE on GitHub (July 6, 2016)
Post by: Paul Squires on July 09, 2016, 12:14:47 AM
Yes, I noticed a corruption in the files yesterday when I changed GitHub's default line ending setting for the text files to be CRLF. I fixed it last night and re-uploaded. You must have a version prior to today? I also added several new uploads today to reduce flicker in the editor. Looks smoother and more polished now.
Title: Re: WinFBE on GitHub (July 6, 2016)
Post by: José Roca on July 09, 2016, 12:40:54 AM
I have just downloaded it again, and the .lang files are corrupted.
Title: Re: WinFBE on GitHub (July 6, 2016)
Post by: Paul Squires on July 09, 2016, 02:01:23 AM
That is strange. They view okay from the GitHub website but when you download the zip they show corrupted. Looks like it must be because they are unicode files (*.lang, *.ini). I will remove those types from the .gitattributes file and see if it makes a difference.
Title: Re: WinFBE on GitHub (July 6, 2016)
Post by: Paul Squires on July 09, 2016, 02:04:35 AM
Yes, that was exactly the problem. Download is working okay now.