> I use some ACCESS and ASSIGN statements in an interface for my Graphics4VO > DLL like this:
> _DLL ACCESS Background CLASS > gFormPushButton:graphlib.gFormPushButton:Background:ACCESS
> This works fine in VO27. But in VO28 an error message comes up when I start > the executable which is using the DLL:
I take it this is a manually written _DLL line?
Are you sure the case of that line is the same in Vo27 and VO28?
Are you sure the case of line it refers to is the same in Vo27 and VO28?
Have you used a tool like depends to check?
> one other thing I have tried in the past with various versions of VO
> is to touch the problem entity and recompile in case it forgot to export > it.
I have checked this. The bug is still present.
Now I installed Dependency Walker. Viewing the GRAPHLIB.DLL for VO28 I found the following entrence:
107 (0x006B) 106 (0x006A) gFormPushButton:Background:Access 0x000BAE4C
>> one other thing I have tried in the past with various versions of VO
>> is to touch the problem entity and recompile in case it forgot to export >> it.
> I have checked this. The bug is still present.
> Now I installed Dependency Walker. Viewing the GRAPHLIB.DLL for VO28 I found > the following entrence:
> 107 (0x006B) 106 (0x006A) gFormPushButton:Background:Access 0x000BAE4C
> "ACCESS" is here written as "Access". Is that ok?
That is the problem. I am less sure what the fix is given what you have
said.
I tried it! When disabeling Tool / Options / Editor / Intellisense / Keyword Case to "None", the word "Access" is not be redisigned to uppercase letters. When trying to run my application using the DLL interface no error comes up anymore.
So we found a real bug in VO28: In _DLL statements the keywords ACCESS and ASSIGN may not be case dependent!
The next problem: Ones changed Tools / Options / Editor / Intellisense / Keyword Case to "None" it is not possible to change it back to "Upper case" or to "Lower case". Any ideas?
This behavior is not only in VO2.8; but it is in all VO-version.
Let me explain: You have generated the code automaticly, and then you
have copy/paste this code. During the paste operation, uppercasing is
done (which is the problem).
Disabling the words ACCESS and ASSIGN to automaticly uppercasing is not
a good idea.
Maybe disabling the :ACCESS and :ASSIGN is a better idea.
how to do the disabling of the strings ":ACCESS" and ":ASSIGN" ?.
Fred
--
Fred Killet
killet-nos...@killetsoft.de
"Dirk (Belgium)" <dirk.dot.herijg...@pbprojects.dot.be> schrieb im Newsbeitrag news:k5j4tc$gjv$1@dont-email.me...
> This behavior is not only in VO2.8; but it is in all VO-version.
> Let me explain: You have generated the code automaticly, and then you
> have copy/paste this code. During the paste operation, uppercasing is
> done (which is the problem).
> Disabling the words ACCESS and ASSIGN to automaticly uppercasing is not
> a good idea.
> Maybe disabling the :ACCESS and :ASSIGN is a better idea.
> Dirk (Belgium)
> =======================
> Fred Killet wrote:
>> Hello,
>> I use some ACCESS and ASSIGN statements in an interface for my
>> Graphics4VO DLL like this:
>> _DLL ACCESS Background CLASS
>> gFormPushButton:graphlib.gFormPushButton:Background:ACCESS
>> This works fine in VO27. But in VO28 an error message comes up when I
>> start the executable which is using the DLL:
>> "The procedure entrence point 'gFormPushButton:Background:ACCESS'
>> could not found in the DLL 'graphlib.DLL'".
>> Is that an bug in VO28? Is there a workaround? Thank you for your
>> help.
