Difference between revisions of "Assignment 2 (Release 0.1): Q & A"

From CDOT Wiki
Jump to: navigation, search
(Q & A)
Line 6: Line 6:
 
<source lang="cpp"> void bordered(bool);</source>method which "sets the visibility of the border to the value received". The frame has no border if it is a fullscreen frame, should be safe to assume it has a border if it is not fullscreen (unless otherwise specified).
 
<source lang="cpp"> void bordered(bool);</source>method which "sets the visibility of the border to the value received". The frame has no border if it is a fullscreen frame, should be safe to assume it has a border if it is not fullscreen (unless otherwise specified).
 
'''Answer Submitted by:''' Team42<br><br>
 
'''Answer Submitted by:''' Team42<br><br>
 +
 +
'''Q:''' In the functions void row(int) and void col(int), are we receiving the values of row and column respectively that are relative to the parent frame or relative to the console screen?<br>
 +
'''Question Submitted by:''' Gideon Thomas and  Marie Karimizadeh<br>
 +
'''A:'''
 +
'''Answer Submitted by:''' <br><br>
  
 
== Bug Reports ==
 
== Bug Reports ==

Revision as of 12:54, 2 October 2012

Q & A

Q: Are we able to toggle the border's visibility or are we only able to toggle the frame's visibility? If yes, the constructor does not receive any information about the visibility of the border, do we assume that the border is visible?
Question Submitted by: Gideon Thomas and Marie Karimizadeh
A: Yes, we do get to toggle the border visibility by using the

 void bordered(bool);
method which "sets the visibility of the border to the value received". The frame has no border if it is a fullscreen frame, should be safe to assume it has a border if it is not fullscreen (unless otherwise specified).

Answer Submitted by: Team42

Q: In the functions void row(int) and void col(int), are we receiving the values of row and column respectively that are relative to the parent frame or relative to the console screen?
Question Submitted by: Gideon Thomas and Marie Karimizadeh
A: Answer Submitted by:

Bug Reports

Possible/Challenging Enhancements

Features Proposed by Team 42

  1. Smart word wrapping - words are not cut off mid-word while wrapping
  2. Optimization - "test" compiled executables have efficiency issues when moving boxes around
  3. Colors - you can add color to the test program if you're making your own main
  4. Timer - to keep track of how long the user has been running your custom main
  5. Files - Read string from file, use that string for editing, then write the result string to that file, overwriting original