In windows-api, the program can have a lot of user messages in one windows-thread, which is very good for us.
Considered: Command Assembling, which is very good on Windows thread.
Cursol + Enter
Cursol + Key "p"
Key "p"
table 1. Command interface.
1 | |||
2 | Cursol: 4th | Right Arrow | Spin: The eye is roate on the camera axes. |
3 | Key "p" | Printing: Objeect coordinates. | |
4 | Key "d" | Display: Display mode change. | |
5 | Packing: Objeect packing as box. | ||
6 | Cursol2: 1th | Display mode 1: Axes Only | |
7 | Cursol2: 2th | Display mode 2: Axes and Packing box. | |
8 | Cursol2: 3th | Display mode 3: Axes Object | |
9 | Cursol2: 4th | Display mode 4: Obejct Only | |
10 | |||
11 | Key "a" | Createing Axes: Recreate axes. | |
Mode Error: 20210711: Not initialized in display-function:
https://github.com/WaitrudWeber/source_zip/blob/master/analyzer_20200712-001.zip
Print Axes and Memorization Error: 20210721
WindowsAPI: windows-make: If you press TAB and 'p', ... - Waitrud Weber’s blog (hatenablog.com)
If we preapre the cursol and cursol2 as wButtonController and press arrow, the cursoles move at the same time., so, we change the control mode as like we put Change_Cursol_mode.
2. table Cursol Controler
1 | Change_Cursol_mode | Value | |
2 | 1 | Cursol can move if you press arrow. | |
3 | 2 | Cursol can move if you press arrow. | |
4 | 3 | Any Cursol doesn't move. | |
5 | |||
6 |
*