Reporting doc bugs short of Github, as in 'version'

Working group for improving LiveCode's User Guide, Dictionary, and other learning resorces.

Moderators: Klaus, FourthWorld, heatherlaine, kevinmiller, robinmiller

Post Reply
srdlrtr
Posts: 6
Joined: Thu Apr 11, 2013 1:29 pm

Reporting doc bugs short of Github, as in 'version'

Post by srdlrtr » Tue Mar 07, 2017 2:12 am

Maybe I've just missed it, but I didn't see a means of reporting errors in the Livecode documentation (or for suggestions) short of navigating GitHub. For those of us who were attracted to then-Revolution, one of the advantages was that we didn't have to dedicate that amount of time for simple tasks -- and if our primary job wasn't programming, keep up with tools like GitHub. Older versions had a section for user comments in the dictionary, but I don't see it now.

For example, I just noticed that in the dictionary entry for the function 'version', the example says"
if item 1 of the version < 3 then
answer "Not all features will be available"
end if

It looks like whoever provided the example expected the version to be separated by commas, so item 1 would be a single numerical value and the comparison would succeed. But the version number is actually separated by periods, so item 1 is the entire version string-- and not considered a number because it has two periods. LiveCode consequently does an alphabetic comparsion -- which is fine when the version number is "8.1.1" but not so good when it's "10.1.1".

My quick and dirty hack is
(char 1 to 3 of the version) div 1
(which works up to version 999.99.99) but others might have a better solution.

FourthWorld
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 5386
Joined: Sat Apr 08, 2006 7:05 am
Location: Los Angeles
Contact:

Re: Reporting doc bugs short of Github, as in 'version'

Post by FourthWorld » Tue Mar 07, 2017 2:30 am

srdlrtr wrote:Maybe I've just missed it, but I didn't see a means of reporting errors in the Livecode documentation (or for suggestions) short of navigating GitHub.
Gothub would be where you'd go to fix a bug. To report one please use the bug database - "Documentation" is a category you can set in a new report:
http://quality.livecode.com/
Richard Gaskin
Community volunteer LiveCode Community Liaison

LiveCode development, training, and consulting services: Fourth World Systems: http://FourthWorld.com
LiveCode User Group on Facebook : http://FaceBook.com/groups/LiveCodeUsers/

srdlrtr
Posts: 6
Joined: Thu Apr 11, 2013 1:29 pm

Re: Reporting doc bugs short of Github, as in 'version'

Post by srdlrtr » Tue Mar 07, 2017 5:45 am

Thanks.

Did the report.

FourthWorld
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 5386
Joined: Sat Apr 08, 2006 7:05 am
Location: Los Angeles
Contact:

Re: Reporting doc bugs short of Github, as in 'version'

Post by FourthWorld » Tue Mar 07, 2017 7:26 am

Others interested in this topic will find the bug report ID very helpful so they can follow its progress.
Richard Gaskin
Community volunteer LiveCode Community Liaison

LiveCode development, training, and consulting services: Fourth World Systems: http://FourthWorld.com
LiveCode User Group on Facebook : http://FaceBook.com/groups/LiveCodeUsers/

srdlrtr
Posts: 6
Joined: Thu Apr 11, 2013 1:29 pm

Re: Reporting doc bugs short of Github, as in 'version'

Post by srdlrtr » Tue Mar 07, 2017 7:53 am

OK,

For anyone interested, it's ID 19377.

Post Reply

Return to “Learning Resources”