PlanetSquires Forums

Please login or register.

Login with username, password and session length
Advanced search  
Pages: 1 2 [3]

Author Topic: WinFBE on GitHub (December 6, 2016)  (Read 9238 times)

Paul Squires

  • Administrator
  • Guru Member
  • *****
  • Posts: 9200
  • Windows 10
    • PlanetSquires Software
Re: WinFBE on GitHub (December 6, 2016)
« Reply #30 on: December 25, 2016, 01:20:42 PM »

Codetip popups for builtin FreeBASIC keywords added to GitHub.
Logged
Paul Squires
PlanetSquires Software
WinFBE Editor and Visual Designer

Paul Squires

  • Administrator
  • Guru Member
  • *****
  • Posts: 9200
  • Windows 10
    • PlanetSquires Software
Re: WinFBE on GitHub (December 6, 2016)
« Reply #31 on: December 25, 2016, 11:35:06 PM »

Made a few more changes. Codetips now show for subs/functions present in all loaded documents in the editor (user written functions). I am also now closing the Compile Output window if it is currently active and a subsequent compile produces no warnings/errors.

I am now ready to deal with the Windows API codetips and other sub/functions found in other #INCLUDE'd files.

This approach seems like it might be the most efficient approach:
(1) Prebuild a codetips file (codetips_winapi.ini) (actually, maybe one for ansi functions and another for unicode).
(2) Parse source code files during loading for all #INCLUDES. Bypass any Windows includes because they would have already been prebuilt. Parse any other #INCLUDEs such as Jose's AFX includes.
(3) When "(" is pressed, search builtin FB keywords first, then subs/functions of all loaded documents, and finally the Windows API codetips (if previous parsing showed that Windows API files were present in the source. Display the ANSI or UNICODE version depending on if #DEFINE UNICODE was present in the source).

Sounds pretty do-able.  :)


Logged
Paul Squires
PlanetSquires Software
WinFBE Editor and Visual Designer
Pages: 1 2 [3]