Click here to Skip to main content
15,891,943 members

Comments by MickFarrell (Top 14 by date)

MickFarrell 15-Apr-20 12:43pm View    
I agree, I'd rather double check than assume. We're going to roll back to the previous SDK's when the issue wasn't present and run some testing.

The whole project is made up of over 1 million lines of code with a mix of c, c++, clr, c#, .net, ASP.net and there's only about 10 places where this happens, and it only happens under very strange conditions that we haven't yet identified.

I do have a work around but I don't want to implement unless we really need to.
MickFarrell 15-Apr-20 10:56am View    
Yes it is the ID of the actual edit control and not the ID of a resource string.
MickFarrell 15-Apr-20 7:02am View    
All good points Steve, and yes the default is IDC_ I have tried adding a new edit control and left it at the default define IDC_EDIT and even the new edit control doesn't work. I'm pretty sure your suggestion would work, if I use the following code (added a CString) it works 100% of the time for all users:

void CUserPromptDlg::TestFunc1()
{
GetDisplayPrompt(m_UserPrompt);
CString temp = m_UserPrompt
SetDlgItemTextW(IDS_USER_PROMPT, temp);
}

I removed the AfxMessageBox(m_UserPrompt) as that is just for testing, it has no impact.

I think you may have been onto something with your previous question about the language and regional settings. We created a few new test accounts on Azure for some testers to test with.

Tester1 logs into Azure using an Azure user account "AzureTest1" and the text is missing.

Tester2 logs into the same Azure account "AzureTest1" and the text appears for him.

Tester1 used his second PC to log into Azure using the Azure account "AzureTest1" and the text appears.

It seems to be some how related to settings on a local PC been passed into the Azure account when logging in? They are checking local and regional settings to see if they can narrow it down

Thansk for your help and suggestions Steve!
MickFarrell 15-Apr-20 6:51am View    
Hi Richard, I've check to make sure that the IDS_USER_PROMPT id is unique and I have even added a new Edit box to the dialog to test and the text still appears blank in the new Edit box as well.

I did try using ::SetWindowText and ::SetWindowTextW (::SetWindowTextA won't compile as its a UNICODE project) and they both return true even when they don't display the text.

I have some of the testers doing some extensive testing on Azure and we did find something very interesting.

Tester1 logs into Azure using an Azure user account "AzureTest1" and the text is missing.

Tester2 logs into the same Azure account "AzureTest1" and the text appears for him.

Tester1 used his second PC to log into Azure using the Azure account "AzureTest1" and the text appears.

It seems to be some how related to settings on a local PC been passed into the Azure account when logging in? They are checking local and regional settings to see if they can narrow it down

Again thanks Richard for your time and input, its always very good to get some other ideas.






MickFarrell 15-Apr-20 4:27am View    
It is a unicode program so SetWindowText is SetWindowTextW. The SetWindowText (SetWindowTextW or SetWindowTextA) does not return a value. You're mixing up the win32 api ::SetWindowText (::SetWindowTextW or ::SetWindowTextA) which does return true or false.

You have givien me an idea, I will try calling the win32 version and see what it returns? thanks