Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
User name:
Password:
Save Password
Forgot your password?

 All Forums
 Visual Assist
 Technical Support
 VAX 1239: new project - just 3 files
 New Topic  Topic Locked
 Printer Friendly
Author Previous Topic Topic Next Topic  

Uniwares
Tomato Guru

Portugal
2321 Posts

Posted - Jun 10 2004 :  7:40:03 PM  Show Profile
When you create a new project under VC6, any type of project it seems, the Open File in Workspace dialog shows only 3 files: Stdafx.cpp, Stdafx.h, Readme.txt

support
Whole Tomato Software

5566 Posts

Posted - Jun 10 2004 :  11:37:37 PM  Show Profile
One file is always missing from the OFIW dialog. On the list to fix.

Click the File heading in the OFIW dialog to reverse the sort order. You see the missing file.

case=123

Whole Tomato Software, Inc.
Go to Top of Page

Uniwares
Tomato Guru

Portugal
2321 Posts

Posted - Jun 11 2004 :  01:37:28 AM  Show Profile
Right. Uhm...
Go to Top of Page

LarryLeonard
Tomato Guru

USA
1041 Posts

Posted - Jun 11 2004 :  07:24:52 AM  Show Profile
Okay, let me state the obvious... shouldn't there be lots of files, not just three (or, four)? Like, say, 12 or so? Two for the app, two for the doc, two for the view, two for stdafx, two for the mainframe, an RC, RC2, and a resource.h file, for example?
Go to Top of Page

support
Whole Tomato Software

5566 Posts

Posted - Jun 11 2004 :  12:01:44 PM  Show Profile
We create a new project in VC++ 6.0 with File|New, a "MFC AppWizard (exe)", in a new workspace and take all the defaults. We wait a few seconds for the IDE to create all files. We open our OFIW dialog and have a dozen+ files.

We intercept the "new project" command and when it completes, we reparse the project. Hmm... How could we miss something.

If you open the OFIW dialog before the project is created, or while it is being created, you get a partial list. (Clicking a column heading in the dialog prods VA X to reread the list of files in the project.)

Whole Tomato Software, Inc.
Go to Top of Page

LarryLeonard
Tomato Guru

USA
1041 Posts

Posted - Jun 11 2004 :  8:12:32 PM  Show Profile
You know, it seems like bad things can happen if we use certain VAX features before the parsing is finished. Is there any way you could disable these features until they're ready to be used? Imagine the frustration that new customers are going to have...
Go to Top of Page

support
Whole Tomato Software

5566 Posts

Posted - Jun 11 2004 :  8:50:15 PM  Show Profile
We agree. We are likely to disable OFIW until parsing is complete.

case=14

Whole Tomato Software, Inc.
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
18939 Posts

Posted - Jun 14 2004 :  06:28:06 AM  Show Profile
could you make the parsing more obvious? for me, winXP pro, VS .NET 2003 and VAX 1239 the status bar often goes blank during parsing. after perhaps a second or two messages about parsing reappear on the status bar.

as a result i am not sure when parsing has finished...

thinking that parsing has finished, and then finding that VAX wont respond as i expect, since it is still silently parsing is rather unhelpful ;)

zen is the art of being at one with the two'ness
Go to Top of Page

support
Whole Tomato Software

5566 Posts

Posted - Jun 14 2004 :  1:05:07 PM  Show Profile
We agree that it would be nice if the status bar were updated more descriptively. Unfortunately, the IDE writes to the bar as well -- and we cannot interfere with its writing. The IDE does not expect we are there.

We will be as clever as we can when we solve the OFIW problem.

Whole Tomato Software, Inc.
Go to Top of Page

Uniwares
Tomato Guru

Portugal
2321 Posts

Posted - Jun 14 2004 :  7:11:11 PM  Show Profile
Then just blank out the dialogs and controls, show a hint that parsing is not completed.
Or, add a status pane with progressbar to show the progress of VAX's parsing. There is lots of space in the status bar.
Go to Top of Page

Stephen
Tomato Guru

United Kingdom
781 Posts

Posted - Jun 15 2004 :  06:10:35 AM  Show Profile
I have a related comment. It's not even clear that the parsing messages come from VA not VS, unless one is already familiar with VS without VA. The text should indicate this somehow.

Stephen Turner
ClickTracks http://www.clicktracks.com/
Winner: ClickZ's Best Web Analytics Tool 2003 & 2004
Go to Top of Page

WannabeeDeveloper
Tomato Guru

Germany
775 Posts

Posted - Jun 15 2004 :  07:14:06 AM  Show Profile
Maybe you should just create a small Modal DialogBox with a Progressbar in it showing the status of parsing?

My PC (P4 1.8) cannot be used when VAX parses heavily through all files/headers, so I'm sitting there useless anyway...


Edited by - WannabeeDeveloper on Jun 15 2004 07:14:42 AM
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
18939 Posts

Posted - Jun 15 2004 :  08:22:11 AM  Show Profile
if you have the VAX wizard bar turned on, which most people will, you could change the colour and style of the "Go" button to show that VAX is still working.

obvious enough to be clear, especially if it is explained in the documentation for new users. since this is fully under VAX's control, no conflicts. also, it has the benefit of not intruding, unlike a dialog box.

of course, if you don't use the VAX wizard bar then this is no help. anyone here turn off the wizard bar? off hand i don't see any good reason to do so.

zen is the art of being at one with the two'ness
Go to Top of Page

support
Whole Tomato Software

5566 Posts

Posted - Jun 15 2004 :  7:02:21 PM  Show Profile
We will look for something clever. Many of the obvious choices are unavailable since we don't own the display. We are not exactly supposed to be doing any of the stuff we do.

First on the list from this thread is improving the OFIW dialog. One option is to make the dialog unavailable until parsing is complete.

Whole Tomato Software, Inc.
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
18939 Posts

Posted - Jun 16 2004 :  07:04:00 AM  Show Profile
if you make it unavailable, the instant result is going to be stream of bug reports saying that the OFIW dialog is broken...

you either need to replace it with a message box saying "this is not available until parsing is complete, VAX is currently n% of the way through parsing this project", assuming you know how far through you are.

alternatively you could load the OFIW dialog, but put a big comment to the same effect inside, instead of the file list.

remember, you will need to do the same for the file list in VA View

presumably the same restriction applies to the symbols in workspace as well, both on the toolbar and in VA View.

as for not supposed to be doing these things, don't own up to then

zen is the art of being at one with the two'ness
Go to Top of Page

support
Whole Tomato Software

5566 Posts

Posted - Oct 04 2004 :  5:38:04 PM  Show Profile
Fixed in build 1272.

OFIW dialog populates when parsing is done.
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Topic Locked
 Printer Friendly
Jump To:
© 2023 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000