Wiki improvements

Forum for discussion about the documentation project.
Post Reply
coderJeff
Site Admin
Posts: 4313
Joined: Nov 04, 2005 14:23
Location: Ontario, Canada
Contact:

Re: Wiki improvements

Post by coderJeff »

See, FBWIkiHelp
And especially, FBWikiPageNames
The only style so far is for keyword pages is FBRikiTopicSample
Wiki formatting codes is supposed to be at FormattingRules but is blanked out -- need to go through the revisions and remake that page.
For experimentation, very acceptable to play around in SandBox

Short answer is:
CatPg* pages are for categories organizing other pages
If you want to add information, in this case, for AndAlso, OrElse, you should add the information on those pages.
MrSwiss
Posts: 3910
Joined: Jun 02, 2013 9:27
Location: Switzerland

Re: Wiki improvements

Post by MrSwiss »

coderJeff, thank you. The *FormatingRules*-page was, what I've been looking for.
The page exists, but is empty. :-(
(I've checked the link from: FBWikiHelp)

I'll have a look at sandbox ...
> If you want to add information, in this case, for AndAlso, OrElse, you should add the information on those pages.
Even if the comment would apply to both? Or a whole bunch, at a CatPg...? (just hypothetically asking, currently)
coderJeff
Site Admin
Posts: 4313
Joined: Nov 04, 2005 14:23
Location: Ontario, Canada
Contact:

Re: Wiki improvements

Post by coderJeff »

OK, I added:
FBWikiFormatting, which will document the formatting code to use in the wiki. The fbdoc tool that generates the manual won't accept everything. This is a work in progress.

WikkaFormattingRules, the original FormattingCodes that was provided by the wiki software when last updated, for reference.

It's a work in progress. Apologies if links and/or formatting codes are not all valid. The goal will be to make it correct before next release of the FB manual.
MrSwiss
Posts: 3910
Joined: Jun 02, 2013 9:27
Location: Switzerland

Re: Wiki improvements

Post by MrSwiss »

Great start ... re-enables, the "comunity effort" on the Wiki. Thanks a lot.
sancho3
Posts: 358
Joined: Sep 30, 2017 3:22

Re: Wiki improvements

Post by sancho3 »

I have fixed the links in tutorial "Using Libraries".
However I cannot fix the code as I am not familiar with any of the libraries.
All the code examples contain problems.

I added the clip parameter to the syntax/usage in tutorial "Using the Mouse in FreeBasic"
dodicat
Posts: 7976
Joined: Jan 10, 2006 20:30
Location: Scotland

Re: Wiki improvements

Post by dodicat »

You forgot to mention that to use getmouse in a Win 10 console (Which most folk's use now I believe), you must first un-check Quick edit mode.
Otherwise a great disappointment looms heavily.
fxm
Moderator
Posts: 12081
Joined: Apr 22, 2009 12:46
Location: Paris suburbs, FRANCE

Re: Wiki improvements

Post by fxm »

Not only since Win 10, but at least since Win XP.
dodicat
Posts: 7976
Joined: Jan 10, 2006 20:30
Location: Scotland

Re: Wiki improvements

Post by dodicat »

Thanks fxm.
I checked my old xp box, it was set as quick edit mode off as default.
But My Win 10 is the opposite.

Of course, I have no intention of adding my md5 to the long list of technical authors, so my rants are not significant.
sancho3
Posts: 358
Joined: Sep 30, 2017 3:22

Re: Wiki improvements

Post by sancho3 »

I actually have no idea what quick edit mode is.
But doesn't this line in this tutorial cover it?
IMPORTANT: It is mandatory that you set yourself in a graphic mode in order to use the mouse. the mouse commands will always return -1 for a value if the graphic mode is not set.

If not then can you write up a line that is more accurate I will add it.

I would also appreciate if someone familiar with the libraries in the other tutorial could rework the code snippets and I will change them.
Alternatively maybe that tutorial should just be scrapped?
dodicat
Posts: 7976
Joined: Jan 10, 2006 20:30
Location: Scotland

Re: Wiki improvements

Post by dodicat »

Right click the console frame
properties
You will see quick edit mode.

This line:
IMPORTANT: It is mandatory that you set yourself in a graphic mode in order to use the mouse. the mouse commands will always return -1 for a value if the graphic mode is not set.

(What is a graphic mode exactly -- a graphics screen??)
I don't know what the line means.

Console:
(if you un-check QuickEdit mode, it should work)
Except the wheel is not showing. (win 10)

Code: Select all

dim as integer x,y,b,w
do
    cls
getmouse x,y,w,b
locate 2,2
print x,y,w,b
sleep 1
loop until len(inkey) 
fxm
Moderator
Posts: 12081
Joined: Apr 22, 2009 12:46
Location: Paris suburbs, FRANCE

Re: Wiki improvements

Post by fxm »

dodicat wrote:Console:
(if you un-check QuickEdit mode, it should work)
Except the wheel is not showing. (win 10)
I thought the wheel worked in windowed mode (and not in full screen mode).
This is true at least for Win 7 (I can not test that on my Win 10 PC currently)
dodicat
Posts: 7976
Joined: Jan 10, 2006 20:30
Location: Scotland

Re: Wiki improvements

Post by dodicat »

Both console modes here have no wheel.
MrSwiss
Posts: 3910
Joined: Jun 02, 2013 9:27
Location: Switzerland

Re: Wiki improvements

Post by MrSwiss »

sancho3 wrote:Alternatively maybe that tutorial should just be scrapped?
Yes, I think so too, it's ancient and, not even written by forum member(s).
(It's from some Journal, about QB, aka: missing relevance to FB: -lang FB).
fxm
Moderator
Posts: 12081
Joined: Apr 22, 2009 12:46
Location: Paris suburbs, FRANCE

Re: Wiki improvements

Post by fxm »

dodicat wrote:Both console modes here have no wheel.
On my PC with Win 10, the mouse wheel works in windowed console mode.
dodicat
Posts: 7976
Joined: Jan 10, 2006 20:30
Location: Scotland

Re: Wiki improvements

Post by dodicat »

If I go down to legacy console the wheel works.
I cannot get a full screen in this mode though.
I have code page 850, maybe something to do with that.
Post Reply