| T O P I C R E V I E W |
| ajtruckle |
Posted - Dec 16 2009 : 3:07:01 PM
Hi again
:(
I have installed vs2005 and latest vax onto a windows 7 computer.
Just created a new dialogue application.
I added two folders (F: drive) to the application preferences for include and libraries.
Even after full symbol build I get no IS40 or ISE40 functions identified.
I did discuss this before and I have forgotten the ABC of fixing the problem. Did I have to add something to a file? Did I have to put the libraries on C drive?
I can send the test app. Sorry about this.
Andrew |
| 17 L A T E S T R E P L I E S (Newest First) |
| ajtruckle |
Posted - Mar 04 2010 : 2:18:30 PM
Maybe you can talk to Chris at smaller animals about it .... Agree a macro that you will support ... |
| feline |
Posted - Mar 04 2010 : 1:59:30 PM
I agree. I am unsure about this change though. The first two additions were:
#define _ISFnDeco(functionName) functionName
#define _ISEFnDeco(fn) fn
and these are fairly uncommon looking macro names. The odds of them causing problems is quite small. In contrast "_ISFn()" does not sound so unique or safe. I am concerned about fixing this library but breaking some other library at the same time. |
| ajtruckle |
Posted - Mar 02 2010 : 4:38:35 PM
You recently added the new macros yourself to the stdafx to support imgsource4. I was merely pointing out the slight adjustment/addition needed for imgsource5. So if you want to maintain support for imgsource5 then you know what adjustment to make.
Andrew |
| feline |
Posted - Mar 02 2010 : 3:27:42 PM
As explained here:
http://docs.wholetomato.com?W302
the copy of VA's StdAfx.h file in the user directory is used instead of the default version of the file if found.
I am a little concerned about adding a #define for _ISFn to the default VA StdAfx.h file since this is a much shorter macro name, and may be more likely to cause unexpected problems. Also if you are using a user copy of VA's StdAfx.h file changes to the default StdAfx.h file are not going to have any effect for you.
Thank you for the update, it is good to know that you have found a solution, and what the solution is. |
| ajtruckle |
Posted - Feb 28 2010 : 12:42:16 PM
OK, maybe it was because I had my own stdaf.h file too in my user folder?
Will that always take precedence?
I added
#define _ISFn(fn) fn
to that file and rebuilt.
OK now.
Was that reason?
Please add #define _ISFn(fn) fn
for imgsource5 support to vax for me.
Thanks.
and please confirm if existence of stdafx in user folder supercedes contents of program files.
Andrew |
| ajtruckle |
Posted - Feb 28 2010 : 12:10:28 PM
Aparently these macros evaluate to nothing for "static libraries" which is what I am using.
So a typical function is defined like this in header files of image source 5:
_ISDeclSpec BOOL _ISCConv _ISFn( is5_OverlayImage )(void *pBottom, UINT32 uBottomWidth, UINT32 uBottomHeight, UINT32 uChannelsPerPixel, UINT32 uBottomRowStride, void *pTop, UINT32 uTopWidth, UINT32 uTopHeight, UINT32 uTopRowStride, __int32 iXPos, __int32 iYPos, double fOpacity, double fK, UINT32 uMode, UINT32 uFlags);
So the function and all parameters are there. Ideas? |
| ajtruckle |
Posted - Feb 28 2010 : 11:34:38 AM
The imgsource5 header has this:
#define _ISCConv __stdcall
#ifdef __cplusplus
#define EXTERNC extern "C"
#else
#define EXTERNC extern
#endif
#ifdef IS50_USING_DLL
// all DLL functions are prefixed with "_" . ex. _is5_ReadJPG
# define _ISFn(fn) _##fn
// functions look like this:
// _ISDeclSpec returnType _ISCConv _ISFn(fnName)(...)
# if !defined(_ISDeclSpec)
// **ONLY** define IS50_BUILD_DLL if you are building the DLL from source
# if defined(IS50_BUILD_DLL)
# define _ISDeclSpec EXTERNC __declspec(dllexport)
# else
# define _ISDeclSpec EXTERNC __declspec(dllimport)
# endif
# endif
#else
// for static lib building and usage, these macros do nothing
# define _ISFn(fn) fn
# define _ISDeclSpec EXTERNC
#endif
So I tried to add _ISFn(fn) fn to your stdafx.h and do rebuild but no joy. |
| ajtruckle |
Posted - Feb 28 2010 : 10:52:55 AM
OK, I have aanother problem.
I just upgraded to ImgSource 5 and all functions start is5_...
The function declaractions seem no different in the headers:
_ISDeclSpec HGLOBAL _ISCConv _ISFnDeco( is5_Function )(int param1, BYTE *param2);
But I don't understand why my is5_ methods won't display or show as functions. I have altered the directories.
I am using your latest version which has the imgsource macro code in the stdafx.h file.
Andrew |
| ajtruckle |
Posted - Jan 31 2010 : 1:50:02 PM
Excellent!
Thanks. |
| support |
Posted - Jan 31 2010 : 1:35:45 PM
case=37158 addresses support for ImgSource and ISEffects libraries, and is implemented in build 1810 |
| accord |
Posted - Dec 19 2009 : 1:55:13 PM
I am glad it works 
EOL is required is case=25876 and we are planning to ship Visual Assist with ImgSource and ISEffects support. |
| ajtruckle |
Posted - Dec 19 2009 : 07:55:32 AM
Thumbs up!! I recall our discussion and forgot about this trailing line. Maybe you can fix that for future release. Also, maybe you should add these macro defenitions for bespoke support for ImgSource and ISEffects.
But it works now after a symbol build. Thanks.
Andrew |
| accord |
Posted - Dec 18 2009 : 5:07:32 PM
Here is the workaround:
Place these lines into VA's stdafx.h:
#define _ISFnDeco(functionName) functionName
#define _ISEFnDeco(fn) fn
Make sure you press enter after the second line. You can learn more about VA stdafx.h here:
http://docs.wholetomato.com?W302
In the another topic that I had linked, feline suggested the same workaround for ImgSource, now I extended the solution for ISEffects. Originally the workaround did not work for you and the solution wasn't documented. We discussed this problem with feline and her idea is that maybe your stdafx.h did not contain trailing blank line (it causes problem for the parser).
So to sum up I hope it will work now |
| ajtruckle |
Posted - Dec 17 2009 : 2:08:58 PM
Sent it |
| feline |
Posted - Dec 17 2009 : 1:59:51 PM
How large is the zip file you are trying to upload with the form?
You can delete the .NCB file in the root directory of the solution, and normally the release and debug directories as well, which should leave you with a small solution that should upload quickly and easily. |
| ajtruckle |
Posted - Dec 17 2009 : 04:12:27 AM
I just tried to send you my project using that form and it seemed to time out.
Andrew |
| accord |
Posted - Dec 16 2009 : 5:31:25 PM
I found a topic with workaround:
http://forum.wholetomato.com/forum/topic.asp?TOPIC_ID=8607
Does this topic help? If not, or you see other problems, you can send the test project you had mentioned to us using this form:
http://www.wholetomato.com/support/contact.asp
Please include the ULR of this thread in the description so we can match it up. |
