Code parser - CoasterBuzz

Maybe this is already fixed in the new version...

But adding URLs is infuriating on an iPad because the iOS auto correct and the syntax requirements of the parser are at odds with one another. While clearly it is Apple that has it wrong here, it might be easier to "fix" the parser...

Problem #1: The URL directive
No, dammit, it isn't URL, it is url, and iOS seems dead set on preventing me from typing it as url. URL, as it turns out, does not work in the current code.

Problem #2: No space before =
Not only does iOS recognize URL as a word and "correct" it to upper case, it also insists on adding a space if you type "url=". So you get "URL =" instead, which does not work.

It seems to me that because the token is enclosed in square brackets, it ought to be possible to be slightly more forgiving about case and formatting.

(of course, if iOS offered cursor movement buttons it would also help tremendously...)

--Dave Althoff, Jr.

    /X\        _      *** Respect rides. They do not respect you. ***
   /XXX\      /X\     /X\_      _     /X\__      _     _        _____
  /XXXXX\    /XXX\   /XXXX\_   /X\   /XXXXX\    /X\   /X\      /XXXXX
_/XXXXXXX\__/XXXXX\/XXXXXXXX\_/XXX\_/XXXXXXX\__/XXX\_/XXX\_/\_/XXXXXX

RideMan said:
cursor movement buttons

This is perhaps my biggest gripe with touchscreen devices.

Don't worry, auto-correct override (and/or full input replacement apps) and precise cursor placement is now commonplace in the android world, which means that Apple should be introducing these as groundbreaking, revolutionary upcoming iOS features... any day now.

Obligatory ;)

Last edited by BBSpeed26,

Bill
ಠ_ಠ

I'll send Steve Jobs a memo.

Jeff - Editor - CoasterBuzz.com - My Blog