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

From CDOT Wiki
Jump to: navigation, search
(Bug Reports)
(Bug Reports)
Line 30: Line 30:
 
== Bug Reports ==
 
== Bug Reports ==
  
'''*''' In the given a2test_1_cframeBORLAND executable given as a reference to work on, if you move the outer frame all the way to the top right corner(or in such a way that it overlaps with Moving! ESC: exit), press ESCAPE, and then move the same frame again to the top left corner(or anywhere not previously occupied by Moving! ESC: exit), and then ESCAPE again, you will notice that a part of the frame is still visible on the part of the screen that used to contain the Moving... string. This is not the desired output.
+
<p>'''*''' <div style="margin-left:20;">In the given a2test_1_cframeBORLAND executable given as a reference to work on, if you move the outer frame all the way to the top right corner(or in such a way that it overlaps with Moving! ESC: exit), press ESCAPE, and then move the same frame again to the top left corner(or anywhere not previously occupied by Moving! ESC: exit), and then ESCAPE again, you will notice that a part of the frame is still visible on the part of the screen that used to contain the Moving... string. This is not the desired output.</div></p>
  
 
== Possible/Challenging Enhancements ==
 
== Possible/Challenging Enhancements ==

Revision as of 22:12, 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: In a CFrame class description most modifiers came in pairs with queries, like

void row(int) - sets the top row to the value received

int row() const - returns the top row position relative to the parent frame, if any; 0 if fullsreen



void col(int) - sets the left column to the value received

int col() const - returns the left column position relative to the parent frame, if any; 0 if fullsreen

So it's safe to assume that modifiers void row(int) and void col(int) will receive coordinates of top-left corner (row and col respectively) of the current frame relative to the parent frame.
Answer Submitted by: 010101000110010101100001011011010011010000110010

Bug Reports

*

In the given a2test_1_cframeBORLAND executable given as a reference to work on, if you move the outer frame all the way to the top right corner(or in such a way that it overlaps with Moving! ESC: exit), press ESCAPE, and then move the same frame again to the top left corner(or anywhere not previously occupied by Moving! ESC: exit), and then ESCAPE again, you will notice that a part of the frame is still visible on the part of the screen that used to contain the Moving... string. This is not the desired output.

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