Changes

Jump to: navigation, search

Assignment 2 (Fall 2013) Q & A

1,816 bytes added, 09:57, 4 November 2013
no edit summary
== Q&A About the CFrame Class ==
* Read Q&A Fall 2012.
* Alek's Questions (Fall 2013)
** In the specifications, it says ”If the constructor receives a negative height, the frame is full screen no matter what values of row, col, or width the caller specifies”. What if the passed-in width is negative? Shouldn’t the frame be considered full screen in this case as well?
*** Answer: Yes, the frame should be full screen if the width is negative.
** The fifth parameter on the constructor is a bool that indicates the frame’s visibility. But when I read the description of the draw() function, it says “... and that border is visible”. These two statements seem to contradict each other. One talks about the visibility of the frame and the other talks about the visibility of the border. In other words, I’m not sure what the visibility parameter refers to (border or the frame). I believe that visibility refers to the visibility of the border, not the frame. Can you please clarify?
*** Answer: Yes, your conclusion is valid. The fifth parameter in the CFrame constructor defines the frame's BORDER VISIBILITY, not the frame's visibility.
** For the draw(int = C_FULL_FRAME) function, I don't understand the purpose of its parameter. Is this intended to override the visibility of the border? If the frame is not bordered and if this parameter says C_FULL_FRAME, then should we draw the border anyways? What if the frame is full screen and this parameter says C_FULL_FRAME? Should it draw a border?
*** Answer:The function draws the frame if a) the frame is bordered AND b) the value of the parameter is not equal to C_NO_FRAME.
* Pavlo's Comment (Fall 2013)
** There seems to be a bug with the executable provided for us for release 1 of assignment 2, if you move the frame (container) all the way to the bottom and keep going right, the frame keeps moving down and leaves a trail.

Navigation menu