GapiDraw 3.6 Issues
Posted: May 27, 2006 @ 4:39amPage 1 of 1
Posted: May 27, 2006 @ 4:39amPosted: May 28, 2006 @ 11:17pmPosted: May 31, 2006 @ 8:16amThanks for the feedback. I will investigate.
Posted: Jun 4, 2006 @ 7:10amPosted: Aug 8, 2006 @ 4:13amPosted: Aug 17, 2006 @ 2:26pmPosted: Aug 17, 2006 @ 11:26pmOk for all you reading this post (620 reads so far) weare working on resolving these issues. Most of them have been resolved this far and we will shortly release an update to GapiDraw: 3.6a which also includes a fix for the Moto Q device.
Current status:
1. Release notes has now been updated.
2. I could not make a solution to GapiApplication that compiles without warnings on lvl4. If anyone has a solution to this please feel free to send me a PM.
3. I cannot reproduce these issues. All samples compile very clean in my Visual Studio 2005 environment. Anyone else who can reproduce this?
4. This error is caused if you use the RELEASE DLL of Visual Studio 2005 PC in a DEBUG build of the sample file. We will in GapiDraw 3.6a include a DEBUG build of GapiDraw for Visual Studio 2005 PC which resolves this issue.
//Johan
Current status:
1. Release notes has now been updated.
2. I could not make a solution to GapiApplication that compiles without warnings on lvl4. If anyone has a solution to this please feel free to send me a PM.
3. I cannot reproduce these issues. All samples compile very clean in my Visual Studio 2005 environment. Anyone else who can reproduce this?
4. This error is caused if you use the RELEASE DLL of Visual Studio 2005 PC in a DEBUG build of the sample file. We will in GapiDraw 3.6a include a DEBUG build of GapiDraw for Visual Studio 2005 PC which resolves this issue.
//Johan
Posted: Aug 20, 2006 @ 10:43amOk we just released GapiDraw 3.6a today which resolves some of these issues and more.
Current status:
1. Release notes has now been updated.
2. GapiApplication now compiles with no warnings when warning level is set to W4.
3. There were some debugging info remaining in the release build which has now been removed, which should cause GapiDraw to compile more nicely.
4. This issue was caused by using GapiDraw as a DLL and making a DEBUG build of an application in a stationary PC environment. Since GapiDraw was built in Release mode this caused memory issues. GapiDraw 3.6a now includes DEBUG DLL files, using one of these files will remove this memory issue.
//Johan
Current status:
1. Release notes has now been updated.
2. GapiApplication now compiles with no warnings when warning level is set to W4.
3. There were some debugging info remaining in the release build which has now been removed, which should cause GapiDraw to compile more nicely.
4. This issue was caused by using GapiDraw as a DLL and making a DEBUG build of an application in a stationary PC environment. Since GapiDraw was built in Release mode this caused memory issues. GapiDraw 3.6a now includes DEBUG DLL files, using one of these files will remove this memory issue.
//Johan
Posted: Aug 21, 2006 @ 7:35amYep, 3.6a addresses these issues. Yay, thanks Johan! You can compile Minimal on warning level 4 cleanly if you modify the Minimal project properties as follows:
General > Whole Program Optimization: Use Link Time Code Generation
C/C++ > Debug Information Format : Program Database (/Zi)
Linker > Ignore Specific Library: MSVCRT
Linker > Enable Incremental Linking: Default (no)
(Thus far I've only tried out Minimal. It'll be a few days before I have a chance to try retrofitting my hobby project.)
General > Whole Program Optimization: Use Link Time Code Generation
C/C++ > Debug Information Format : Program Database (/Zi)
Linker > Ignore Specific Library: MSVCRT
Linker > Enable Incremental Linking: Default (no)
(Thus far I've only tried out Minimal. It'll be a few days before I have a chance to try retrofitting my hobby project.)
Posted: Aug 21, 2006 @ 9:13pmThanks for these tips. 
I'm gonna modify the sample projects and upload an updated version of 3.6a.
I'm gonna modify the sample projects and upload an updated version of 3.6a.