Defect Name: XML File In Glyph
Detailed Defect Description: Write a glyph that will read data from a file in XML format and convert to a format suitable to be used as a SourceGlyph.
Steps to Recreate the Defect: N/A Enhancement
Possible/Suggested Resolution: Create a glyph similar to the CFileInGlyph and add code to convert between XML format and TIP format.
Submitted by: Unknown Student
Status: OPEN
Priority: LOW
Defect Name: XML File Out Glyph
Detailed Defect Description: Write a glyph that will convert data in TIP format to XML format and store it in an ASCII file.
Steps to Recreate the Defect: N/A Enhancement
Possible/Suggested Resolution: Create a glyph similar to the CFileOutGlyph and add code to convert between XML format and TIP format.
Submitted by: Unknown Student
Status: OPEN
Priority: LOW
Defect Name: Move handlers from TipView to TipDoc
Version: 1.40
Detailed Defect Description: There are a bunch of methods in CTipView that really belong in CTipDoc as they have to do with file related data.
Steps to Recreate the Defect: N/A Enhancement
Possible/Suggested Resolution: Elimnate from CTvipView and move to CTipDoc. Make sure the Message_Map is modified correctly.
Submitted by: The Doctor
Status: CLOSED
Priority: Low
Defect Name: Opening workspace and compiling errors
Version: TIP 1.40
Detailed Defect Description: With Microsoft Developer Studio 97 (Visual C++ 5.0) unable to open workspace correctly and unable to compile TIP 1.40 program.
Steps to Recreate the Defect: Opening the file "Tip.dsw" created a warning dialog to be opened stating the following: "Cannot recognize the current ClassView Information (.NCB) file format. Would you like to overwrite the file?" The dialog also contained the the choices of Yes or No. Choosing Yes allows the workspace to be opened. Then when choosing to build the project the following error is created: "~\Tip\stdafx.h(19) : fatal error C1083: Cannot open include file: 'afxdtctl.h': No such file or directory"
Possible/Suggested Resolution: Improve Documentation to resolve question of ClassView Information (.NCB) and if MS VC++ 6.0 is necessary to compile.
Submitted by: Todd Krahenbuhl
Status: OPEN
Priority: Low
Defect Name: Processing Glyph Crash
Version: Tip 1.40
Detailed Defect Description: If you connect a processing glyph to the display glyph and attempt to Run System, the program will crash.
Steps to Recreate the Defect: 1.) Open Tip 2.) Create a new Processing Glyph (I used Summer) 3. Connect the processing glyph to the display glyph 4. Attempt to run the system.
Possible/Suggested Resolution: I think that it crashes because the summer has no input. A simple solution would be to check to see whether there is input before it runs.
Submitted by: Jason DeCock
Status: OPEN
Priority: Medium
Defect Name: Unable to use Delete button to delete a Glyph
Version: TIP 1.41
Detailed Defect Description: In TIP version 1.41, the only way to delete a selected glyph is to right click and select the "delete glyph" choice.
Steps to Recreate the Defect: 1.) Open TIP 2.) Select glyph to delete and press the "Delete" key
Possible/Suggested Resolution: Add ability to delete a selected glyph using the delete key
Submitted by: Anders Wiborg
Status: OPEN
Priority: Medium
Defect Name: Bounds checking on Amplitude of SineWaveGlyph.
Version: 1.41
Detailed Defect Description: After connecting a sine wave to a plotting device and double clicking on the sine wave icon, one can change the amplitude. If a very large value is placed in the amplitude the graph will not appear (for obvious reasons). The coordinates display odd characters and the plotter displays weird qualities.
Steps to Recreate the Defect: Simply connect a sine wave to a plotter and place an extremely large value in the field, i.e. 1e+9999.
Possible/Suggested Resolution: Possible bounds check on all fields to make sure abnormal values aren't entered.
Submitted by: Alex Withers
Status: OPEN
Priority: Medium
Defect Name: An ambiguous message box for FileOut Glyph
Version: 1.42
Detailed Defect Description: When outputting to a file, an ambiguous message box appears to indicate the file's creation. It would be more user-friendly if it would state which file was created and in what directory it was stored. Along the same lines, it would be nice if Tip gave the user the option to rename an output file if it already exists.
Steps to Recreate the Defect: Generate an 'out' glyph and use this as a destination to connect from any graph. Then run the system
Possible/Suggested Resolution: Modifications should be made to the FileOutGlyph and FileOutDialog implementation files. There should be only simple modifications by proceeding with the following steps: 1) Go to the code where the message box is actually created 2) Specify it to output a more meaningful message 3) If an absolute path was not specified for the output file location, the programmer should give the path of the default directory where the output file was sent. 4.1) This will probably done in the Parameters function Inside of FileOutGlyph.cpp 4.2) Giving the user the opportunity to rename the file if it is used will probably occur in Parameters() as well.
Submitted by: Andy Kim
Status: OPEN
Priority: LOW
Defect Name: Zoom Issue
Version: 1.42
Detailed Defect Description: The line that the plotter shows does not stay within the cartesian plane defined in the window when somebody zooms in.
Steps to Recreate the Defect: 1. Start Tip 2. connect the default source glyph to the default display glyph and run the connection. 3. click the zoom in button on the plotter. once should be sufficient to cause the defect.
Possible/Suggested Resolution: Try modifying CPlotterDialog to show the line only within the cartesian plane in the window.
Submitted by: Rafael Pozos
Status: OPEN
Priority: High
Defect Name: Plotter Overload Crash
Version: 1.41
Detailed Defect Description: When five or more inputs are connected to a plotter, the program crashes when run. With only four devices connected, a strange blip shows up in the plotter's output (at the far left or beginning of the plot). Either a mixture of processing glyphs and sources, all sources, and all processing glyphs will overload the plotter.
Steps to Recreate the Defect: 1. Create five sine wave sources. 2. Create a plotter glyph. 3. Connect each source to the glyph and run the system.
Possible/Suggested Resolution: The problem likely resides within the CPlotterGlyph runGlyph(). One might limit the user from over four connections to a plotter Glyph if it is not possible to expand this limit.
Submitted by: : Jeff Rice
Status: OPEN
Priority: Medium
Defect Name: The graph created when plotting has no scale markings or labels for the axes
Version: 1.42
Detailed Defect Description: when running the system from any glyph or sequence of glyphs to the plotter, on the resulting "Graph Signals" dialog box there are neither scale markings for the x or y axis, or labels describing what the x and y axes represent
Steps to Recreate the Defect: Run the system with any glyphs to the plotter
Possible/Suggested Resolution: The CPlotterDialog is displayed after the user runs the system, so it is likely that the 'defect' could be resolved by adding code here to display the needed information
Submitted by: Ian May
Status: OPEN
Priority: Medium
Defect Name: Sometimes not allowed to connect between glyphs
Version: 1.42
Detailed Defect Description:
Steps to Recreate the Defect:
Possible/Suggested Resolution:
Submitted by: Ryan Hutcherson
Status: OPEN
Priority: Low
Defect Name: The two glyph colors
Version: 1.42
Detailed Defect Description: The two colors chosen for the glyphs, green and yellow, could be improved to make the program look better and more pleasing to the eye
Steps to Recreate the Defect: Run the program, create a green glyph, then create a yellow glyph, repeat as many times as wanted, and observe that the colors could be chosen better to interact.
Possible/Suggested Resolution: in the Draw() function, maybe choose two colors that coincide better, like red/blue, blue/green, or some other combination of the sorts
Submitted by: Jason Hamilton
Status: OPEN
Priority: Medium
Defect Name: Unable to use any commands from the "Edit" menu.
Version: 1.42
Detailed Defect Description: Cannot cut, copy, paste objects in TIP, or undo actions.
Steps to Recreate the Defect: 1. Create a Glyph in TIP. 2. Try to copy, cut, or paste the object, or perform and action and try to undo it using the corresponding options from the "Edit" Menu. Notice that none of the Edit menu controls are activated.
Possible/Suggested Resolution: Implement methods such as "OnUndo," "OnCut" etc. to handle the Edit menu options.
Submitted by: Katya Craven
Status: OPEN
Priority: Medium
Defect Name: Not Enough Hot Keys
Version: 1.42
Detailed Defect Description: Since there is no real typing involved, and the standard SAVE, PRINT, NEW, and OPEN functions already have ctrl+key hot keys, there should be a way to add each of the glyphs to the field with just the keyboard. Suggestions include using just plain characters, S for Sine Wave Glyph, P for plotter, etc. A single hot key for toggling select / deselect should also be included. Maybe even the spacebar could be used for this. A single hot key for making a connection should also exist. Also, one other suggestion would be to have the TAB key cycle through the glyphs on the field in the order they were placed / added.
Steps to Recreate the Defect: None.
Possible/Suggested Resolution: CGlyphs, and every specific Glyph Class
Submitted by: Andy Dentone
Status: OPEN
Priority: Medium
Defect Name: Poor color choice for two waves on same graph.
Version: 1.42
Detailed Defect Description: When two waves are displayed on the same graph, with different frequencies, it is hard to see the second wave due to it's faint green color.
Steps to Recreate the Defect: Connect two waves to the same plotter glyph. Choose different values for frquency by double clicking on the wave glyphs. Then plot the graph.
Possible/Suggested Resolution: The color can be changed in the class CPlotterDialog . Here is the line where the color is selected within the function plotData. plotPen1.CreatePen( PS_SOLID, 1, RGB(0,255,0) );
Submitted by: Chris Burdick
Status: OPEN
Priority: Medium
Defect Name: In-line Help
Version: 1.42
Detailed Defect Description: The program itself doesn't offer any instructions or help in properly using the software.
Steps to Recreate the Defect: N/A
Possible/Suggested Resolution: Add another item to the menu toolbar, that offers help to the user. This could be as simple as providing the direction for the user to examine the readme.txt file. Of course a readme file would need to be created that documents basic operations of the software, along with possibly further explanation on where there is common confusion.
Submitted by: Jameus Hutchens
Status: OPEN
Priority: Medium
Defect Name: Plotter Window Resize
Version: 1.42
Detailed Defect Description:
Steps to Recreate the Defect:
Possible/Suggested Resolution:
Submitted by:
Status: OPEN
Priority: Medium
Defect Name: Blue sine wave that is hardly distinguishable from the
centered dashed line.
Version: 1.42
Detailed Defect Description: It is really hard to distinguish between a blue sine wave with an amplitude of 20 or more and a blue dashed line in the center.
Steps to Recreate the Defect: 1. connect 3 sine glyphs to the plotter 2. one of the waves will be blue. Change the amplitude on the glyph that displays the blue sine wave to 20 or more 3. notice that it is hardly distinguishable from the blue dashed line in the center.
Possible/Suggested Resolution: Change the color of the dashed line or do not display the sine wave in blue.
Submitted by: Lana Slisenko
Status: OPEN
Priority: Medium
Defect Name: File In browser
Version: 1.42
Detailed Defect Description: When the user wishes to use the File In button, the user needs to know the exact name and path of the input file. It would be much easier if a browse window was available for the user to utilize in finding the proper input file. For example, if a file was saved as "friday3.tip", but the user comes back Monday and can't remember the name, the saved file is useless to the user.
Steps to Recreate the Defect: Add a File In Glyph. Double-click on it. Notice the absence of a browse window.
Possible/Suggested Resolution: Add to the File In Glyph a browse button, which opens up a browse window that can be used by the user to find *.tip files. Use a CSpecialFileDialog, as used in the "Tools | Delete *.tip Files" menu.
Submitted by: Andrew Bennett
Status: OPEN
Priority: Medium
Defect Name: Delete all TIP *.tip System Files dialog aesthetics
Version: 1.42
Detailed Defect Description: The Delete all TIP *.tip System Files dialog box has a Files of type click-down (pull-down) menu which displays nothing, this should either be removed or possibly have a message saying To be added soon. But from the nature of this dialog window it sounds as if this widget is completely useless since it will be just be *.tip files deleted
Steps to Recreate the Defect: click Tools -> Delete *.tip Files and then look for the extra file type pull-down menu with nothing in it.
Possible/Suggested Resolution: Editing this resource and removing this window item from it
Submitted by: Jim Donnelly
Status: OPEN
Priority: Medium
Defect Name: "In data file" glyph
Version: 1.42
Detailed Defect Description: Description: The "In data file" glyph doesn't check for valid existing files.
Steps to Recreate the Defect: Put a test for a valid file name in the code where the infile is read from.
Possible/Suggested Resolution: not sure
Submitted by: Kelly Hiltner
Status: OPEN
Priority: Medium
Defect Name:
Version: 1.42
Detailed Defect Description:
Steps to Recreate the Defect:
Possible/Suggested Resolution:
Submitted by:
Status: OPEN
Priority: Medium
Defect Name:
Version: 1.42
Detailed Defect Description:
Steps to Recreate the Defect:
Possible/Suggested Resolution:
Submitted by:
Status: OPEN
Priority: Medium
Defect Name:
Version: 1.42
Detailed Defect Description:
Steps to Recreate the Defect:
Possible/Suggested Resolution:
Submitted by:
Status: OPEN
Priority: Medium
Defect Name:
Version: 1.42
Detailed Defect Description:
Steps to Recreate the Defect:
Possible/Suggested Resolution:
Submitted by:
Status: OPEN
Priority: Medium
Defect Name:
Version: 1.42
Detailed Defect Description:
Steps to Recreate the Defect:
Possible/Suggested Resolution:
Submitted by:
Status: OPEN
Priority: Medium
Defect Name:
Version: 1.42
Detailed Defect Description:
Steps to Recreate the Defect:
Possible/Suggested Resolution:
Submitted by:
Status: OPEN
Priority: Medium
Defect Name:
Version: 1.42
Detailed Defect Description:
Steps to Recreate the Defect:
Possible/Suggested Resolution:
Submitted by:
Status: OPEN
Priority: Medium
Defect Name:
Version: 1.42
Detailed Defect Description:
Steps to Recreate the Defect:
Possible/Suggested Resolution:
Submitted by:
Status: OPEN
Priority: Medium
Defect Name:
Version: 1.42
Detailed Defect Description:
Steps to Recreate the Defect:
Possible/Suggested Resolution:
Submitted by:
Status: OPEN
Priority: Medium
Defect Name:
Version: 1.42
Detailed Defect Description:
Steps to Recreate the Defect:
Possible/Suggested Resolution:
Submitted by:
Status: OPEN
Priority: Medium