The behavior of parameter processing for callmethod was intentionally changed in 5.5. I personally feel that the changes made things worse rather than better, but With felt that it now behaves more "correctly." Basically, it evaluates the parameters before passing them through. The other problem that you now have is if an parameter has a comma in it, this will be interpreted as two parameters. :(
The good news is that the call method action still works correctly. You can pass in parameters with single quotes and commas and such without a problem. So, the callmethod tag and the call method action behave differently. It's something that I have been frustrated with for a long time, but it will not likely be fixed since it's not considered to be broken. Stefan ---------------------------------------- From: Witango Talk <[email protected]> Sent: Wednesday, January 21, 2009 11:57 AM To: [email protected] Subject: SPAM-MED: Witango-Talk: 5.5 Server - Single Quote Issue With ActivePDF Toolkit Hello All, We're finally proceeding with an upgrade from 5.0 to 5.5. While testing and working through small fixes, I'm having an issue that I can't find a good work around for. Server setup is: Windows Server 2003Witango 5.5 ProfessionalActivePDF Toolkit We've used the same setup on Windows 2000 and 5.0 for years and all has been fine when working with the ActivePDF Toolkit. The issue is specifically with single quotes and the ActivePDF Toolkit COM Object. Using the <@CALLMETHOD> we call either GetTextWidth or PrintText and pass a variable that contains a single quote and an error will occur. Obviously, I can remove the single quote all together, but I need the character in there. I've tried all sorts of work arounds but nothing accomplishes the goal of having the single quote on the pdf. I can encode the string, but the activepdf doesn't decode it leaving the encoded value on the pdf. Was the COM interface changed in the upgrade from 5.0 to 5.5? Does anyone have any suggestions on a work around? Also, on a related subject, when we pass an empty string to the PrintText method, it displays as 6 questions marks on the pdf. This obviously looks like crap on the pdf. To work around that, I've written a <@IFEMPTY> check im the call and pass a <@CHAR CODE="32"> instead of the empty variable, but it's not feasible to do that with every application that uses the toolkit. Any ideas/help? Thanks, Dave Green ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
