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

From CDOT Wiki
Jump to: navigation, search
(Q & A)
(Q & A)
Line 8: Line 8:
  
 
'''Q:''' The CField constructor receives a bool value that stores the <u>'''border's'''</u> visibility. The guidelines say that it passes all but one value to its base class constructor, CFrame. However, the CFrame constructor does not take an argument for the border's visibility and only takes one for the frame's visibility. How would we send this as an argument to the base class constructor?<br>
 
'''Q:''' The CField constructor receives a bool value that stores the <u>'''border's'''</u> visibility. The guidelines say that it passes all but one value to its base class constructor, CFrame. However, the CFrame constructor does not take an argument for the border's visibility and only takes one for the frame's visibility. How would we send this as an argument to the base class constructor?<br>
''' Question Submitted by:''' Gideon Thomas and  Marie Karimizadeh<br>
+
''' Question Submitted by:''' Team 15<br>
 
'''A:''' <br>
 
'''A:''' <br>
 
'''Answer Submitted by:''' <br><br>
 
'''Answer Submitted by:''' <br><br>

Revision as of 20:08, 2 November 2012

Q & A

For CButton, it says it needs to be a clickable button.
My question is, how do you record said click.
While looking this up on cplusplus.com and google, all i could find were examples with the windows API.
Is that what we're supposed to use to record the click action?
Question by: Team # 3

Q: The CField constructor receives a bool value that stores the border's visibility. The guidelines say that it passes all but one value to its base class constructor, CFrame. However, the CFrame constructor does not take an argument for the border's visibility and only takes one for the frame's visibility. How would we send this as an argument to the base class constructor?
Question Submitted by: Team 15
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