I’ve an Action that I’m debugging at the moment and the RPL Action is getting upset and throwing an error because of something my Action is doing. Here is a screen shot of RPL’s error; http://d.pr/i/bo04
For some reason the RPL Action is encoded so I can’t see what the issue may be. Softpress, is there any chance I can get a copy of the unencoded RPL Action please or, failing that, a list of the callbacks that the Action runs at? I’d rather not have to second guess these things if I can avoid it.
Thanks,
Tim.
Encoding could be used for two legitimate reasons that I can think of – source length reduction, to get around limitations in Freeway with regard to long Actions, or distribution to Express users. Every other Action I have seen come out of Softpress that was encoded was released for Express, and that was the only reason for that. In lieu of a more comprehensive API documentation, seeing how the experts in the long white coats do things is pretty much the only way to learn how to write more esoteric Actions. Joe, I know you sweated long and hard on this one, could you comment as to your (philosophical or practical) reasons for encoding?
Walter
On Nov 14, 2013, at 4:11 AM, Paul wrote:
The encoding of the RPL Action was a surprise to me. I was hoping it could have helped answer my recent DIV sizing questions too.
The Action does its stuff in the fwAfterEndBody callback. The code that’s producing the error is expecting there to be an internal indentation character at that position in the code. It essentially makes a check to see if the page is set to More Readable and uses that to move things around and add/remove any indentations that are required.
If your Action is also moving elements then it might be worth moving them after fwAfterEndBody, or moving them with their indentation characters (or adding the correct indentation to the things that you’re moving).
If that’s not what your Action is doing then I’d be happy to take a look at it for you and offer some other alternatives.
In answer to your question, Walter: the reason for making the RPL Action closed source is because the algorithm contained within it holds some value to us.
In answer to your question, Walter: the reason for making the RPL Action closed source is because the algorithm contained within it holds some value to us.