Wiki improvements
Re: Wiki improvements
I read also this but it's more like an example for finding an explicit name.
Re: Wiki improvements
changelog.txt:
- CompilerCmdLine → fxm [default stack size doubled for 64-bit targets]
- CatPgCompOpt → fxm [default stack size doubled for 64-bit targets]
- CompilerOptt → fxm [default stack size doubled for 64-bit targets]
- CompilerFAQ → fxm [default stack size doubled for 64-bit targets]
- ProPgDynamicMemory → fxm [default stack size doubled for 64-bit targets]
Documentation update:Version 1.08.0
[changed]
.....
- fbc: double the minimum and default stacksize on 64-bit to 64Kb and 2048Kb respectively.
.....
- CompilerCmdLine → fxm [default stack size doubled for 64-bit targets]
- CatPgCompOpt → fxm [default stack size doubled for 64-bit targets]
- CompilerOptt → fxm [default stack size doubled for 64-bit targets]
- CompilerFAQ → fxm [default stack size doubled for 64-bit targets]
- ProPgDynamicMemory → fxm [default stack size doubled for 64-bit targets]
Re: Wiki improvements
fxm, you are the best! If it weren't for your help I'm sure I would forget to document ... everything. :)
There's an old post about some missing docs. Exe formats and gfx formats. Do you mind re-posting that? Plus any new stuff? I'll do my best to fill in some details.
There's an old post about some missing docs. Exe formats and gfx formats. Do you mind re-posting that? Plus any new stuff? I'll do my best to fill in some details.
Re: Wiki improvements
I guess you're talking about this one: Missing Documentation
I did everything I could in relation to these shortcomings, but I am reaching my limits of knowledge here.Missing Documentation
Please edit this page to remove items when they are written or add items when they are noticed.
Missing/Incomplete/Outdated PagesPages missing/incorrect examples
- External Libraries - availability (windows, linux, DOS), usage, and download locations
Cross compiling and environment variables (used to invoke sub-programs)
Programmer's Guide (W.I.P.): External Graphics File Formats (page to fill in)
Programmer's Guide (W.I.P.): Executables (page to complete)
Dedicated page for Screen's QB/page-choosing mode - perhaps KeyPgScreenqb? (quick fb example added to KeyPgPcopy for now...)Misc wishlist
- None known (but if found, please edit this page)
- Warn in all non-portable or "evil" examples
Consistent policy about "FB version diff" KeyPgImageInfo KeyPgRem
FB source file size limit
"returning references" stuff (PEEK, (), [], ... total 7 pages BUMP'ed today)
"-gen GCC" document how to get it working (esp. in DOS)
Re: Wiki improvements
Also my fault because it was my request and we both coded it.coderJeff wrote: If it weren't for your help I'm sure I would forget to document ... everything. :)
Thank you fxm.
Btw I have to finish some docs about 64bit assembly (requested by D.J.Peter). I hope before end of january.
Re: Wiki improvements
Yes, exactly. Thank-you for collecting everything there.fxm wrote:I guess you're talking about this one: Missing Documentation
"dedicated page for qb screen statement" was added back in 2009.
@counting_pine, do you remember the reason? I feel like one page for screen should be good.
-
- Site Admin
- Posts: 6323
- Joined: Jul 05, 2005 17:32
- Location: Manchester, Lancs
Re: Wiki improvements
Mainly just to clean things up a bit I think. At the time, I maybe thought that lang qb users could do with more tailored documentation? I don’t know...
I half thought the active/visible page parameters were only available in Lang qb, but it looks like lang fb has its own syntax for that too. Maybe the “Differences from QB” section just needs to be clearer on that.
But since it has the same functionality available as lang qb, splitting the page maybe wouldn’t streamline things that much.
I don’t mind if it stays the way it is, particularly if the issue has been sitting in someone else’s backlog for 11 years!
I half thought the active/visible page parameters were only available in Lang qb, but it looks like lang fb has its own syntax for that too. Maybe the “Differences from QB” section just needs to be clearer on that.
But since it has the same functionality available as lang qb, splitting the page maybe wouldn’t streamline things that much.
I don’t mind if it stays the way it is, particularly if the issue has been sitting in someone else’s backlog for 11 years!
Re: Wiki improvements
Does anyone object if I split the first example on https://freebasic.net/wiki/KeyPgOpNew into 2 examples?
The use of 'Scope / End Scope' might be a nice example for the use of 'Scope', but only confusing on the 'New' page.
BTW: The forum seems a bit broken at the moment here, I hope it is only temporary.
The use of 'Scope / End Scope' might be a nice example for the use of 'Scope', but only confusing on the 'New' page.
BTW: The forum seems a bit broken at the moment here, I hope it is only temporary.
Re: Wiki improvements
Or, in the example, just remove both scopes but use 2 different pointer names.
Re: Wiki improvements
I decide to split the example. This was more in line with the 3rd example (1st = new / single element, 2nd = new [], 1D-array, 3rd = new [], 2D-array).
The 2nd example is a bit boring, nothing was printed. I added "Done.", to give at least some feedback.
The 3rd example (untouched by me) is not for a beginner, with: Dim As UDT Ptr Ptr p = New UDT Ptr [4]
The 2nd example is a bit boring, nothing was printed. I added "Done.", to give at least some feedback.
The 3rd example (untouched by me) is not for a beginner, with: Dim As UDT Ptr Ptr p = New UDT Ptr [4]
Re: Wiki improvements
I just modified the second filename because 2 examples cannot have the same filename.
Fortunately, in the reference documentation there are not only examples for beginners!
Fortunately, in the reference documentation there are not only examples for beginners!
Re: Wiki improvements
To finalize the 'Programmer's Guide', only the 'External Graphics File Formats' page (in 'Graphics') remains to be completely filled in.fxm wrote:ProPgExecutables → fxm [page complemented]fxm wrote:I will perhaps soon (if no one does before) devote myself to completing the 'Executables' article in the 'Programmer's Guide' ('Making Binaries' section), from the above Jeff's posts and by synthesizing there only the information most useful to a programmer.
Are there any volunteers?
Re: Wiki improvements
@CoderJeff:
I do not understand this change:
(I'm not talking about the '= -2147483648' term which seems to be missing once in the second overload)
No problem for changing SCREENINFO and IMAGEINFO.
I do not understand this change:
compared to the present syntax:- Change overload for SCREENCONTROL( byval as const long, byref as long = -2147483648, byref as long = -2147483648, byref as long = -2147483648, byref as long = -2147483648 )
- Add overload for SCREENCONTROL( byval as const long, byref as longint, byref as longint = -2147483648, byref as longint = -2147483648, byref as longint = -2147483648 )
Most significant bit for the long default type passed to 1?declare sub ScreenControl ( byval what as long, byref param1 as integer = 0, byref param2 as integer = 0, byref param3 as integer = 0, byref param4 as integer = 0 )
declare sub ScreenControl ( byval what as long, byref param as string = "" )
(I'm not talking about the '= -2147483648' term which seems to be missing once in the second overload)
No problem for changing SCREENINFO and IMAGEINFO.
Re: Wiki improvements
In the LONG (or INTEGER<32>) versions of the functions, parameters are optional as per previous documentation:
- SCREENCONTROL(what [,param1 [,param2 [,param3 [,param4]]]] )
- SCREENINFO( [width [,height [,depth [,bpp [,pitch [,refresh_rate [, driver]]]]]]] )
- IMAGEINFO( img [,width [,height [,bpp [,pitch [,imagedata [,size]]]]]] )
In the LONGINT (or INTEGER<64>) versions of the functions, the first 2 or 3 parameters are not optional:
- SCREENCONTROL( what, param1 [,param2 [,param3 [,param4]]] )
- SCREENINFO( width, height [,depth [,bpp [,pitch [,refresh_rate [, driver]]]]] )
- IMAGEINFO( img, width, height [,bpp [,pitch [,imagedata [,size]]]] )
It must be this way so that the procedure overload between the LONG and LONGINT versions can be resolved.
From fbc sources:
- SCREENCONTROL(what [,param1 [,param2 [,param3 [,param4]]]] )
- SCREENINFO( [width [,height [,depth [,bpp [,pitch [,refresh_rate [, driver]]]]]]] )
- IMAGEINFO( img [,width [,height [,bpp [,pitch [,imagedata [,size]]]]]] )
In the LONGINT (or INTEGER<64>) versions of the functions, the first 2 or 3 parameters are not optional:
- SCREENCONTROL( what, param1 [,param2 [,param3 [,param4]]] )
- SCREENINFO( width, height [,depth [,bpp [,pitch [,refresh_rate [, driver]]]]] )
- IMAGEINFO( img, width, height [,bpp [,pitch [,imagedata [,size]]]] )
It must be this way so that the procedure overload between the LONG and LONGINT versions can be resolved.
From fbc sources:
Code: Select all
declare sub screencontrol overload _
( _
byval what as const long, _
byref param as string _
)
declare sub screencontrol overload _
( _
byval what as const long, _
byref param1 as long = &h80000000, _
byref param2 as long = &h80000000, _
byref param3 as long = &h80000000, _
byref param4 as long = &h80000000 _
)
declare sub screencontrol overload _
( _
byval what as const long, _
byref param1 as longint, _
byref param2 as longint = &h80000000, _
byref param3 as longint = &h80000000, _
byref param4 as longint = &h80000000 _
)
declare sub screeninfo overload _
( _
byref width as long = 0, _
byref height as long = 0, _
byref depth as long = 0, _
byref bpp as long = 0, _
byref pitch as long = 0, _
byref refresh_rate as long = 0, _
byref driver as string = "" _
)
declare sub screeninfo overload _
( _
byref width as longint, _
byref height as longint, _
byref depth as longint = 0, _
byref bpp as longint = 0, _
byref pitch as longint = 0, _
byref refresh_rate as longint = 0, _
byref driver as string = "" _
)
declare function imageinfo_ overload _
( _
byval img as const any ptr, _
byref width as long = 0, _
byref height as long = 0, _
byref bpp as long = 0, _
byref pitch as long = 0, _
byref imgdata as any ptr = 0, _
byref size as long = 0 _
) as long
declare function imageinfo_ overload _
( _
byval img as const any ptr, _
byref width as longint, _
byref height as longint, _
byref bpp as longint = 0, _
byref pitch as longint = 0, _
byref imgdata as any ptr = 0, _
byref size as longint = 0 _
) as long
Re: Wiki improvements
Thanks.