| Author |
 Topic  |
|
|
WannabeeDeveloper
Tomato Guru
Germany
775 Posts |
 Posted - Jun 10 2004 : 04:47:28 AM
|
Hi!
Still have some problems/bugs in 1239:
1.) type #in, completion-box shows #include <-?> and #include "-?".
choose the first one (with the '<>') using the TAB key and you get #include <> | where | is the caret (with a tabulator between > and the caret).
Needless to say that no Header-Files are suggested when you manually put the caret between the <> afterwards.
1.b) Yesterday, I was typing re (completion offering return), I chose it with TAB and got rereturn. Possibly related, but I cannot reproduce it...
2.) Sometimes, when I add new controls to my dialogs in the VS .NET Dialog-Editor and use the ID's in my sourcecode, they are not colored right. Even reparsing the File manually doesn't help. Only after opening the "resource.h" manually, all newly added ID's become colored right. Not good... |
 |
Edited by - WannabeeDeveloper on Jun 10 2004 04:49:03 AM |
|
|
support
Whole Tomato Software
5566 Posts |
Posted - Jun 10 2004 : 12:08:27 PM
|
1) Is the problem reproducable? We cannot make it happen. In fact, our first suggestion is always #include "".
Ctrl+Space inside <> should open list.
1b) Do you suspect the rereturn problem is timing related?
2) Probably the same problem as this:
http://forum.wholetomato.com/forum/topic.asp?TOPIC_ID=2345
|
Whole Tomato Software, Inc. |
 |
|
|
WannabeeDeveloper
Tomato Guru
Germany
775 Posts |
Posted - Jun 10 2004 : 3:43:35 PM
|
1) Definitely it is! But sometimes it works, while the other time it behaves as described. I'll let you know if timing could be involved... I always happens with the <>-variant (never with the "" include).
1b) could be. I think it happened yesterday for the first time. Cannot remember of any other occurrence...
2) Probaby, yes. Quite annoying, as I relate on VAX very much. I always get nervous if if doesn't color my defines right. I always tend to look for the error on my end... |
|
|
|
|
support
Whole Tomato Software
5566 Posts |
Posted - Jun 10 2004 : 6:35:54 PM
|
1) Does the <> variant always appear first in the suggestion list? We still cannot make that happen. We toggle "Include Autotext...", "Suggest bits", tweak the templates file, type in different places in the source.
2) We are likely to deal with symbols-in-cpp-only, aka I-need-to-update-resource.h, in the next few builds. |
Whole Tomato Software, Inc. |
|
|
|
WannabeeDeveloper
Tomato Guru
Germany
775 Posts |
Posted - Jun 11 2004 : 02:07:05 AM
|
quote:
Originally posted by support
1) Does the <> variant always appear first in the suggestion list? We still cannot make that happen. We toggle "Include Autotext...", "Suggest bits", tweak the templates file, type in different places in the source.
Not sure, don't nail me on the "appears first in the list"-part.
With "choose the first one (with the '<>')" I meant the first one mentioned by me in the thread. I did NOT mean it appears first in the suggestion List. The Bug is another one (using the TAB key and you get #include <> | where | is the caret (with a tabulator between > and the caret)).
|
|
|
|
|
support
Whole Tomato Software
5566 Posts |
Posted - Jun 11 2004 : 11:30:19 AM
|
We are still unable to reproduce the problem. We type #in and get a suggestion listbox, ie with tomatoes, and use Down Arrow/mouse to select the <> entry. We press Tab. We get the caret between the <>.
Does Templates\\CPP.tpl look okay? It should have two entries for #in that specify where the caret goes.
Do you have "Suggest bits" and/or "Include autotext" enabled on the Completion node of our options dialog? |
Whole Tomato Software, Inc. |
|
|
|
WannabeeDeveloper
Tomato Guru
Germany
775 Posts |
Posted - Jun 11 2004 : 1:41:07 PM
|
Jup, the TPL looks okay:
readme:
Autotext and Code Templates for Visual Assist X
caretPosChar:
-?
#u:
#undef
#p:
#pragma
#in:
#include "-?"
#in:
#include <-?>
#im:
#import "-?"
#im:
#import <-?>
#if:
#ifdef -?
#endif
#ifn:
#ifndef -?
#endif
#el:
#else
#eli:
#elif
#en:
#endif
Both Options are set/enabled.
I think I found it (reproducable)!
Go to the VERY FIRST LINE of the CPP-File and test again.
Everytime I try, I get the wrong behaviour! |
|
|
|
|
support
Whole Tomato Software
5566 Posts |
Posted - Jun 11 2004 : 9:02:52 PM
|
D'oh! That's it.
Obviously, workaround is to type your #include on the second line of your file. 
Problem exists in VS.NET only.
case=126 |
Whole Tomato Software, Inc. |
|
|
| |
Topic |
|
Topic Locked
