Project R0.1 20123- OOP344
- 1 Release
- 2 Notes
- 3 Due Dates
- 4 Help
- 5 Learning Outcome
- 6 Console Line Editing Facility
- 7 Submission
- Using Linux: please use putty only and set the keyboard to
- Backspace = Ctrl-?
- Home and End = Standard
- Function keys and keypad = Linux
- And then:
- Connection > Data > Terminal-type string = linux (This step must be done when first connecting through putty!)
- Or if you have already connected, type in (export TERM="linux") without brackets
- Guide for Using Borland 5.5
- Note that to change the cmd.exe window size, right click on the top bar -> Properties -> Layout Tab
- Mon Oct 15th, 23:59
Thanks Omkar, that was all I needed to understand how past this test.
- Omkar Parmar
Re : Amir, after previous test, without pressing any key it will display like this +--------------------------------------------------------------------+ |Test 4.17: console.edit() initial corrections, Offset: The offset is| |set to 10 that is invalid and it should be corrected to 5. The | |function should terminate returning 0. | +--------------------------------------------------------------------+ +--------------------+ | | +--------------------+ PASSED, hit any key to continue
- Re: Jessica, My question is what is the instruction for test 4.17, but thank you for replying.
- Re: Amir.
Amir, Try to re-download the cio_test.cpp from git and re-compile it again. I had some problem with you. It works fine after I re-upload the text.cpp file. I do not know what happened. - Jessica Park
- Re: Omkar.
Return value of edit is correct. How we should act in test 4.17? pressing arrow keys?
- Student: Omkar Parmar
Amir Check return value of edit function
- My program fails at the following test. Anyone knowswhy should it returns Unkown keycode? How it should be handled then! - Amir
+--------------------------------------------------------------------+ |Test 4.17: console.edit() initial corrections, Offset: The offset is| |set to 10 that is invalid and it should be corrected to 5. The | |function should terminate returning 0. | +--------------------------------------------------------------------+ +--------------------+ | | +--------------------+ - console.edit() was supposed to return Unknown Keycode, Dec: 0 Hex: 0 but instead it returned: ENTER, Dec: 10 Hex: A FAILED, hit any key to continue
- "My program is working completely fine in window but when I am trying to testing it on matrix it gives same error as below."- Tejas Patel
To Omkar Parmar: "Write [export TERM="linux"] then try it again"-Tejas Patel
- Student :Omkar Parmar
HOME,END F1, F2, F3, F4, F5 keys are not working while testing linux. HOME,END are return Unknown key and F1 A F2 B F3 C F4 D F5 E.
- After copying cio_test.o, it has changed MY NAME and R.01 to "CIO TESTER PROGRAM" and "R0.93". I can assume what happened it, but I just wonder it is ok? - Rody Choi <==I think that's it. cio_test.o cannot be edited. I guess cio_test.cpp is submitted as well. - Linpei Fan ===> I guess so. Thanks, Lily - Rody Choi
- I keep getting messages " The row and column of the terminal must be maximum of 30 by 100. press any key to quit
" when I tried to test it on matrix account. is there anyone who has same problem? - Jessica Park
- You need to resize the terminal window because the test program restricts it to 24x80 to 30x100 (rows x cols). You can also edit the size thru preferences/settings if you don't like trial and error - Michael Wang <=== Hey,you have to use the "PUTTY" - Rody Choi
<==Just using the "PUTTY" anything will be fined - Jay Feng =>
- When running on matrix, whenever I press Home, End, or Insert, the program exits rather than run the code I wrote. It works fine on Visual Studio however. I complied with -lncurses. - Ronny Wan <-- Check Notes section on this page and follow "Using Linux..." instruction even for Windows version of Putty - Hiroshi Takemoto
<===Try to compile it in a Linux OS, such as Fedora, using VM. It will be fine. - Linpei Fan ===>
- Ok, I did something with the display function. It's not 1 line but it's different from the code that's online and it has less loops. I sincerely hope it's not what was shown in class today, though, lol. I could be just writing remembered code which would be funny. Sad. But funny. Blog: ashtramwasser1
- Questions about terminating the process of editing by pressing ENTER, TAB, ESCAPE, UP, DOWN.... and what your program doing after pressing ESCAPE were not clear for me, so I decided to ask Fardad, here the answers.Blog: stanislavatseneca
- Here's a post of my troubleshooting issues with compiling the code on OSX. It covers both the terminal c++ compiler and Xcode. mgauer
- hi guys i would like to know ho you solved these two questions?
in the first one the test ask: PrnTextBox(1, 5, 70, 8, "Test 4.2: console.edit() initial corrections, Offset: The offset is set to 10 that is invalid and it should be corrected to 5. "//////////
"HIT ENTER ONLY to test!");
in the second test the same question is asked: PrnTextBox(1, 5, 70, 8, "Test 4.17: console.edit() initial corrections, Offset: The offset is set to 10 that is invalid and it should be corrected to 5. " //////////
"The function should terminate returning 0."); but how am i going to return 0 and at the same time set the offset to 10. I do not understand those two questions.
Upon successful completion of this first assignment, you will have demonstrated the abilities to design and code
- functions that use the basic console input and output library
- a line editor
- use of extern
- operator overload
- use of namespaces
Console Line Editing Facility
As your first assignment, you are to upgrade the basic console input output class (BConsole) to include line-display and line-editing facilities and use of "<<" and ">>" operators for character I/O and string output.
Your submission consists of a class called Console that is to be inherited from BConsole in a namespace called cio. Your application module is fully portable across Borland C++5.5 on windows, Linux GNU C++, Viusual C++ on Windows and Mac C++ platforms which accepts console input, and provides console output through the set of facilities available in your Console module.
The name of the library object to be created is console. The header file for the original version of this module is console.h and the implementation file for the original version is console.cpp. All of the identifiers for the library module and all upgrades to the module are defined in the cio namespace (short for console input output).
Your upgrade in this assignment consists of creating a class called Console, inherited from BConsole, implemented in two files; console.h and console.cpp:
In addition to all public methods of BConsole, Console must have the following two public methods and overload "<<" and ">>" operators.
- Create a global variable (unsigned int) called CIO_TABSIZE in cio namespace and create an external linkage to it in console.h
- instantiate Console, in an object called "console" in cio namespace and create an external linkage to in console.h
void display(const char* str, int row, int col, int fieldLen=0);
This method outputs the C-style, null-terminated string pointed to by str starting at row row and column col of the screen in a field of fieldLen characters. Row value 0 refers to the top row, and column value 0 refers to the left-most column.
If the string is longer than fieldLen, your function displays the first fieldLen characters. If the string is shorter than fieldLen, your function displays the portion of the entire string that fits on the screen, followed by enough trailing spaces to fill out the field completely.
If fieldLen is 0, your function displays the portion of the entire string with no trailing spaces. EDIT: In the video lecture, Fardad explains that if fieldLen is 0, the entire string is displayed.
Your function positions the cursor after the last character displayed. Your function does not flush the output buffer. The results are undefined if the starting position of the string is not within the dimensions of the screen.
Bonus: display() in One Line
int edit(char *str, int row, int col, int fieldLength, int maxStrLength, bool* insertMode, int* strOffset, int* curPosition, bool IsTextEditor = false, bool ReadOnly = false);
This method is to be written in two steps.
Ignore the last two arguments of the edit method (IsTextEditor and ReadOnly) and write the method as follows:
This method edits the C-style, null-terminated string pointed by str. The parameter row holds the row (0 is the top row) of the string on the screen. The parameter col holds the starting column (0 is the left-most column) on the screen. The parameter fieldLength holds the length of the editable field. The string may be larger than the field itself, in which case part of the string is hidden from view. The parameter maxStrLength holds the maximum length of the string, excluding the null byte. The parameter insertMode points to a bool variable that holds the current insert mode of the string. The parameter insertMode receives the address of a variable that stores the current editing mode - insert or overwrite. The parameter strOffset points to an int variable that holds the initial offset of the string within the field; that is, the index of the character in the string that initially occupies the first character position in the field. The parameter curPosition points to an int variable that holds the initial cursor position within the field; that is, the index of the character in the field at which the cursor is initially placed.
- Initial Corrections
- If the initial offset is beyond the end of the string, your function resets the offset to the length of the string; that is, to the index of the character immediately beyond the end of the string. If no offset variable is pointed to; that is, if the address of the variable is NULL, your function sets the offset to the index of the first character in the string; that is, to 0. (to do this have a local variable for the offset that holds zero to be pointed instead of an external variable)
- If the initial cursor position is beyond the end of the field, your function resets the position to the last character in the field. If the position is beyond the end of the string, your function resets the position to that immediately beyond the end of the string. If no cursor position variable is pointed to; that is, if the address of the variable is NULL, your function sets the cursor position to the first position in the field; that is, to position 0.(like the offset, to do this have a local variable for the cursor position that holds zero to be pointed instead of an external variable)
Your function does not allow the cursor to move before the start of the field or past the end of the field. If the field ends at the right edge of the screen, your function does not allow the cursor to the right of that edge.
Your function uses the symbolic names for non-ASCII and special keys defined in the keys.h header file. These names are the same symbolic names as those used in the original library module.
The user terminates editing by pressing ENTER, TAB, ESCAPE, UP, DOWN, PGUP, PGDN or any of the function keys F(1) through F(12) inclusive. If the user presses ESCAPE, your function aborts editing, replaces the contents of the string with the original contents upon entry into your function, and leaves the offset and cursor position values unaltered. In order to be able to revert to the original string, your function needs to allocate memory at run time.
At termination, your function passes back through the same int variables the current values of the offset and the cursor position, unless no variables were pointed to upon entry into your function; that is, unless the value of either address was NULL.
Your function returns an int identifying the key that the user pressed to exit the function.
Your function takes no action (other than perhaps beeping) if the user tries to enter too many characters (if, for example, the string is full in insert mode, or the cursor is positioned after the last character of a full string in overstrike mode).
Your function handles the non-ASCII keys as follows
- LEFT - moves the cursor left one character, if possible, changing the offset, if necessary.
- RIGHT - moves the cursor right one character, if possible, changing the offset, if necessary.
- HOME - moves the cursor to the beginning of the string, changing the offset, if necessary.
- END - moves the cursor to the position to the right of the last character in the string, changing the offset, if necessary. If the last character is at the edge of the screen, moves the cursor to that character.
- INSERT - toggles Insert/Overstrike mode. In Insert mode, your function inserts a printable character into the string at the current cursor position, moves the remainder of the string to the right to make room for the inserted character, and positions the cursor just to the right of the inserted character. The printable characters are the characters from space (' ') to tilde ('~') inclusive in the ASCII table. In Overstrike mode, your function overwrites the character (if any) at the current cursor position with a printable character and advances the cursor just to the right of the new character. If the cursor is past the end of the string, your function appends a printable character to the string as long as the string isn't full, regardless of the mode.
- DEL - discards the character at the current cursor position and moves all characters to the right of the cursor position one position to the left.
- BACKSPACE - discards the character to the left of the current cursor position, if possible, moves the characters at and to the right of the cursor position one position to the left, if possible, and positions the cursor one character to the left, if possible.
edit() always displays blanks in any part of the field that is not occupied by the string. UNDER NO CIRCUMSTANCES DOES YOUR FUNCTION CHANGE ANY POSITION ON THE SCREEN OUTSIDE THE FIELD. For example, your function does not display status information (such as "INS" or "OVR") elsewhere on the screen, since such displays limit the programmer's ability to design their own screen layouts.
You may assume that it is the calling program's responsibility to ensure that the string array is large enough to handle maxStrLength characters and that the starting screen position provides enough room (on the screen) for the field, etc.
First run your program with cio_test.cpp and make sure it passes all the tests up to and including "4.16". If all tests are passed continue with step two:
If IsTextEditor is true and the value of *strOffset is changed at any time, then terminate the edit function immediately and return 0;
If IsTextEditor is true and TAB key is hit, then instead of terminating the function, CIO_TABSIZE spaces are inserted into str. CIO_TABSIZE is to be global variable (unsigned integer initially set to be 4) to hold the number of spaces to be inserted when tab is hit.
If ReadOnly is true, then edit function works exactly like before, except that any modification to the data (the content of the str string) will be ignored.
Overload "<<" and ">>" operators
Console& operator>>(Console& cn, int& ch);
Get a key from keyboard using cn and store it in ch;
Console& operator<<(Console& cn, char ch);
Print the character ch on the screen, where the cursor is located, using cn and return the cn reference;
Console& operator<<(Console& cn, const char* str);
print the string str on the screen where the cursor is using cn and return the cn reference
Compile and test your upgrade with your test main in the following three command-line environments:
Local PC: Borland 5.5
bcc32 bconsole.cpp console.cpp cio_test.cpp
Local PC: Microsoft .net
Local Mac: (use -lcurses to link curses library)
c++ bconsole.cpp console.cpp cio_test.cpp -lcurses -Wno-write-strings
matrix: GNU (use -lncurses to link ncurses library)
g++ bconsole.cpp console.cpp cio_test.cpp -lncurses -Wno-write-strings
For submission purposes, your solution must compile, link, and run without errors in each environment.
To see how tester runs, you can run on Matrix (only use putty with the setting stated at Notes) run:
The due date for submission is: Mon Oct 15th 23:59
When your program passed all the tests, on matrix, create a directory and copy all the source files (console.cpp, console.h, bconsole.cpp, bconsole.h) into it. Then copy cio_test.o from "~fardad.soleimanloo" and then compile your code with your professors version of cio_test (i.e cio_test.o) and run it. If all the tests are passed successfully, an email will be sent to your professor automatically with your source code (console.h and console.cpp) attached to it.
to copy the cio_test.o do the following.
From the directory containing all source files:
$cp ~fardad.soleimanloo/cio_test.o .
to compile the code:
$g++ bconsole.cpp console.cpp cio_test.o -lncurses
This should not generate any warnings.
To run the test (with automatic submission)