Author Topic: Canary Bay (PowerBASIC version)  (Read 6781 times)

Patrice Terrier

  • Administrator
  • *****
  • Posts: 1984
    • zapsolution
Canary Bay (PowerBASIC version)
« on: June 10, 2020, 04:17:53 pm »
This is the PowerBASIC 32-bit version.

Much of advanced stuffs in the source code.

  • Anchor properties.
  • NCHITTEST emulation.
  • GetBitmapFromFile (to replace LoadImage %LR_LOADFROMFILE).
  • "STATIC" %SS_NOTIFY using flat button image.
  • Use of dynamic Region.
  • System caption emulation.
  • RegisterWindowMessage to communicate with the embedded browser.
  • CreateBrowserProcess to embed/capture another window on the fly.

You can post your questions or comments about this beta version in this thread.

06-10-2020 version 1.03
                  First PowerBASIC release
06-13-2020 version 1.04
                  New cfg.defaultURL parameter to open a specific URL (rather than Bing) when clicking on + to open a new tab.
07-03-2020 version 1.07
                  Unlimited URL short cuts selection, using horizontal scrolling.
                  Random wallpaper image when closing the last TAB.
                  New WV2B.exe 32-bit custom browser engine.               
07-29-2020 version 1.08
                  New PocessTerminate function
                  to get rid of potential orphan process when running the 32-bit project for the first time.

Note: Attachments are only available to registered users.
You must first register in order to see them.
See here what to do to register
« Last Edit: August 05, 2020, 11:44:26 pm by Patrice Terrier »
(Always working with the latest Windows version available...)

Patrice Terrier

  • Administrator
  • *****
  • Posts: 1984
    • zapsolution
Re: Canary Bay (PowerBASIC version)
« Reply #1 on: July 29, 2020, 05:20:18 pm »
The PowerBASIC CanaryBay 32-bit has been updated to version 1.08

The behavior of the 32-bit is not the same than the 64-bit, when loading the browser from a fresh boot.
Probably because the 32-bit dependencies are not loaded the same than in native 64-bit.

This could cause the creation of an orphan process when closing the powerBASIC application.
The solution is to make sure that the WV2B process has been terminated before closing the PB application,
using the new ProcessTerminate function.

The new zip is attached to the first post of this thread.
(Always working with the latest Windows version available...)