A couple of things that might save someone else some time -
Here are a some things that got me :
1) In the FF project file the (.ffp file) I needed to change the line
DefaultIncludes=0
to
DefaultIncludes=1
This has to be done with an editor (Notepad etc.)
I'm not sure what is going on here. It doesn't matter which set of includes I specify in the Environment setup.
With DefaultIncludes=0 I get an error 420 : Relational Operator Expected
2) Variables called db and dd are no longer valid. This does not appear to be a PB10 thing, but probably to do with the new includes.
(I am using Jose's new ones) It would be nice to know if other variable names are affected though.
3) Font End fhndl worked fine in PB9, but in PB10 be careful, you might need
Graphic Set Font 0
before
Font End fhndl
(This is probably a good thing to do anyway)
4) If you are using Jose's (excellent) includes and using GdipSaveImageToFile then you need to use the new Wide string declarations:
'Local strFileName As string -->> this worked before
Local strFileName As WSTRINGZ *256 '-->> this is what you need now
'strFileName = UCode$(filetosave) -->> you needed to convert to unicode before
strFileName = filetosave '-->> now you don't
hStatus = GdipSaveImageToFile(pImage, strFileName, EncoderClsid, ByVal 0)
Now I have most of my FF3 projects moved over. Wish I could say the same about the older stuff created in PBForms.
I am quite surprised actually, considering how easy the transition was from PB7 to 8 and then 9.
That being said I am looking forward to using the new features of PB10 (and FF4 when it is ready).
Quote
2) Variables called db and dd are no longer valid. This does not appear to be a PB10 thing, but probably to do with the new includes.
(I am using Jose's new ones) It would be nice to know if other variable names are affected though.
It has nothing to do with the includes. db, dd, dw and dq are reserved words in PB10. They are used in the ASMDATA/END ASMDATA block.
Conflicts with reserved words are always a pain, but it's the price that you have to pay for asking for new features.
Quote
I am quite surprised actually, considering how easy the transition was from PB7 to 8 and then 9.
If native unicode support had been implemented years ago, we would not had the need to use workarounds. You can still use that UCODE$/ACODE$ legacy code with PB 10 using the old headers.
Thanks for your reply Jose.
I am curious about db, dd, dw and dq because I tried db and dd quickly in a very simple PB forms test
declared as :
Local db,dd as long
and received no error on compile.
Too late here now to get into it again, will have a look tomorrow (I don't doubt you though!)
You must have compiled it with PB 9. If you try to compile it with PB 10, you will get a "Variable expected" error.
Yes, you are correct, it was getting late last night.