Page 1 of 1
Ruby: Error messages that don't help
Posted: Fri Jun 12, 2015 10:57 pm
by tulamide
- error_message.png (4.63 KiB) Viewed 7674 times
In this short example it is pretty obvious. The original int was converted to a float and now can't be represented as a hex string. But the error message is just annoying. Imagine you get this message, as happened to me, in a draw method filled with a few dozen of lines. Further imagine that you used a method to convert to strings of various forms, so that you don't have something like "drawString mynumber.to_s(16)", but "drawString mymethod". Still the error is reported for the draw method...
Took me half an hour to find the cause.
Re: Ruby: Error messages that don't help
Posted: Fri Jun 12, 2015 11:21 pm
by Nubeat7
trogs error tracing code snippet helps a lot to find the issues
viewtopic.php?f=3&t=1291and you can edit the ruby editclass to get the code with linenr
here is the topic:
viewtopic.php?f=2&t=2712&start=10after this was requested already a few times it really would be great to get line-numbers implemented in the ruby module in one of the next updates..
Re: Ruby: Error messages that don't help
Posted: Sat Jun 13, 2015 12:15 am
by tulamide
Nubeat7 wrote:trogs error tracing code snippet helps a lot to find the issues
viewtopic.php?f=3&t=1291and you can edit the ruby editclass to get the code with linenr
here is the topic:
viewtopic.php?f=2&t=2712&start=10after this was requested already a few times it really would be great to get line-numbers implemented in the ruby module in one of the next updates..
Thank you very much!
I always tend to believe that I'm the only one who is annoyed by something like that.
The other thing that bugs me is how easy you can destroy a working chain of RubyEdits by just inserting new ones, forcing you to re-arrange the whole chain. How cool it would be to have an id per RubyEdit that you can set yourself, and Flowstone loads them by id instead of where and when they were located...