Dear Mary,

@7-Jan-2006, 16:58 -0600 (07-Jan 22:58 here) Mary Bull [MRB] in
mid:[EMAIL PROTECTED] said to Marck:

>> https://www.ritlabs.com/bt/view.php?id=4933

>> This issue has been a complete PITA for me since it started playing
>> up. It goes under the caption "Big problem with To field in QTs".

>> The bug is nasty because there's not even a work-around for it.
>> Nothing will let me assign the To header once it gets to a certain
>> depth of nested operation.

MRB> Then Miguel suggested in mid:[EMAIL PROTECTED]

MRB> "What about %SetHeader('To','[EMAIL PROTECTED]')? It is working for me."

MRB> And you reported that you'd tried it and the work-around fixed your
MRB> problem.

Admirably.

MRB> My question is: Did you have to re-do all your QT nested templates for
MRB> the Address Book after the first appearance of the bug in v. 3.51.4?

I had to correct every template that used the "%TO=...." construct.

MRB> A friend has lost all the carefully customized nested QTs by upgrading
MRB> to v. 3.64.03 from the Christmas Edition 3.64.01.

That would be some other effect than the bug we were discussing.

MRB> Dropping back from the new beta still left all the customized, nested
MRB> QTs missing.

Yes, I would expect so. It sounds like a bad file write or otherwise
corrupted QT store files.

MRB> NB to Stefan Tanurkov, to whom this open BT issue report is
MRB> listed as assigned: Are you working on the bug right now--it's
MRB> sort of serious for the more advanced users of The Bat! Has been
MRB> lurking around since July 18, 2005.

Yes. About that.

-- 
Cheers --  //.arck D Pearlstone -- List moderator and fellow end user
TB! v3.64.04 Christmas Edition on Windows XP 5.1.2600 Service Pack 2
'

Attachment: pgpEZCOVCZduQ.pgp
Description: PGP signature

________________________________________________________
 Current beta is 3.64.03 | 'Using TBBETA' information:
http://www.silverstones.com/thebat/TBUDLInfo.html
IMPORTANT: To register as a Beta tester, use this link first -
http://www.ritlabs.com/en/partners/testers/

Reply via email to