Forum Replies Created
-
AuthorPosts
-
KevinBParticipant
Whenever I would try to rebuild after getting the error the build would just fail again. However I've rebuilt the 12.12 version of AC and it is now building just fine in release mode. So maybe something just went wrong when initially building AC and I was using a faulty .bpl file. I'll let you know if I start getting this error again though.
Thanks!
Kevin
KevinBParticipantCode:[BCC32 Fatal Error] TSetupWizardForm.cpp(145): F1004 Internal compiler error at 0x9300d99 with base 0x92b0000This is the error that I get. When I double click on the error it brings me to a section of code that works with PNG images, so maybe it's something with the acPNG package? When I build in Debug mode everything works fine and I don't get this error. The file that the error points to also had an issue that I previously reported. Even though this was fixed a few versions ago, this may have something to do with this issue since they both involve the PNG images.
Thanks!
KevinBParticipantI just downloaded the newest version (12.08) and it looks like you guys fixed the problem. Thanks for your help!
KevinBParticipantHere are some screenshots of the same area of our software with a light and dark skin. Also, to clarify, those are TsLabels and their Caption text is the text that isn't getting updated.
KevinBParticipant'Support' wrote:The issue must be fixed in the v12.07 already.
Check it, please.
Just tried it out with v12.07 and it is indeed fixed! Thank you for your help!
KevinBParticipantThis capture is from a previous build of our software and the image has the intended transparency. The method used to display the images and the images themselves haven't changed at all but the transparency stopped working when we updated from 10.15 to 11.21.
Thanks!
KevinBParticipantSorry for taking so long to get back to this. Here's an example project of this. Again I'm using version 11.21 of Alpha Controls.
Thanks for your help!
KevinBParticipant'Support' wrote:Hello!
Reasons of these issues are different.
Try to use the sSkinManager1.Options.StdImgTransparency property, this solution must work in your case, I think.
I've tried using that but that still won't fix the issue. Are there any other properties that need to be set in the ImageList for that to work? For some more context, we're using the GetBitmap32 method to load the images in the list into an empty image in our form. I've tried setting the transparency of the image to true, I've tried different drawing styles for the image list and different blend colors and different bk colors but none of that has fixed it.
KevinBParticipant'Support' wrote:Do you mean – after the window with a file preview closing? And when the main window is activated?
Yes, that is what I mean.
KevinBParticipantSo the access violation actually occurs after the new file is closed. So maybe it is even with the underlying Windows function for closing windows? It seems to only happen when our application is maximized as well when opening the new file. And to be more specific the actual method call we are using is
Code:int hResult = (int)ShellExecuteW(Application->Handle, NULL, objectPath.c_str(), NULL, NULL, SW_SHOWNORMAL);It appears to happen more frequently when on a Windows 10 machine. It will happen on a Windows 7 machine but not nearly as often. It may sound silly too but if the access violation doesn't occur when first opening the new file I was able to get it to appear by spamming the maximize then restore down button of the window many times then closing the window when it's maximized.
Hopefully this helps, if there is anything else you need to know hopefully I can give you an answer.
Thanks!
Kevin
November 29, 2016 at 12:08 am in reply to: ExtendedBorders property causing EAccessViolations #55787KevinBParticipant'Support' wrote:Hello, Kevin!
This exception occurs when document is generated and opened for preview?
Could you show a screeshot of this preview form without extended borders?
So we're not necessarily opening the file for preview. We are using the Windows ShellExecute function to open the new files. So the files aren't shown within any Alpha Controls form but are opened in whatever default program the specific file type opens in.
-
AuthorPosts