hDC = GetDC(picBoxDisp);
/* Create a memory device compatible with the above DC variable*/
MemDCExercising = CreateCompatibleDC(hDC);
/* Select the new bitmap*/
/* Copy the bits from the memory DC into the current dc*/
BitBlt(hDC, 0, 0, 200, 200, MemDCExercising, 0, 0, SRCCOPY);
Images are displayed correctly but second image overlapps first...
I am creating a MFC application using VS2010 on WinXP.
i am using CFileDialog with Preview functionality while opening a file.It is working Fine in WinXP but in Win7,it is not showing any preview.
Do i need to change in MFC header Files? As I Found that,we need to chahnge #define WINVER to 0X501 from 0X00600. But I didnt get any clear result.
I derived class CFileDialog and Customize File Open Dialog by adding Preview option in OpenDialog[flags used OFN_ENABLETEMPLATE].
But this is not working in Win7.
I found on net tht we need to use Common File Dialog to Customize open File dialog in Windows7. But there should be way for Existing Applications which is using CFileDialog.
I have a 32-bit application that I've been maintaining for about 12 years and it runs on every Windows platform up to Windows 7. In all that time I've been using CWinApp::GetProfileXxxx() and CWinApp::WriteProfileXxxx() calls to read and write my program settings (about 70 settings) in the Registry. The settings are read from the Registry at start-up and written to the Registry when the program closes. There is also a method for the user to read and write the program settings to an INI file using the same code as the Registry access.
On my Windows 7 system the Registry read/write works just like it always has on all previous Windows versions. However, on some customer's Windows 7 machines there appears to be a problem with the Registry access. The program settings are either not being read from the Registry or are not being written to the Registry. I think the settings are not being written – but I don't know that. When the user uses the INI file the settings appear to be read and written.
The customer has complained a bit (I'd complain too) but doesn't have the time or doesn't want to take the time to run some simple tests for me to find out what's going on with his Windows 7 system.
So here is my question: Are there any user account settings or permissions that can block the program's access to the Registry? He claims he is an Administrator but I can't even get him to verify that.
I don't think UAC is the answer. I looked at my UAC settings and didn't see anything other than how to set the warning levels. Mine is set to: "Default: Notify me only when programs try to make changes to my compputer". Even with this setting my program never causes the UAC to display the notification.
I think the problem lies in the Registry p0ermission settings, but I don't know yet.
I KNOW I sould be looking at the customer's setting. The problem is that I'm not getting any support from him.
So, I need to understand the settings on my computer so I can run some tests and make suggestions to him. My problem is that I'm not very well versed in "security" settings in Windows 7. I still think it is a user permission setting in Registrey - but I'm not sure where to look yet.
The Registry key permission setting does indeed stop my program from writing to its Registry key. On my two WinXP and my Win7 systems the Registry key permissions are set to "full control".
Registry editor does not allow me to manually change the "full control" permission to "Read". The "full control" permission is checked but disabled (dimmed) so I can't change it and I don't know why. I had to find a utility that changed the permission outside of registry editor. When the key permission was changed to "read" then writing to the Registry failed.
CWinApp:WriteProfileInt() fails with a "read" permision but there is no error code associated with the failure (i.e. GetLastError() doesn't return an error code).
I think the only thing I can do is detect the Registry write failure, report it to the user, and use an INI file instead of the Registry. I don't particularily like it but I think that's my only choice.
When changing permissions on registry keys using regedit, make sure you select your user name to see which permissions you have. Programmatic changes to the registry are done using either your user account or the system user account, or some similar named account on the system. My bet is that the read or write permission is not set for all the accounts on your system. This is easy to check, open your regedit, navigate to the key in question, right click the key, select permissions. This should show a registry permissions dialog. Select each user account on the top section of the dialog and watch how the related permissions change for the different accounts. When you find the account with the missing permission, you will have your culprit. Hope this helps.
I'm wanting to batch edit the ID3V2 tags in around 1660 CDs worth of tracks, as I have metadata stored elsewhere.
Part of this process involves adding a APIC tag with the contents of a JPEG file.
Now, I have jumped through the various hoops to get everything working except one thing, namely, the artwork. Everything else (genre, album, track number, etc) work fine, and the tags are visible to iTunes and Windows Media Player. However, I am stumped as to how to add the artwork
I thought that the sequence
TagLib::ID3v2::Tag*t = f.ID3v2Tag();
// code omitted to initialise the ByteVector of data from file (which I checked!)
TagLib::ID3v2::AttachedPictureFrame* pF = new TagLib::ID3v2::AttachedPictureFrame();
should work, but it does not save my artwork
If anyone has working C++ code that does work, I'd be very grateful.
The jpeg image is bigger than the Picture Control, and the jpeg file is in the local disk. It is no problem to show jpeg image, I can use the CImage to load the jpeg image and then user Picture Control's SetBitmap() method to display this image.
of-course yes. You can invoke a modal dialog from another modal dialog. Coming to your problem there is something wrong with the usage of CFileDialog. can you paste the complete exception stack/message so that we can able find what went wrong.
I took this sample from here[^] hope you are doing the same. if not give a try.
dlgFile.GetOFN().lpstrFile = fileName.GetBuffer(<very large number&>);
dlgFile.GetOFN().nMaxFile = <very large number >;
INT_PTR nResult = dlgFile.DoModal();
Read these lines carefully
The destruction of CFileDialog objects is handled automatically. It is not necessary to call CDialog::EndDialog.
To allow the user to select multiple files, set the OFN_ALLOWMULTISELECT flag before calling DoModal. You need to supply your own filename buffer to accommodate the returned list of multiple filenames. Do this by replacing m_ofn.lpstrFile with a pointer to a buffer you have allocated, after constructing the CFileDialog, but before calling DoModal.
When the user allocates their own buffer to accommodate OFN_ALLOWMULTISELECT, the buffer can't be larger than 2048 or else everything gets corrupted (2048 is the maximum size).
Additionally, you must set m_ofn.nMaxFile with the number of characters in the buffer pointed to by m_ofn.lpstrFile. If you set the maximum number of files to be selected to n, the necessary buffer size is n*(_MAX_PATH + 1) + 1.
You are using the _T() macro in some places to ensure your strings are correctly created as ASCII or Unicode. However, further down you are using the (LPCTSTR) cast. This means that your code should not even compile in Unicode mode. You also failed to tell us what the exception is that you are seeing.
So you think that randomly changing some strings to Unicode will fix the problem? My comment was made in the hope that you would actually think about what you are trying to do and whether your various parameters are correct. Read the documentation[^] and look more closely at the requirements for the different parameters on the CFIleDialog class.
You should also learn the difference between the _T() macro and the L prefix on strings. And finally you need to understand exactly what a cast, such as (LPCTSTR), does and how it affects the way your program runs.
When the user clicks the OK button, they are expecting to be done, not be presented with yet another dialog box. The OK button should not be available to click until all required information has been collected. It sounds like what you need is a Browse button to allow browsing for the file name.
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"Show me a community that obeys the Ten Commandments and I'll show you a less crowded prison system." - Anonymous