Uh-oh ... - .Left assignment issue

[badkarma]

Its probably my dodgy coding, though ...

I've just realised I am still using the old v6 B4PPC and not the latest v6.30 as when opening GalleyHC's code in the previous post, Basic4PPC said GalleyHC's program was saved in a later version of Basic4PPC.

*ANYWAY* ... so I updated my Basic4PPC to v6.30 (could have sworn I did it previously ... perhaps I was having a bad day) ...

*ANYWAY * ... to get to the point - having just realised my app (Adventure PDA) was still compiled on the old version of Basic4PPC I thought I would recompile to 6.30 (as I said I had done previously on my app)

*ANYWAY* ... when recompiling, I receive an error (which I did not get previously on the earlier version) ...

Error Compiling program. (For both device and desktop)
Error description: Subroutine identifier cannot be assigned
Occured on line: 2421
AdvDesc.Left = 133

AdvDesc is a label caption which can be found on the FSelect form in my app...

You can take a look at my full SBP at http://www.therealeasterbunny.pwp.bl....uk/advpda.sbp

... or an excerpt of my code is:

ButGETDROP.Top = 190
ButMAG.Top = 190
ButINV.Top = 190
ButHELP.Top = 190
ButELC.Top = 190
AdvDesc.Height = 220
AdvDesc.Left = 133
AdvDesc.Width = 105
BackGnd.Height = 162

Could it be because I have a subroutine called Left ?

If so, the old version took a blind eye to this and the new version is getting grumpy at it ?

[badkarma]

Yes, I have done some testing and I can now confirm that if I rename my "sub Left()" to "sub xLeft()" it now compiles OK.

Perhaps a wishlist for the compiler to run and pop up an error if using reserved words for subs.

Curious ... what happens if you have a variable called "Left" ... will test now ...

[badkarma]

It seems happy with a variable called Left ...

It only errors on compile of AdvDesc.Left = 133 if you have a sub called Left ...

Is this a bug of the compiler then, or should it not let you compile if subs are using reserved words?

[badkarma]

Just rummaging in the Announcements and I saw a reply to v6.30 released by DeeCee ...

I downloaded and installed V 6.30. The install went ok. When I run the desktop, the Help file and references say v 6.30, but the About Box, still says v 6.05. Is that correct?

This maybe what happened to me, as tonight i didn't "Repair' but did Uninstall then re-ran setup to install - I must have "repaired" earlier this month which is why I was still on the old version 6.05 (!?)

Anyway - cooking on gas now ... apart from my 2x DLLs wont go into my EXE - Erel did say "Most" DLLs, not "All" my DLLs are webbrowser.dll and bdeviceinfo.dll - why do some DLLs get embedded and some not? Just curious...

My EXE file size has increased by 40k though - think could be the images that are now getting placed in the EXE - will continue to poke ...

[agraham]

Originally Posted by badkarma

my DLLs are webbrowser.dll and bdeviceinfo.dll - why do some DLLs get embedded and some not?

See here Merging agraham libraries with the exe

[agraham]

See this attachment. You could "merge" the bDeviceInfo library by either using the Door library instead (which itself merges OK) as demonstrated here or by putting the .cs source file in your Basic4ppc Desktop\Libraries folder. Caveat - I haven't tried the latter but it is so simple it must work - which means it probably won't!

[Erel]

My EXE file size has increased by 40k though

The size has increased only because of images / libraries that are now merged in the executable.

[agraham]

Source code for merging WebBrowser library now posted Web browser for desktop and device

[badkarma]

Cool, thanks chaps, I will have a tinker and report back.

[badkarma]

Thanks agraham. The two libraries successfully merged OK for Adventure PDA. I will be releasing v1.03 shortly which will have a landscape mode gameplay option. Just some minor testing to complete now ...