Jeff Massung wrote:
Honestly, this is something that's always urked me about Rev. With [almost]
everything else being so user-friendly, error reporting is definitely not
one of them. How hard could it possibly be to convert that into object,
function name, line #?
Yeah, I've never seen anyone
On 11/30/10 12:13 PM, Jeff Massung wrote:
Honestly, this is something that's always urked me about Rev. With [almost]
everything else being so user-friendly, error reporting is definitely not
one of them. How hard could it possibly be to convert that into object,
function name, line #?
In the I
Hi Ton,
the dictionary says:
You can look up the description of an error using this line of code:
answer line (item 1 of line 1 of pExecutionError) of the cErrorsList of card 1
of stack "revErrorDisplay"
Best regards,
Harald Müller.
| Harald Müller (www.etcpp.de)
| Theodor-Körner-Straße 4, 97
Honestly, this is something that's always urked me about Rev. With [almost]
everything else being so user-friendly, error reporting is definitely not
one of them. How hard could it possibly be to convert that into object,
function name, line #?
Jeff M.
On Tue, Nov 30, 2010 at 11:05 AM, Ton Cardo
Hi Ton,
You can enter those numbers here
http://runrev.info/error.html
--
Best regards,
Mark Schonewille
Economy-x-Talk Consulting and Software Engineering
Homepage: http://economy-x-talk.com
Twitter: http://twitter.com/xtalkprogrammer
KvK: 50277553
How to receive a free Color Converter licens
Could you tell me where I can find an understandable explanation of errors
reported as number. For example this one:
141,91,17
465,91,1
Thanks in advance
Ton
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscri
