Obscuring text for Password entry

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   I am trying to cause a password to be obscured using asterisks using CXTPReportRecordItemEditOptions and setting 
m_pEditOptions->m_dwEditStyle |= ES_PASSWORD;

Has anyone any advice on how I can get the toolkit to take notice of this ?

Thanks

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
vernonr Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 08 May 2006 Status: Offline Points: 7	Post Options Post Reply Quote vernonr Report Post Thanks(0) Quote Reply Topic: Obscuring text for Password entry Posted: 04 August 2006 at 12:40pm
	I am trying to cause a password to be obscured using asterisks using CXTPReportRecordItemEditOptions and setting m_pEditOptions->m_dwEditStyle \|= ES_PASSWORD; Has anyone any advice on how I can get the toolkit to take notice of this ? Thanks

vernonr Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 08 May 2006 Status: Offline Points: 7	Post Options Post Reply Quote vernonr Report Post Thanks(0) Quote Reply Posted: 10 August 2006 at 4:27am
	Eventually solved this problem myself.....!! as no replies received ... Not simple as Codejock buried the instantiation of CXTPReportInplaceEdit within CXTPReportRecordItem, and lots of functions in both call GetCaption for the string to display. Whilst it is possible to obscure the string - you actually need to blank the obscured string before allowing an edit - otherwise addition of characters in middle of string can cause havoc. Brief Outline... There derive subclasses from CXTPReportRecordItem ( overriding the classes that refer to the edit control ) . Derive a subclass from CXTPReportInplaceEdit and override the create function to call GetStartEditCaption - which returns a blank CString for a password, and the normal GetCaption() a non password. You'll need to adjust the class friends to get rid of linkage errors as well.. Don't use CXTPReportRecordItemText. Cheers