| Author |
 Topic  |
|
|
AGL
New Member
Russia
8 Posts |
 Posted - Mar 01 2006 : 01:47:12 AM
|
Hi
There some problems with TLI\\TLH files in VAX 1440 under VS6.
I import into my project 3'rd party TLB and I've got pair of files - TLI and TLH.
1.
VAX cant find any interfaces from TLH at all.
I've solved this problem using plug:
// qqq is not declared anywhere but causes VAX to parse them
#ifdef qqq
#include " ....tlh" // direct path to imported TLH file
#include " ....tli" // direct path to imported TLI file
#endif
2.
My result TLH file contains about 220000 lines. All declarations below 65535 line can't be met by "GoTo" command. But declarations in "goto" context menu are shown correctly.
3.
When I open these TLI\\TLH files in editor WAV become inactive |
|
|
feline
Whole Tomato Software
United Kingdom
18941 Posts |
Posted - Mar 01 2006 : 7:13:04 PM
|
| what are these TLI \\ TLH files? are they standard C++ source code, or something else? is it possible for me to download one or two of these files so i can test this here? |
zen is the art of being at one with the two'ness |
 |
|
|
bugfix
Tomato Guru
Germany
324 Posts |
Posted - Mar 02 2006 : 01:29:15 AM
|
Those files are generated via #import "somecom.dll" statement and by default are put in debug/release folder of project.
-bugfix |
http://www.mf-sd.de |
|
|
|
AGL
New Member
Russia
8 Posts |
Posted - Mar 02 2006 : 01:36:53 AM
|
.. of course
RxInventor.tlb for API of "Autodesk Inventor" product.
These headers were gotten by #import directive.
TLH is available at
_http://slil.ru/22590501
and TLI at
_http://slil.ru/22590509
I want emphasize that I use only #import directive, not #include. Compiler of VC6 can't correctly accept such large files when specified #include for TLH/TLI. |
|
|
|
feline
Whole Tomato Software
United Kingdom
18941 Posts |
Posted - Mar 04 2006 : 11:37:06 AM
|
the download keeps on failing. would it be easier for me to download the Autodesk API / SDK directly? or is it not feely available?
if it is easier i will email you via the forum and then you can reply with these two files zipped up and attached. |
zen is the art of being at one with the two'ness |
|
|
|
AGL
New Member
Russia
8 Posts |
Posted - Mar 09 2006 : 02:39:25 AM
|
Autodesk not allow to download SDK TLB directly from its WEB until you is not member of Autodesk Developers Network (ADN).
I can send packed files directly to you via e-mail or by other way you want. |
|
|
|
feline
Whole Tomato Software
United Kingdom
18941 Posts |
Posted - Mar 09 2006 : 5:00:33 PM
|
| i have emailed you via the forum, if you reply to that email any attachments should reach me just fine. |
zen is the art of being at one with the two'ness |
|
|
|
feline
Whole Tomato Software
United Kingdom
18941 Posts |
Posted - Mar 20 2006 : 7:35:42 PM
|
i have got the email, and the attachment. i have now been able to reproduce this problem despite the problems i had at first.
case=1061 |
zen is the art of being at one with the two'ness |
|
|
|
AGL
New Member
Russia
8 Posts |
Posted - Mar 27 2006 : 10:59:24 PM
|
One problem more persists in VAX when C++ projects use TLB libraries.
If some projects in solution/workspace use the same TLB,
which imported with the same options,
VAX parses them separately, and every time when rebuild was made.
Can VAX parse TLB only once if it was imported with the same options
in some projects (exactly configurations).
For example, we use solution with 40 projects.
5 projects in solution (each have 4 configuraions) import the same TLB
('RxInventor.tlb' which I sent to you recently).
When I press GoTo button, VAX hangs process for a tens of minutes.
|
|
|
|
feline
Whole Tomato Software
United Kingdom
18941 Posts |
Posted - Mar 28 2006 : 3:47:51 PM
|
interesting. can you open the OFIW dialog please, and see if it lists any files? if the dialog is empty and the title bar says "parsing..." then VA is still parsing. however if you see the files then the main parsing phase has finished.
i am guessing that parsing is not causing this problem, but obviously something is. have you ever left VA long enough for it to start responding again? |
zen is the art of being at one with the two'ness |
|
|
|
AGL
New Member
Russia
8 Posts |
Posted - Mar 29 2006 : 01:08:24 AM
|
I can't reproduce it right now, because such parsing happens not so predictable.
But I remember that IDE is hanged (may be because TLH and TLI files is about 10mb of size).
Yes, I left VAX to parse completely all what it wants.
Next opening of the same solution was over normally.
Now I use another method...
I kill process of IDE when VAX begins parsing everything in trash directories.
Then I start IDE again and open the same solution.
In this case VAX works normally too. |
|
|
|
feline
Whole Tomato Software
United Kingdom
18941 Posts |
Posted - Mar 29 2006 : 4:59:12 PM
|
| i have emailed support, to see if they have any ideas on this. |
zen is the art of being at one with the two'ness |
|
|
|
support
Whole Tomato Software
5566 Posts |
Posted - Mar 29 2006 : 10:23:40 PM
|
Assuming VA X can find the dll, it normally generates and parses TLH/TLI automatically when it sees a #import.
feline noted the bug with Goto not going beyond 65535. You seem to have a performance problem as well.
We tried your example on a slow PC. We #included Debug/RxInventor.tlh and tried Goto from a few symbols. It tooks VA X only a few seconds to make the jump. (A little faster in forthcoming beta builds.)
Can you press Rebuild on the Performance node of our options dialog? Restart the IDE, reopen your workspace and wait for parsing to finish. Try a Goto into the tlh.
Send your license info to us the info from the About node of our options dialog if you still have a problem. Use the Copy Info button. Include all info. |
Edited by - support on Mar 29 2006 10:27:41 PM |
|
|
| |
Topic |
|
Problems with TLI/TLH files
