CommonDialog crashes

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

   Using CJ v16.3 (but also happens on 13.0!)
When showing the Common Dialog on Windows 10 64bit in a skinned application, the application often crashes when the Common Dialog is opened/shown.
The first time a Common Dialog is shown (.ShowOpen) it can take up to 10 seconds, but then the Common Dialog crashes and so does the application.
Each next time the .ShowOpen is called the application crashes immediately.

It doesn't make any difference whether I use the MS Common Dialog or the CJ Common Dialog.

This does not happen on our own test machine running W10 64bit, but a lot of customers do experience this problem. On these machine showing the BrowseForFolder freezes the application, no matter if I use direct API calls or the CJ CommonDialog.

When creating a test application which does not do any skinning the problem does not occur.

Is there a way to exclude the CommonDialog and the BrowseForFolder dialog (either MS or CJ) from skinning?

On our own test machine the application works normally, but the CommonDialog has some strange glitches in the pathname, see the red circles.
For some reason "?" are shown in front of each directory name.

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
Arnoutdv Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 29 September 2010 Status: Offline Points: 38	Post Options Post Reply Quote Arnoutdv Report Post Thanks(0) Quote Reply Topic: CommonDialog crashes Posted: 18 October 2016 at 11:18am
	Using CJ v16.3 (but also happens on 13.0!) When showing the Common Dialog on Windows 10 64bit in a skinned application, the application often crashes when the Common Dialog is opened/shown. The first time a Common Dialog is shown (.ShowOpen) it can take up to 10 seconds, but then the Common Dialog crashes and so does the application. Each next time the .ShowOpen is called the application crashes immediately. It doesn't make any difference whether I use the MS Common Dialog or the CJ Common Dialog. This does not happen on our own test machine running W10 64bit, but a lot of customers do experience this problem. On these machine showing the BrowseForFolder freezes the application, no matter if I use direct API calls or the CJ CommonDialog. When creating a test application which does not do any skinning the problem does not occur. Is there a way to exclude the CommonDialog and the BrowseForFolder dialog (either MS or CJ) from skinning? On our own test machine the application works normally, but the CommonDialog has some strange glitches in the pathname, see the red circles. For some reason "?" are shown in front of each directory name.
	VB6 SP6, SuitePro 16.3.0 / 18.2.0, Win10/64

flowfact Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 04 August 2016 Status: Offline Points: 5	Post Options Post Reply Quote flowfact Report Post Thanks(0) Quote Reply Posted: 18 October 2016 at 11:20am
	Hi Arnoutdv, yes you can use m_oSkinFramework.ExcludeModule "test.dll"

olebed Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 01 July 2014 Location: Ukraine Status: Offline Points: 841	Post Options Post Reply Quote olebed Report Post Thanks(0) Quote Reply Posted: 18 October 2016 at 2:49pm
	Hi, may be this helps.

Arnoutdv Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 29 September 2010 Status: Offline Points: 38	Post Options Post Reply Quote Arnoutdv Report Post Thanks(0) Quote Reply Posted: 19 October 2016 at 3:40am
	As advised I'm going to add: SkinFrameWork.ExcludeModule "AcLayers.dll" I will report the results in this thread
	VB6 SP6, SuitePro 16.3.0 / 18.2.0, Win10/64