Perhaps the examples could be updated to reflect the more current FB version changes to the TYPE of the arguments for these keywords. It can be confusing for a beginner, especially if they research any examples in the forum history that mention type-mismatch errors.
I didn't check any of the others (SCREENRES, SCREENCONTROL, WIDTH, etc.)
edit:
(Actually, I did check others. Many have problems. I don't want to imply these are the only ones with errors.)
david
SCREENINFO, SCREENPTR, etc examples
-
- Posts: 606
- Joined: Nov 28, 2012 1:27
- Location: CA, USA moving to WA, USA
- Contact:
SCREENINFO, SCREENPTR, etc examples
Last edited by speedfixer on Mar 25, 2022 6:33, edited 1 time in total.
Re: SCREENINFO, SCREENPTR, etc examples
Yes, but it would then be necessary to check all the examples of the documentation, because in many other cases one uses for example Integer variables where Long variables would be sufficient ?
(at least the current examples already compile without errors it seems to me)
(at least the current examples already compile without errors it seems to me)
-
- Posts: 606
- Joined: Nov 28, 2012 1:27
- Location: CA, USA moving to WA, USA
- Contact:
Re: SCREENINFO, SCREENPTR, etc examples
I accept that the usage of integer everywhere is leftover from before the 64 bit 'fix.'
But each keyword page with examples should have valid, proper usage examples that can stand on its own, without contadictions within that one page.
Any one page should be able to be validated on its own. Checking/fixing one at a time will do. No rush.
But each keyword page with examples should have valid, proper usage examples that can stand on its own, without contadictions within that one page.
Any one page should be able to be validated on its own. Checking/fixing one at a time will do. No rush.
Re: SCREENINFO, SCREENPTR, etc examples
It will be necessary to make a systematic check of all the keyword pages (little by little in alphabetical order for example) because moreover in rare cases, the variable types themselves specified in the documentation are not exactly those implemented in the code.
Checking in progress.....
Checking done.
(to see later the omissions piecemeal)
Checking in progress.....
Checking done.
(to see later the omissions piecemeal)
Last edited by fxm on Mar 26, 2022 10:04, edited 24 times in total.
Reason: Done from "A" to "Z".
Reason: Done from "A" to "Z".
-
- Posts: 606
- Joined: Nov 28, 2012 1:27
- Location: CA, USA moving to WA, USA
- Contact:
Re: SCREENINFO, SCREENPTR, etc examples
Thanks.
No rush; do it as is convenient for you.
There are a lot of details.
Perfection is the goal, not the expectation.
No rush; do it as is convenient for you.
There are a lot of details.
Perfection is the goal, not the expectation.