1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
2407
2408
2409
2410
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420
2421
2422
2423
2424
2425
2426
2427
2428
2429
2430
2431
2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460
2461
2462
2463
2464
2465
2466
2467
2468
2469
2470
2471
2472
2473
2474
2475
2476
2477
2478
2479
2480
2481
2482
2483
2484
2485
2486
2487
2488
2489
2490
2491
2492
2493
2494
2495
2496
2497
2498
2499
2500
2501
2502
2503
2504
2505
2506
2507
2508
2509
2510
2511
2512
2513
2514
2515
2516
2517
2518
2519
2520
2521
2522
2523
2524
2525
2526
2527
2528
2529
2530
2531
2532
2533
2534
2535
2536
2537
2538
2539
2540
2541
2542
2543
2544
2545
2546
2547
2548
2549
2550
2551
2552
2553
2554
2555
2556
2557
2558
2559
2560
2561
2562
2563
2564
2565
2566
2567
2568
2569
2570
2571
2572
2573
2574
2575
2576
2577
2578
2579
2580
2581
2582
2583
2584
2585
2586
2587
2588
2589
2590
2591
2592
2593
2594
2595
2596
2597
2598
2599
2600
2601
2602
2603
2604
2605
2606
2607
2608
2609
2610
2611
2612
2613
2614
2615
2616
2617
2618
2619
2620
2621
2622
2623
2624
2625
2626
2627
2628
2629
2630
2631
2632
2633
2634
2635
2636
2637
2638
2639
2640
2641
2642
2643
2644
2645
2646
2647
2648
2649
2650
2651
2652
2653
2654
2655
2656
2657
2658
2659
2660
2661
2662
2663
2664
2665
2666
2667
2668
2669
2670
2671
2672
2673
2674
2675
2676
2677
2678
2679
2680
2681
2682
2683
2684
2685
2686
2687
2688
2689
2690
2691
2692
2693
2694
2695
2696
2697
2698
2699
2700
2701
2702
2703
2704
2705
2706
2707
2708
2709
2710
2711
2712
2713
2714
2715
2716
2717
2718
2719
2720
2721
2722
2723
2724
2725
2726
2727
2728
2729
2730
2731
2732
2733
2734
2735
2736
2737
2738
2739
2740
2741
2742
2743
2744
2745
2746
2747
2748
2749
2750
2751
2752
2753
2754
2755
2756
2757
2758
2759
2760
2761
2762
2763
2764
2765
2766
2767
2768
2769
2770
2771
2772
2773
2774
2775
2776
2777
2778
2779
2780
2781
2782
2783
2784
2785
2786
2787
2788
2789
2790
2791
2792
2793
2794
2795
2796
2797
2798
2799
2800
2801
2802
2803
2804
2805
2806
2807
2808
2809
2810
2811
2812
2813
2814
2815
2816
2817
2818
2819
2820
2821
2822
2823
2824
2825
2826
2827
2828
2829
2830
2831
2832
2833
2834
2835
2836
2837
2838
2839
2840
2841
2842
2843
2844
2845
2846
2847
2848
2849
2850
2851
2852
2853
2854
2855
2856
2857
2858
2859
2860
2861
2862
2863
2864
2865
2866
2867
2868
2869
2870
2871
2872
2873
2874
2875
2876
2877
2878
2879
2880
2881
2882
2883
2884
2885
2886
2887
2888
2889
2890
2891
2892
2893
2894
2895
2896
2897
2898
2899
2900
2901
2902
2903
2904
2905
2906
2907
2908
2909
2910
2911
2912
2913
2914
2915
2916
2917
2918
2919
2920
2921
2922
2923
2924
2925
2926
2927
2928
2929
2930
2931
2932
2933
2934
2935
2936
2937
2938
2939
2940
2941
2942
2943
2944
2945
2946
2947
2948
2949
2950
2951
2952
2953
2954
2955
2956
2957
2958
2959
2960
2961
2962
2963
2964
2965
2966
2967
2968
2969
2970
2971
2972
2973
2974
2975
2976
2977
2978
2979
2980
2981
2982
2983
2984
2985
2986
2987
2988
2989
2990
2991
2992
2993
2994
2995
2996
2997
2998
2999
3000
3001
3002
3003
3004
3005
3006
3007
3008
3009
3010
3011
3012
3013
3014
3015
3016
3017
3018
3019
3020
3021
3022
3023
3024
3025
3026
3027
3028
3029
3030
3031
3032
3033
3034
3035
3036
3037
3038
3039
3040
3041
3042
3043
3044
3045
3046
3047
3048
3049
3050
3051
3052
3053
3054
3055
3056
3057
3058
3059
3060
3061
3062
3063
3064
3065
3066
3067
3068
3069
3070
3071
3072
3073
3074
3075
3076
3077
3078
3079
3080
3081
3082
3083
3084
3085
3086
3087
3088
3089
3090
3091
3092
3093
3094
3095
3096
3097
3098
3099
3100
3101
3102
3103
3104
3105
3106
3107
3108
3109
3110
3111
3112
3113
3114
3115
3116
3117
3118
3119
3120
3121
3122
3123
3124
3125
3126
3127
3128
3129
3130
3131
3132
3133
3134
3135
3136
3137
3138
3139
3140
3141
3142
3143
3144
3145
3146
3147
3148
3149
3150
3151
3152
3153
3154
3155
3156
3157
3158
3159
3160
3161
3162
3163
3164
3165
3166
3167
3168
3169
3170
3171
3172
3173
3174
3175
3176
3177
3178
3179
3180
3181
3182
3183
3184
3185
3186
3187
3188
3189
3190
3191
3192
3193
3194
3195
3196
3197
3198
3199
3200
3201
3202
3203
3204
3205
3206
3207
3208
3209
3210
3211
3212
3213
3214
3215
3216
3217
3218
3219
3220
3221
3222
3223
3224
3225
3226
3227
3228
3229
3230
3231
3232
3233
3234
3235
3236
3237
3238
3239
3240
3241
3242
3243
3244
3245
3246
3247
3248
3249
3250
3251
3252
3253
3254
3255
3256
3257
3258
3259
3260
3261
3262
3263
3264
3265
3266
3267
3268
3269
3270
3271
3272
3273
3274
3275
3276
3277
3278
3279
3280
3281
3282
3283
3284
3285
3286
3287
3288
3289
3290
3291
3292
3293
3294
3295
3296
3297
3298
3299
3300
3301
3302
3303
3304
3305
3306
3307
3308
3309
3310
3311
3312
3313
3314
3315
3316
3317
3318
3319
3320
3321
3322
3323
3324
3325
3326
3327
3328
3329
3330
3331
3332
3333
3334
3335
3336
3337
3338
3339
3340
3341
3342
3343
3344
3345
3346
3347
3348
3349
3350
3351
3352
3353
3354
3355
3356
3357
3358
3359
3360
3361
3362
3363
3364
3365
3366
3367
3368
3369
3370
3371
3372
3373
3374
3375
3376
3377
3378
3379
3380
3381
3382
3383
3384
3385
3386
3387
3388
3389
3390
3391
3392
3393
3394
3395
3396
3397
3398
3399
3400
3401
3402
3403
3404
3405
3406
3407
3408
3409
3410
3411
3412
3413
3414
3415
3416
3417
3418
3419
3420
3421
3422
3423
3424
3425
3426
3427
3428
3429
3430
3431
3432
3433
3434
3435
3436
3437
3438
3439
3440
3441
3442
3443
3444
3445
3446
3447
3448
3449
3450
3451
3452
3453
3454
3455
3456
3457
3458
3459
3460
3461
3462
3463
3464
3465
3466
3467
3468
3469
3470
3471
3472
3473
3474
3475
3476
3477
3478
3479
3480
3481
3482
3483
3484
3485
3486
3487
3488
3489
3490
3491
3492
3493
3494
3495
3496
3497
3498
3499
3500
3501
3502
3503
3504
3505
3506
3507
3508
3509
3510
3511
3512
3513
3514
3515
3516
3517
3518
3519
3520
3521
3522
3523
3524
3525
3526
3527
3528
3529
3530
3531
3532
3533
3534
3535
3536
3537
3538
3539
3540
3541
3542
3543
3544
3545
3546
3547
3548
3549
3550
3551
3552
3553
3554
3555
3556
3557
3558
3559
3560
3561
3562
3563
3564
3565
3566
3567
3568
3569
3570
3571
3572
3573
3574
3575
3576
3577
3578
3579
3580
3581
3582
3583
3584
3585
3586
3587
3588
3589
3590
3591
3592
3593
3594
3595
3596
3597
3598
3599
3600
3601
3602
3603
3604
3605
3606
3607
3608
3609
3610
3611
3612
3613
3614
3615
3616
3617
3618
3619
3620
3621
3622
3623
3624
3625
3626
3627
3628
3629
3630
3631
3632
3633
3634
3635
3636
3637
3638
3639
3640
3641
3642
3643
3644
3645
3646
3647
3648
3649
3650
3651
3652
3653
3654
3655
3656
3657
3658
3659
3660
3661
3662
3663
3664
3665
3666
3667
3668
3669
3670
3671
3672
3673
3674
3675
3676
3677
3678
3679
3680
3681
3682
3683
3684
3685
3686
3687
3688
3689
3690
3691
3692
3693
3694
3695
3696
3697
3698
3699
3700
3701
3702
3703
3704
3705
3706
3707
3708
3709
3710
3711
3712
3713
3714
3715
3716
3717
3718
3719
3720
3721
3722
3723
3724
3725
3726
3727
3728
3729
3730
3731
3732
3733
3734
3735
3736
3737
3738
3739
3740
3741
3742
3743
3744
3745
3746
3747
3748
3749
3750
3751
3752
3753
3754
3755
3756
3757
3758
3759
3760
3761
3762
3763
3764
3765
3766
3767
3768
3769
3770
3771
3772
3773
3774
3775
3776
3777
3778
3779
3780
3781
3782
3783
3784
3785
3786
3787
3788
3789
3790
3791
3792
3793
3794
3795
3796
3797
3798
3799
3800
3801
3802
3803
3804
3805
3806
3807
3808
3809
3810
3811
3812
3813
3814
3815
3816
3817
3818
3819
3820
3821
3822
3823
3824
3825
3826
3827
3828
3829
3830
3831
3832
3833
3834
3835
3836
3837
3838
3839
3840
3841
3842
3843
3844
3845
3846
3847
3848
3849
3850
3851
3852
3853
3854
3855
3856
3857
3858
3859
3860
3861
3862
3863
3864
3865
3866
3867
3868
3869
3870
3871
3872
3873
3874
3875
3876
3877
3878
3879
3880
3881
3882
3883
3884
3885
3886
3887
3888
3889
3890
3891
3892
3893
3894
3895
3896
3897
3898
3899
3900
3901
3902
3903
3904
3905
3906
3907
3908
3909
3910
3911
3912
3913
3914
3915
3916
3917
3918
3919
3920
3921
3922
3923
3924
3925
3926
3927
3928
3929
3930
3931
3932
3933
3934
3935
3936
3937
3938
3939
3940
3941
3942
3943
3944
3945
3946
3947
3948
3949
3950
3951
3952
3953
3954
3955
3956
3957
3958
3959
3960
3961
3962
3963
3964
3965
3966
3967
3968
3969
3970
3971
3972
3973
3974
3975
3976
3977
3978
3979
3980
3981
3982
3983
3984
3985
3986
3987
3988
3989
3990
3991
3992
3993
3994
3995
3996
3997
3998
3999
4000
4001
4002
4003
4004
4005
4006
4007
4008
4009
4010
4011
4012
4013
4014
4015
4016
4017
4018
4019
4020
4021
4022
4023
4024
4025
4026
4027
4028
4029
4030
4031
4032
4033
4034
4035
4036
4037
4038
4039
4040
4041
4042
4043
4044
4045
4046
4047
4048
4049
4050
4051
4052
4053
4054
4055
4056
4057
4058
4059
4060
4061
4062
4063
4064
4065
4066
4067
4068
4069
4070
4071
4072
4073
4074
4075
4076
4077
4078
4079
4080
4081
4082
4083
4084
4085
4086
4087
4088
4089
4090
4091
4092
4093
4094
4095
4096
4097
4098
4099
4100
4101
4102
4103
4104
4105
4106
4107
4108
4109
4110
4111
4112
4113
4114
4115
4116
4117
4118
4119
4120
4121
4122
4123
4124
4125
4126
4127
4128
4129
4130
4131
4132
4133
4134
4135
4136
4137
4138
4139
4140
4141
4142
4143
4144
4145
4146
4147
4148
4149
4150
4151
4152
4153
4154
4155
4156
4157
4158
4159
4160
4161
4162
4163
4164
4165
4166
4167
4168
4169
4170
4171
4172
4173
4174
4175
4176
4177
4178
4179
4180
4181
4182
4183
4184
4185
4186
4187
4188
4189
4190
4191
4192
4193
4194
4195
4196
4197
4198
4199
4200
4201
4202
4203
4204
4205
4206
4207
4208
4209
4210
4211
4212
4213
4214
4215
4216
4217
4218
4219
4220
4221
4222
4223
4224
4225
4226
4227
4228
4229
4230
4231
4232
4233
4234
4235
4236
4237
4238
4239
4240
4241
4242
4243
4244
4245
4246
4247
4248
4249
4250
4251
4252
4253
4254
4255
4256
4257
4258
4259
4260
4261
4262
4263
4264
4265
4266
4267
4268
4269
4270
4271
4272
4273
4274
4275
4276
4277
4278
4279
4280
4281
4282
4283
4284
4285
4286
4287
4288
4289
4290
4291
4292
4293
4294
4295
4296
4297
4298
4299
4300
4301
4302
4303
4304
4305
4306
4307
4308
4309
4310
4311
4312
4313
4314
4315
4316
4317
4318
4319
4320
4321
4322
4323
4324
4325
4326
4327
4328
4329
4330
4331
4332
4333
4334
4335
4336
4337
4338
4339
4340
4341
4342
4343
4344
4345
4346
4347
4348
4349
4350
4351
4352
4353
4354
4355
4356
4357
4358
4359
4360
4361
4362
4363
4364
4365
4366
4367
4368
4369
4370
4371
4372
4373
4374
4375
4376
4377
4378
4379
4380
4381
4382
4383
4384
4385
4386
4387
4388
4389
4390
4391
4392
4393
4394
4395
4396
4397
4398
4399
4400
4401
4402
4403
4404
4405
4406
4407
4408
4409
4410
4411
4412
4413
4414
4415
4416
4417
4418
4419
4420
4421
4422
4423
4424
4425
4426
4427
4428
4429
4430
4431
4432
4433
4434
4435
4436
4437
4438
4439
4440
4441
4442
4443
4444
4445
4446
4447
4448
4449
4450
4451
4452
4453
4454
4455
4456
4457
4458
4459
4460
4461
4462
4463
4464
4465
4466
4467
4468
4469
4470
4471
4472
4473
4474
4475
4476
4477
4478
4479
4480
4481
4482
4483
4484
4485
4486
4487
4488
4489
4490
4491
4492
4493
4494
4495
4496
4497
4498
4499
4500
4501
4502
4503
4504
4505
4506
4507
4508
4509
4510
4511
4512
4513
4514
4515
4516
4517
4518
4519
4520
4521
4522
4523
4524
4525
4526
4527
4528
4529
4530
4531
4532
4533
4534
4535
4536
4537
4538
4539
4540
4541
4542
4543
4544
4545
4546
4547
4548
4549
4550
4551
4552
4553
4554
4555
4556
4557
4558
4559
4560
4561
4562
4563
4564
4565
4566
4567
4568
4569
4570
4571
4572
4573
4574
4575
4576
4577
4578
4579
4580
4581
4582
4583
4584
4585
4586
4587
4588
4589
4590
4591
4592
4593
4594
4595
4596
4597
4598
4599
4600
4601
4602
4603
4604
4605
4606
4607
4608
4609
4610
4611
4612
4613
4614
4615
4616
4617
4618
4619
4620
4621
4622
4623
4624
4625
4626
4627
4628
4629
4630
4631
4632
4633
4634
4635
4636
4637
4638
4639
4640
4641
4642
4643
4644
4645
4646
4647
4648
4649
4650
4651
4652
4653
4654
4655
4656
4657
4658
4659
4660
4661
4662
4663
4664
4665
4666
4667
4668
4669
4670
4671
4672
4673
4674
4675
4676
4677
4678
4679
4680
4681
4682
4683
4684
4685
4686
4687
4688
4689
4690
4691
4692
4693
4694
4695
4696
4697
4698
4699
4700
4701
4702
4703
4704
4705
4706
4707
4708
4709
4710
4711
4712
4713
4714
4715
4716
4717
4718
4719
4720
4721
4722
4723
4724
4725
4726
4727
4728
4729
4730
4731
4732
4733
4734
4735
4736
4737
4738
4739
4740
4741
4742
4743
4744
4745
4746
4747
4748
4749
4750
4751
4752
4753
4754
4755
4756
4757
4758
4759
4760
4761
4762
4763
4764
4765
4766
4767
4768
4769
4770
4771
4772
4773
4774
4775
4776
4777
4778
4779
4780
4781
4782
4783
4784
4785
4786
4787
4788
4789
4790
4791
4792
4793
4794
4795
4796
4797
4798
4799
4800
4801
4802
4803
4804
4805
4806
4807
4808
4809
4810
4811
4812
4813
4814
4815
4816
4817
4818
4819
4820
4821
4822
4823
4824
4825
4826
4827
4828
4829
4830
4831
4832
4833
4834
4835
4836
4837
4838
4839
4840
4841
4842
4843
4844
4845
4846
4847
4848
4849
4850
4851
4852
4853
4854
4855
4856
4857
4858
4859
4860
4861
4862
4863
4864
4865
4866
4867
4868
4869
4870
4871
4872
4873
4874
4875
4876
4877
4878
4879
4880
4881
4882
4883
4884
4885
4886
4887
4888
4889
4890
4891
4892
4893
4894
4895
4896
4897
4898
4899
4900
4901
4902
4903
4904
4905
4906
4907
4908
4909
4910
4911
4912
4913
4914
4915
4916
4917
4918
4919
4920
4921
4922
4923
4924
4925
4926
4927
4928
4929
4930
4931
4932
4933
4934
4935
4936
4937
4938
4939
4940
4941
4942
4943
4944
4945
4946
4947
4948
4949
4950
4951
4952
4953
4954
4955
4956
4957
4958
4959
4960
4961
4962
4963
4964
4965
4966
4967
4968
4969
4970
4971
4972
4973
4974
4975
4976
4977
4978
4979
4980
4981
4982
4983
4984
4985
4986
4987
4988
4989
4990
4991
4992
4993
4994
4995
4996
4997
4998
4999
5000
5001
5002
5003
5004
5005
5006
5007
5008
5009
5010
5011
5012
5013
5014
5015
5016
5017
5018
5019
5020
5021
5022
5023
5024
5025
5026
5027
5028
5029
5030
5031
5032
5033
5034
5035
5036
5037
5038
5039
5040
5041
5042
5043
5044
5045
5046
5047
5048
5049
5050
5051
5052
5053
5054
5055
5056
5057
5058
5059
5060
5061
5062
5063
5064
5065
5066
5067
5068
5069
5070
5071
5072
5073
5074
5075
5076
5077
5078
5079
5080
5081
5082
5083
5084
5085
5086
5087
5088
5089
5090
5091
5092
5093
5094
5095
5096
5097
5098
5099
5100
5101
5102
5103
5104
5105
5106
5107
5108
5109
5110
5111
5112
5113
5114
5115
5116
5117
5118
5119
5120
5121
5122
5123
5124
5125
5126
5127
5128
5129
5130
5131
5132
5133
5134
5135
5136
5137
5138
5139
5140
5141
5142
5143
5144
5145
5146
5147
5148
5149
5150
5151
5152
5153
5154
5155
5156
5157
5158
5159
5160
5161
5162
5163
5164
5165
5166
5167
5168
5169
5170
5171
5172
5173
5174
5175
5176
5177
5178
5179
5180
5181
5182
5183
5184
5185
5186
5187
5188
5189
5190
5191
5192
5193
5194
5195
5196
5197
5198
5199
5200
5201
5202
5203
5204
5205
5206
5207
5208
5209
5210
5211
5212
5213
5214
5215
5216
5217
5218
5219
5220
5221
5222
5223
5224
5225
5226
5227
5228
5229
5230
5231
5232
5233
5234
5235
5236
5237
5238
5239
5240
5241
5242
5243
5244
5245
5246
5247
5248
5249
5250
5251
5252
5253
5254
5255
5256
5257
5258
5259
5260
5261
5262
5263
5264
5265
5266
5267
5268
5269
5270
5271
5272
5273
5274
5275
5276
5277
5278
5279
5280
5281
5282
5283
5284
5285
5286
5287
5288
5289
5290
5291
5292
5293
5294
5295
5296
5297
5298
5299
5300
5301
5302
5303
5304
5305
5306
5307
5308
5309
5310
5311
5312
5313
5314
5315
5316
5317
5318
5319
5320
5321
5322
5323
5324
5325
5326
5327
5328
5329
5330
5331
5332
5333
5334
5335
5336
5337
5338
5339
5340
5341
5342
5343
5344
5345
5346
5347
5348
5349
5350
5351
5352
5353
5354
5355
5356
5357
5358
5359
5360
5361
5362
5363
5364
5365
5366
5367
5368
5369
5370
5371
5372
5373
5374
5375
5376
5377
5378
5379
5380
5381
5382
5383
5384
5385
5386
5387
5388
5389
5390
5391
5392
5393
5394
5395
5396
5397
5398
5399
5400
5401
5402
5403
5404
5405
5406
5407
5408
5409
5410
5411
5412
5413
5414
5415
5416
5417
5418
5419
5420
5421
5422
5423
5424
5425
5426
5427
5428
5429
5430
5431
5432
5433
5434
5435
5436
5437
5438
5439
5440
5441
5442
5443
5444
5445
5446
5447
5448
5449
5450
5451
5452
5453
5454
5455
5456
5457
5458
5459
5460
5461
5462
5463
5464
5465
5466
5467
5468
5469
5470
5471
5472
5473
5474
5475
5476
5477
5478
5479
5480
5481
5482
5483
5484
5485
5486
5487
5488
5489
5490
5491
5492
5493
5494
5495
5496
5497
5498
5499
5500
5501
5502
5503
5504
5505
5506
5507
5508
5509
5510
5511
5512
5513
5514
5515
5516
5517
5518
5519
5520
5521
5522
5523
5524
5525
5526
5527
5528
5529
5530
5531
5532
5533
5534
5535
5536
5537
5538
5539
5540
5541
5542
5543
5544
5545
5546
5547
5548
5549
5550
5551
5552
5553
5554
5555
5556
5557
5558
5559
5560
5561
5562
5563
5564
5565
5566
5567
5568
5569
5570
5571
5572
5573
5574
5575
5576
5577
5578
5579
5580
5581
5582
5583
5584
5585
5586
5587
5588
5589
5590
5591
5592
5593
5594
5595
5596
5597
5598
5599
5600
5601
5602
5603
5604
5605
5606
5607
5608
5609
5610
5611
5612
5613
5614
5615
5616
5617
5618
5619
5620
5621
5622
5623
5624
5625
5626
5627
5628
5629
5630
5631
5632
5633
5634
5635
5636
5637
5638
5639
5640
5641
5642
5643
5644
5645
5646
5647
5648
5649
5650
5651
5652
5653
5654
5655
5656
5657
5658
5659
5660
5661
5662
5663
5664
5665
5666
5667
5668
5669
5670
5671
5672
5673
5674
5675
5676
5677
5678
5679
5680
5681
5682
5683
5684
5685
5686
5687
5688
5689
5690
5691
5692
5693
5694
5695
5696
5697
5698
5699
5700
5701
5702
5703
5704
5705
5706
5707
5708
5709
5710
5711
5712
5713
5714
5715
5716
5717
5718
5719
5720
5721
5722
5723
5724
5725
5726
5727
5728
5729
5730
5731
5732
5733
5734
5735
5736
5737
5738
5739
5740
5741
5742
5743
5744
5745
5746
5747
5748
5749
5750
5751
5752
5753
5754
5755
5756
5757
5758
5759
5760
5761
5762
5763
5764
5765
5766
5767
5768
5769
5770
5771
5772
5773
5774
5775
5776
5777
5778
5779
5780
5781
5782
5783
5784
5785
5786
5787
5788
5789
5790
5791
5792
5793
5794
5795
5796
5797
5798
5799
5800
5801
5802
5803
5804
5805
5806
5807
5808
5809
5810
5811
5812
5813
5814
5815
5816
5817
5818
5819
5820
5821
5822
5823
5824
5825
5826
5827
5828
5829
5830
5831
5832
5833
5834
5835
5836
5837
5838
5839
5840
5841
5842
5843
5844
5845
5846
5847
5848
5849
5850
5851
5852
5853
5854
5855
5856
5857
5858
5859
5860
5861
5862
5863
5864
5865
5866
5867
5868
5869
5870
5871
5872
5873
5874
5875
5876
5877
5878
5879
5880
5881
5882
5883
5884
5885
5886
5887
5888
5889
5890
5891
5892
5893
5894
5895
5896
5897
5898
5899
5900
5901
5902
5903
5904
5905
5906
5907
5908
5909
5910
5911
5912
5913
5914
5915
5916
5917
5918
5919
5920
5921
5922
5923
5924
5925
5926
5927
5928
5929
5930
5931
5932
5933
5934
5935
5936
5937
5938
5939
5940
5941
5942
5943
5944
5945
5946
5947
5948
5949
5950
5951
5952
5953
5954
5955
5956
5957
5958
5959
5960
5961
5962
5963
5964
5965
5966
5967
5968
5969
5970
5971
5972
5973
5974
5975
5976
5977
5978
5979
5980
5981
5982
5983
5984
5985
5986
5987
5988
5989
5990
5991
5992
5993
5994
5995
5996
5997
5998
5999
6000
6001
6002
6003
6004
6005
6006
6007
6008
6009
6010
6011
6012
6013
6014
6015
6016
6017
6018
6019
6020
6021
6022
6023
6024
6025
6026
6027
6028
6029
6030
6031
6032
6033
6034
6035
6036
6037
6038
6039
6040
6041
6042
6043
6044
6045
6046
6047
6048
6049
6050
6051
6052
6053
6054
6055
6056
6057
6058
6059
6060
6061
6062
6063
6064
6065
6066
6067
6068
6069
6070
6071
6072
6073
6074
6075
6076
6077
6078
6079
6080
6081
6082
6083
6084
6085
6086
6087
6088
6089
6090
6091
6092
6093
6094
6095
6096
6097
6098
6099
6100
6101
6102
6103
6104
6105
6106
6107
6108
6109
6110
6111
6112
6113
6114
6115
6116
6117
6118
6119
6120
6121
6122
6123
6124
6125
6126
6127
6128
6129
6130
6131
6132
6133
6134
6135
6136
6137
6138
6139
6140
6141
6142
6143
6144
6145
6146
6147
6148
6149
6150
6151
6152
6153
6154
6155
6156
6157
6158
6159
6160
6161
6162
6163
6164
6165
6166
6167
6168
6169
6170
6171
6172
6173
6174
6175
6176
6177
6178
6179
6180
6181
6182
6183
6184
6185
6186
6187
6188
6189
6190
6191
6192
6193
6194
6195
6196
6197
6198
6199
6200
6201
6202
6203
6204
6205
6206
6207
6208
6209
6210
6211
6212
6213
6214
6215
6216
6217
6218
6219
6220
6221
6222
6223
6224
6225
6226
6227
6228
6229
6230
6231
6232
6233
6234
6235
6236
6237
6238
6239
6240
6241
6242
6243
6244
6245
6246
6247
6248
6249
6250
6251
6252
6253
6254
6255
6256
6257
6258
6259
6260
6261
6262
6263
6264
6265
6266
6267
6268
6269
6270
6271
6272
6273
6274
6275
6276
6277
6278
6279
6280
6281
6282
6283
6284
6285
6286
6287
6288
6289
6290
6291
6292
6293
6294
6295
6296
6297
6298
6299
6300
6301
6302
6303
6304
6305
6306
6307
6308
6309
6310
6311
6312
6313
6314
6315
6316
6317
6318
6319
6320
6321
6322
6323
6324
6325
6326
6327
6328
6329
6330
6331
6332
6333
6334
6335
6336
6337
6338
6339
6340
6341
6342
6343
6344
6345
6346
6347
6348
6349
6350
6351
6352
6353
6354
6355
6356
6357
6358
6359
6360
6361
6362
6363
6364
6365
6366
6367
6368
6369
6370
6371
6372
6373
6374
6375
6376
6377
6378
6379
6380
6381
6382
6383
6384
6385
6386
6387
6388
6389
6390
6391
6392
6393
6394
6395
6396
6397
6398
6399
6400
6401
6402
6403
6404
6405
6406
6407
6408
6409
6410
6411
6412
6413
6414
6415
6416
6417
6418
6419
6420
6421
6422
6423
6424
6425
6426
6427
6428
6429
6430
6431
6432
6433
6434
6435
6436
6437
6438
6439
6440
6441
6442
6443
6444
6445
6446
6447
6448
6449
6450
6451
6452
6453
6454
6455
6456
6457
6458
6459
6460
6461
6462
6463
6464
6465
6466
6467
6468
6469
6470
6471
6472
6473
6474
6475
6476
6477
6478
6479
6480
6481
6482
6483
6484
6485
6486
6487
6488
6489
6490
6491
6492
6493
6494
6495
6496
6497
6498
6499
6500
6501
6502
6503
6504
6505
6506
6507
6508
6509
6510
6511
6512
6513
6514
6515
6516
6517
6518
6519
6520
6521
6522
6523
6524
6525
6526
6527
6528
6529
6530
6531
6532
6533
6534
6535
6536
6537
6538
6539
6540
6541
6542
6543
6544
6545
6546
6547
6548
6549
6550
6551
6552
6553
6554
6555
6556
6557
6558
6559
6560
6561
6562
6563
6564
6565
6566
6567
6568
6569
6570
6571
6572
6573
6574
6575
6576
6577
6578
6579
6580
6581
6582
6583
6584
6585
6586
6587
6588
6589
6590
6591
6592
6593
6594
6595
6596
6597
6598
6599
6600
6601
6602
6603
6604
6605
6606
6607
6608
6609
6610
6611
6612
6613
6614
6615
6616
6617
6618
6619
6620
6621
6622
6623
6624
6625
6626
6627
6628
6629
6630
6631
6632
6633
6634
6635
6636
6637
6638
6639
6640
6641
6642
6643
6644
6645
6646
6647
6648
6649
6650
6651
6652
6653
6654
6655
6656
6657
6658
6659
6660
6661
6662
6663
6664
6665
6666
6667
6668
6669
6670
6671
6672
6673
6674
6675
6676
6677
6678
6679
6680
6681
6682
6683
6684
6685
6686
6687
6688
6689
6690
6691
6692
6693
6694
6695
6696
6697
6698
6699
6700
6701
6702
6703
6704
6705
6706
6707
6708
6709
6710
6711
6712
6713
6714
6715
6716
6717
6718
6719
6720
6721
6722
6723
6724
6725
6726
6727
6728
6729
6730
6731
6732
6733
6734
6735
6736
6737
6738
6739
6740
6741
6742
6743
6744
6745
6746
6747
6748
6749
6750
6751
6752
6753
6754
6755
6756
6757
6758
6759
6760
6761
6762
6763
6764
6765
6766
6767
6768
6769
6770
6771
6772
6773
6774
6775
6776
6777
6778
6779
6780
6781
6782
6783
6784
6785
6786
6787
6788
6789
6790
6791
6792
6793
6794
6795
6796
6797
6798
6799
6800
6801
6802
6803
6804
6805
6806
6807
6808
6809
6810
6811
6812
6813
6814
6815
6816
6817
6818
6819
6820
6821
6822
6823
6824
6825
6826
6827
6828
6829
6830
6831
6832
6833
6834
6835
6836
6837
6838
6839
6840
6841
6842
6843
6844
6845
6846
6847
6848
6849
6850
6851
6852
6853
6854
6855
6856
6857
6858
6859
6860
6861
6862
6863
6864
6865
6866
6867
6868
6869
6870
6871
6872
6873
6874
6875
6876
6877
6878
6879
6880
6881
6882
6883
6884
6885
6886
6887
6888
6889
6890
6891
6892
6893
6894
6895
6896
6897
6898
6899
6900
6901
6902
6903
6904
6905
6906
6907
6908
6909
6910
6911
6912
6913
6914
6915
6916
6917
6918
6919
6920
6921
6922
6923
6924
6925
6926
6927
6928
6929
6930
6931
6932
6933
6934
6935
6936
6937
6938
6939
6940
6941
6942
6943
6944
6945
6946
6947
6948
6949
6950
6951
6952
6953
6954
6955
6956
6957
6958
6959
6960
6961
6962
6963
6964
6965
6966
6967
6968
6969
6970
6971
6972
6973
6974
6975
6976
6977
6978
6979
6980
6981
6982
6983
6984
6985
6986
6987
6988
6989
6990
6991
6992
6993
6994
6995
6996
6997
6998
6999
7000
7001
7002
7003
7004
7005
7006
7007
7008
7009
7010
7011
7012
7013
7014
7015
7016
7017
7018
7019
7020
7021
7022
7023
7024
7025
7026
7027
7028
7029
7030
7031
7032
7033
7034
7035
7036
7037
7038
7039
7040
7041
7042
7043
7044
7045
7046
7047
7048
7049
7050
7051
7052
7053
7054
7055
7056
7057
7058
7059
7060
7061
7062
7063
7064
7065
7066
7067
7068
7069
7070
7071
7072
7073
7074
7075
7076
7077
7078
7079
7080
7081
7082
7083
7084
7085
7086
7087
7088
7089
7090
7091
7092
7093
7094
7095
7096
7097
7098
7099
7100
7101
7102
7103
7104
7105
7106
7107
7108
7109
7110
7111
7112
7113
7114
7115
7116
7117
7118
7119
7120
7121
7122
7123
7124
7125
7126
7127
7128
7129
7130
7131
7132
7133
7134
7135
7136
7137
7138
7139
7140
7141
7142
7143
7144
7145
7146
7147
7148
7149
7150
7151
7152
7153
7154
7155
7156
7157
7158
7159
7160
7161
7162
7163
7164
7165
7166
7167
7168
7169
7170
7171
7172
7173
7174
7175
7176
7177
7178
7179
7180
7181
7182
7183
7184
7185
7186
7187
7188
7189
7190
7191
7192
7193
7194
7195
7196
7197
7198
7199
7200
7201
7202
7203
7204
7205
7206
7207
7208
7209
7210
7211
7212
7213
7214
7215
7216
7217
7218
7219
7220
7221
7222
7223
7224
7225
7226
7227
7228
7229
7230
7231
7232
7233
7234
7235
7236
7237
7238
7239
7240
7241
7242
7243
7244
7245
7246
7247
7248
7249
7250
7251
7252
7253
7254
7255
7256
7257
7258
7259
7260
7261
7262
7263
7264
7265
7266
7267
7268
7269
7270
7271
7272
7273
7274
7275
7276
7277
7278
7279
7280
7281
7282
7283
7284
7285
7286
7287
7288
7289
7290
7291
7292
7293
7294
7295
7296
7297
7298
7299
7300
7301
7302
7303
7304
7305
7306
7307
7308
7309
7310
7311
7312
7313
7314
7315
7316
7317
7318
7319
7320
7321
7322
7323
7324
7325
7326
7327
7328
7329
7330
7331
7332
7333
7334
7335
7336
7337
7338
7339
7340
7341
7342
7343
7344
7345
7346
7347
7348
7349
7350
7351
7352
7353
7354
7355
7356
7357
7358
7359
7360
7361
7362
7363
7364
7365
7366
7367
7368
7369
7370
7371
7372
7373
7374
7375
7376
7377
7378
7379
7380
7381
7382
7383
7384
7385
7386
7387
7388
7389
7390
7391
7392
7393
7394
7395
7396
7397
7398
7399
7400
7401
7402
7403
7404
7405
7406
7407
7408
7409
7410
7411
7412
7413
7414
7415
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<meta name="generator" content=
"HTML Tidy for Linux (vers 25 March 2009), see www.w3.org">
<title>NCURSES Programming HOWTO</title>
<meta name="GENERATOR" content=
"Modular DocBook HTML Stylesheet Version 1.79">
</head>
<body class="ARTICLE" bgcolor="#FFFFFF" text="#000000" link=
"#0000FF" vlink="#840084" alink="#0000FF">
<div class="ARTICLE">
<div class="TITLEPAGE">
<h1 class="TITLE"><a name="AEN2" id="AEN2">NCURSES
Programming HOWTO</a></h1>
<h3 class="AUTHOR"><a name="AEN4" id="AEN4">Pradeep
Padala</a></h3>
<div class="AFFILIATION">
<div class="ADDRESS">
<p class="ADDRESS"><code class="EMAIL"><<a href=
"mailto:ppadala@gmail.com">ppadala@gmail.com</a>></code></p>
</div>
</div>
<p class="PUBDATE">v1.9, 2005-06-20<br></p>
<div class="REVHISTORY">
<table width="100%" border="0" summary="revisions">
<tr>
<th align="left" valign="top" colspan="3"><b>Revision
History</b></th>
</tr>
<tr>
<td align="left">Revision 1.9</td>
<td align="left">2005-06-20</td>
<td align="left">Revised by: ppadala</td>
</tr>
<tr>
<td align="left" colspan="3">The license has been
changed to the MIT-style license used by NCURSES. Note
that the programs are also re-licensed under this.</td>
</tr>
<tr>
<td align="left">Revision 1.8</td>
<td align="left">2005-06-17</td>
<td align="left">Revised by: ppadala</td>
</tr>
<tr>
<td align="left" colspan="3">Lots of updates. Added
references and perl examples. Changes to examples. Many
grammatical and stylistic changes to the content.
Changes to NCURSES history.</td>
</tr>
<tr>
<td align="left">Revision 1.7.1</td>
<td align="left">2002-06-25</td>
<td align="left">Revised by: ppadala</td>
</tr>
<tr>
<td align="left" colspan="3">Added a README file for
building and instructions for building from
source.</td>
</tr>
<tr>
<td align="left">Revision 1.7</td>
<td align="left">2002-06-25</td>
<td align="left">Revised by: ppadala</td>
</tr>
<tr>
<td align="left" colspan="3">Added "Other formats"
section and made a lot of fancy changes to the
programs. Inlining of programs is gone.</td>
</tr>
<tr>
<td align="left">Revision 1.6.1</td>
<td align="left">2002-02-24</td>
<td align="left">Revised by: ppadala</td>
</tr>
<tr>
<td align="left" colspan="3">Removed the old Changelog
section, cleaned the makefiles</td>
</tr>
<tr>
<td align="left">Revision 1.6</td>
<td align="left">2002-02-16</td>
<td align="left">Revised by: ppadala</td>
</tr>
<tr>
<td align="left" colspan="3">Corrected a lot of
spelling mistakes, added ACS variables section</td>
</tr>
<tr>
<td align="left">Revision 1.5</td>
<td align="left">2002-01-05</td>
<td align="left">Revised by: ppadala</td>
</tr>
<tr>
<td align="left" colspan="3">Changed structure to
present proper TOC</td>
</tr>
<tr>
<td align="left">Revision 1.3.1</td>
<td align="left">2001-07-26</td>
<td align="left">Revised by: ppadala</td>
</tr>
<tr>
<td align="left" colspan="3">Corrected maintainers
paragraph, Corrected stable release number</td>
</tr>
<tr>
<td align="left">Revision 1.3</td>
<td align="left">2001-07-24</td>
<td align="left">Revised by: ppadala</td>
</tr>
<tr>
<td align="left" colspan="3">Added copyright notices to
main document (LDP license) and programs (GPL),
Corrected printw_example.</td>
</tr>
<tr>
<td align="left">Revision 1.2</td>
<td align="left">2001-06-05</td>
<td align="left">Revised by: ppadala</td>
</tr>
<tr>
<td align="left" colspan="3">Incorporated ravi's
changes. Mainly to introduction, menu, form, justforfun
sections</td>
</tr>
<tr>
<td align="left">Revision 1.1</td>
<td align="left">2001-05-22</td>
<td align="left">Revised by: ppadala</td>
</tr>
<tr>
<td align="left" colspan="3">Added "a word about
window" section, Added scanw_example.</td>
</tr>
</table>
</div>
<div>
<div class="ABSTRACT">
<a name="AEN67" id="AEN67"></a>
<p><span class="emphasis"><i class="EMPHASIS">This
document is intended to be an "All in One" guide for
programming with ncurses and its sister libraries. We
graduate from a simple "Hello World" program to more
complex form manipulation. No prior experience in ncurses
is assumed. Send comments to <a href=
"mailto:ppadala@gmail.com" target="_top">this
address</a></i></span></p>
</div>
</div>
<hr>
</div>
<div class="TOC">
<dl>
<dt><b>Table of Contents</b></dt>
<dt>1. <a href="#INTRO">Introduction</a></dt>
<dd>
<dl>
<dt>1.1. <a href="#WHATIS">What is NCURSES?</a></dt>
<dt>1.2. <a href="#WHATCANWEDO">What we can do with
NCURSES</a></dt>
<dt>1.3. <a href="#WHERETOGETIT">Where to get
it</a></dt>
<dt>1.4. <a href="#PURPOSE">Purpose/Scope of the
document</a></dt>
<dt>1.5. <a href="#ABOUTPROGRAMS">About the
Programs</a></dt>
<dt>1.6. <a href="#OTHERFORMATS">Other Formats of the
document</a></dt>
<dd>
<dl>
<dt>1.6.1. <a href="#LISTFORMATS">Readily available
formats from tldp.org</a></dt>
<dt>1.6.2. <a href="#BUILDSOURCE">Building from
source</a></dt>
</dl>
</dd>
<dt>1.7. <a href="#CREDITS">Credits</a></dt>
<dt>1.8. <a href="#WISHLIST">Wish List</a></dt>
<dt>1.9. <a href="#COPYRIGHT">Copyright</a></dt>
</dl>
</dd>
<dt>2. <a href="#HELLOWORLD">Hello World !!!</a></dt>
<dd>
<dl>
<dt>2.1. <a href="#COMPILECURSES">Compiling With the
NCURSES Library</a></dt>
<dt>2.2. <a href="#DISSECTION">Dissection</a></dt>
<dd>
<dl>
<dt>2.2.1. <a href="#ABOUT-INITSCR">About
initscr()</a></dt>
<dt>2.2.2. <a href="#MYST-REFRESH">The mysterious
refresh()</a></dt>
<dt>2.2.3. <a href="#ABOUT-ENDWIN">About
endwin()</a></dt>
</dl>
</dd>
</dl>
</dd>
<dt>3. <a href="#GORY">The Gory Details</a></dt>
<dt>4. <a href="#INIT">Initialization</a></dt>
<dd>
<dl>
<dt>4.1. <a href="#ABOUTINIT">Initialization
functions</a></dt>
<dt>4.2. <a href="#RAWCBREAK">raw() and
cbreak()</a></dt>
<dt>4.3. <a href="#ECHONOECHO">echo() and
noecho()</a></dt>
<dt>4.4. <a href="#KEYPAD">keypad()</a></dt>
<dt>4.5. <a href="#HALFDELAY">halfdelay()</a></dt>
<dt>4.6. <a href="#MISCINIT">Miscellaneous
Initialization functions</a></dt>
<dt>4.7. <a href="#INITEX">An Example</a></dt>
</dl>
</dd>
<dt>5. <a href="#AWORDWINDOWS">A Word about
Windows</a></dt>
<dt>6. <a href="#PRINTW">Output functions</a></dt>
<dd>
<dl>
<dt>6.1. <a href="#ADDCHCLASS">addch() class of
functions</a></dt>
<dt>6.2. <a href="#AEN298">mvaddch(), waddch() and
mvwaddch()</a></dt>
<dt>6.3. <a href="#PRINTWCLASS">printw() class of
functions</a></dt>
<dd>
<dl>
<dt>6.3.1. <a href="#PRINTWMVPRINTW">printw() and
mvprintw</a></dt>
<dt>6.3.2. <a href="#WPRINTWMVWPRINTW">wprintw()
and mvwprintw</a></dt>
<dt>6.3.3. <a href="#VWPRINTW">vw_printw()</a></dt>
<dt>6.3.4. <a href="#SIMPLEPRINTWEX">A Simple
printw example</a></dt>
</dl>
</dd>
<dt>6.4. <a href="#ADDSTRCLASS">addstr() class of
functions</a></dt>
<dt>6.5. <a href="#ACAUTION">A word of caution</a></dt>
</dl>
</dd>
<dt>7. <a href="#SCANW">Input functions</a></dt>
<dd>
<dl>
<dt>7.1. <a href="#GETCHCLASS">getch() class of
functions</a></dt>
<dt>7.2. <a href="#SCANWCLASS">scanw() class of
functions</a></dt>
<dd>
<dl>
<dt>7.2.1. <a href="#SCANWMVSCANW">scanw() and
mvscanw</a></dt>
<dt>7.2.2. <a href="#WSCANWMVWSCANW">wscanw() and
mvwscanw()</a></dt>
<dt>7.2.3. <a href="#VWSCANW">vw_scanw()</a></dt>
</dl>
</dd>
<dt>7.3. <a href="#GETSTRCLASS">getstr() class of
functions</a></dt>
<dt>7.4. <a href="#GETSTREX">Some examples</a></dt>
</dl>
</dd>
<dt>8. <a href="#ATTRIB">Attributes</a></dt>
<dd>
<dl>
<dt>8.1. <a href="#ATTRIBDETAILS">The details</a></dt>
<dt>8.2. <a href="#ATTRONVSATTRSET">attron() vs
attrset()</a></dt>
<dt>8.3. <a href="#ATTRGET">attr_get()</a></dt>
<dt>8.4. <a href="#ATTRFUNCS">attr_ functions</a></dt>
<dt>8.5. <a href="#WATTRFUNCS">wattr functions</a></dt>
<dt>8.6. <a href="#CHGAT">chgat() functions</a></dt>
</dl>
</dd>
<dt>9. <a href="#WINDOWS">Windows</a></dt>
<dd>
<dl>
<dt>9.1. <a href="#WINDOWBASICS">The basics</a></dt>
<dt>9.2. <a href="#LETBEWINDOW">Let there be a Window
!!!</a></dt>
<dt>9.3. <a href="#BORDEREXEXPL">Explanation</a></dt>
<dt>9.4. <a href="#OTHERSTUFF">The other stuff in the
example</a></dt>
<dt>9.5. <a href="#OTHERBORDERFUNCS">Other Border
functions</a></dt>
</dl>
</dd>
<dt>10. <a href="#COLOR">Colors</a></dt>
<dd>
<dl>
<dt>10.1. <a href="#COLORBASICS">The basics</a></dt>
<dt>10.2. <a href="#CHANGECOLORDEFS">Changing Color
Definitions</a></dt>
<dt>10.3. <a href="#COLORCONTENT">Color
Content</a></dt>
</dl>
</dd>
<dt>11. <a href="#KEYS">Interfacing with the key
board</a></dt>
<dd>
<dl>
<dt>11.1. <a href="#KEYSBASICS">The Basics</a></dt>
<dt>11.2. <a href="#SIMPLEKEYEX">A Simple Key Usage
example</a></dt>
</dl>
</dd>
<dt>12. <a href="#MOUSE">Interfacing with the
mouse</a></dt>
<dd>
<dl>
<dt>12.1. <a href="#MOUSEBASICS">The Basics</a></dt>
<dt>12.2. <a href="#GETTINGEVENTS">Getting the
events</a></dt>
<dt>12.3. <a href="#MOUSETOGETHER">Putting it all
Together</a></dt>
<dt>12.4. <a href="#MISCMOUSEFUNCS">Miscellaneous
Functions</a></dt>
</dl>
</dd>
<dt>13. <a href="#SCREEN">Screen Manipulation</a></dt>
<dd>
<dl>
<dt>13.1. <a href="#GETYX">getyx() functions</a></dt>
<dt>13.2. <a href="#SCREENDUMP">Screen Dumping</a></dt>
<dt>13.3. <a href="#WINDOWDUMP">Window Dumping</a></dt>
</dl>
</dd>
<dt>14. <a href="#MISC">Miscellaneous features</a></dt>
<dd>
<dl>
<dt>14.1. <a href="#CURSSET">curs_set()</a></dt>
<dt>14.2. <a href="#TEMPLEAVE">Temporarily Leaving
Curses mode</a></dt>
<dt>14.3. <a href="#ACSVARS">ACS_ variables</a></dt>
</dl>
</dd>
<dt>15. <a href="#OTHERLIB">Other libraries</a></dt>
<dt>16. <a href="#PANELS">Panel Library</a></dt>
<dd>
<dl>
<dt>16.1. <a href="#PANELBASICS">The Basics</a></dt>
<dt>16.2. <a href="#COMPILEPANELS">Compiling With the
Panels Library</a></dt>
<dt>16.3. <a href="#PANELBROWSING">Panel Window
Browsing</a></dt>
<dt>16.4. <a href="#USERPTRUSING">Using User
Pointers</a></dt>
<dt>16.5. <a href="#PANELMOVERESIZE">Moving and
Resizing Panels</a></dt>
<dt>16.6. <a href="#PANELSHOWHIDE">Hiding and Showing
Panels</a></dt>
<dt>16.7. <a href="#PANELABOVE">panel_above() and
panel_below() Functions</a></dt>
</dl>
</dd>
<dt>17. <a href="#MENUS">Menus Library</a></dt>
<dd>
<dl>
<dt>17.1. <a href="#MENUBASICS">The Basics</a></dt>
<dt>17.2. <a href="#COMPILEMENUS">Compiling With the
Menu Library</a></dt>
<dt>17.3. <a href="#MENUDRIVER">Menu Driver: The work
horse of the menu system</a></dt>
<dt>17.4. <a href="#MENUWINDOWS">Menu Windows</a></dt>
<dt>17.5. <a href="#SCROLLMENUS">Scrolling
Menus</a></dt>
<dt>17.6. <a href="#MULTICOLUMN">Multi Columnar
Menus</a></dt>
<dt>17.7. <a href="#MULTIVALUEMENUS">Multi Valued
Menus</a></dt>
<dt>17.8. <a href="#MENUOPT">Menu Options</a></dt>
<dt>17.9. <a href="#MENUUSERPTR">The useful User
Pointer</a></dt>
</dl>
</dd>
<dt>18. <a href="#FORMS">Forms Library</a></dt>
<dd>
<dl>
<dt>18.1. <a href="#FORMBASICS">The Basics</a></dt>
<dt>18.2. <a href="#COMPILEFORMS">Compiling With the
Forms Library</a></dt>
<dt>18.3. <a href="#PLAYFIELDS">Playing with
Fields</a></dt>
<dd>
<dl>
<dt>18.3.1. <a href="#FETCHINFO">Fetching Size and
Location of Field</a></dt>
<dt>18.3.2. <a href="#MOVEFIELD">Moving the
field</a></dt>
<dt>18.3.3. <a href="#JUSTIFYFIELD">Field
Justification</a></dt>
<dt>18.3.4. <a href="#FIELDDISPATTRIB">Field
Display Attributes</a></dt>
<dt>18.3.5. <a href="#FIELDOPTIONBITS">Field Option
Bits</a></dt>
<dt>18.3.6. <a href="#FIELDSTATUS">Field
Status</a></dt>
<dt>18.3.7. <a href="#FIELDUSERPTR">Field User
Pointer</a></dt>
<dt>18.3.8. <a href=
"#VARIABLESIZEFIELDS">Variable-Sized
Fields</a></dt>
</dl>
</dd>
<dt>18.4. <a href="#FORMWINDOWS">Form Windows</a></dt>
<dt>18.5. <a href="#FILEDVALIDATE">Field
Validation</a></dt>
<dt>18.6. <a href="#FORMDRIVER">Form Driver: The work
horse of the forms system</a></dt>
<dd>
<dl>
<dt>18.6.1. <a href="#PAGENAVREQ">Page Navigation
Requests</a></dt>
<dt>18.6.2. <a href="#INTERFIELDNAVREQ">Inter-Field
Navigation Requests</a></dt>
<dt>18.6.3. <a href="#INTRAFIELDNAVREQ">Intra-Field
Navigation Requests</a></dt>
<dt>18.6.4. <a href="#SCROLLREQ">Scrolling
Requests</a></dt>
<dt>18.6.5. <a href="#EDITREQ">Editing
Requests</a></dt>
<dt>18.6.6. <a href="#ORDERREQ">Order
Requests</a></dt>
<dt>18.6.7. <a href="#APPLICCOMMANDS">Application
Commands</a></dt>
</dl>
</dd>
</dl>
</dd>
<dt>19. <a href="#TOOLS">Tools and Widget
Libraries</a></dt>
<dd>
<dl>
<dt>19.1. <a href="#CDK">CDK (Curses Development
Kit)</a></dt>
<dd>
<dl>
<dt>19.1.1. <a href="#WIDGETLIST">Widget
List</a></dt>
<dt>19.1.2. <a href="#CDKATTRACT">Some Attractive
Features</a></dt>
<dt>19.1.3. <a href=
"#CDKCONCLUSION">Conclusion</a></dt>
</dl>
</dd>
<dt>19.2. <a href="#DIALOG">The dialog</a></dt>
<dt>19.3. <a href="#PERLCURSES">Perl Curses Modules
CURSES::FORM and CURSES::WIDGETS</a></dt>
</dl>
</dd>
<dt>20. <a href="#JUSTFORFUN">Just For Fun !!!</a></dt>
<dd>
<dl>
<dt>20.1. <a href="#GAMEOFLIFE">The Game of
Life</a></dt>
<dt>20.2. <a href="#MAGIC">Magic Square</a></dt>
<dt>20.3. <a href="#HANOI">Towers of Hanoi</a></dt>
<dt>20.4. <a href="#QUEENS">Queens Puzzle</a></dt>
<dt>20.5. <a href="#SHUFFLE">Shuffle</a></dt>
<dt>20.6. <a href="#TT">Typing Tutor</a></dt>
</dl>
</dd>
<dt>21. <a href="#REF">References</a></dt>
</dl>
</div>
<div class="SECT1">
<h2 class="SECT1"><a name="INTRO" id="INTRO">1.
Introduction</a></h2>
<p>In the olden days of teletype terminals, terminals were
away from computers and were connected to them through serial
cables. The terminals could be configured by sending a series
of bytes. All the capabilities (such as moving the cursor to
a new location, erasing part of the screen, scrolling the
screen, changing modes etc.) of terminals could be accessed
through these series of bytes. These control seeuqnces are
usually called escape sequences, because they start with an
escape(0x1B) character. Even today, with proper emulation, we
can send escape sequences to the emulator and achieve the
same effect on a terminal window.</p>
<p>Suppose you wanted to print a line in color. Try typing
this on your console.</p>
<pre class="PROGRAMLISTING">
echo "^[[0;31;40mIn Color"
</pre>
<p>The first character is an escape character, which looks
like two characters ^ and [. To be able to print it, you have
to press CTRL+V and then the ESC key. All the others are
normal printable characters. You should be able to see the
string "In Color" in red. It stays that way and to revert
back to the original mode type this.</p>
<pre class="PROGRAMLISTING">
echo "^[[0;37;40m"
</pre>
<p>Now, what do these magic characters mean? Difficult to
comprehend? They might even be different for different
terminals. So the designers of UNIX invented a mechanism
named <tt class="LITERAL">termcap</tt>. It is a file that
lists all the capabilities of a particular terminal, along
with the escape sequences needed to achieve a particular
effect. In the later years, this was replaced by <tt class=
"LITERAL">terminfo</tt>. Without delving too much into
details, this mechanism allows application programs to query
the terminfo database and obtain the control characters to be
sent to a terminal or terminal emulator.</p>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="WHATIS" id="WHATIS">1.1. What is
NCURSES?</a></h3>
<p>You might be wondering, what the import of all this
technical gibberish is. In the above scenario, every
application program is supposed to query the terminfo and
perform the necessary stuff (sending control characters
etc.). It soon became difficult to manage this complexity
and this gave birth to 'CURSES'. Curses is a pun on the
name "cursor optimization". The Curses library forms a
wrapper over working with raw terminal codes, and provides
highly flexible and efficient API (Application Programming
Interface). It provides functions to move the cursor,
create windows, produce colors, play with mouse etc. The
application programs need not worry about the underlying
terminal capabilities.</p>
<p>So what is NCURSES? NCURSES is a clone of the original
System V Release 4.0 (SVr4) curses. It is a freely
distributable library, fully compatible with older version
of curses. In short, it is a library of functions that
manages an application's display on character-cell
terminals. In the remainder of the document, the terms
curses and ncurses are used interchangeably.</p>
<p>A detailed history of NCURSES can be found in the NEWS
file from the source distribution. The current package is
maintained by <a href="mailto:dickey@his.com" target=
"_top">Thomas Dickey</a>. You can contact the maintainers
at <a href="mailto:bug-ncurses@gnu.org" target=
"_top">bug-ncurses@gnu.org</a>.</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="WHATCANWEDO" id=
"WHATCANWEDO">1.2. What we can do with NCURSES</a></h3>
<p>NCURSES not only creates a wrapper over terminal
capabilities, but also gives a robust framework to create
nice looking UI (User Interface)s in text mode. It provides
functions to create windows etc. Its sister libraries
panel, menu and form provide an extension to the basic
curses library. These libraries usually come along with
curses. One can create applications that contain multiple
windows, menus, panels and forms. Windows can be managed
independently, can provide 'scrollability' and even can be
hidden.</p>
<p>Menus provide the user with an easy command selection
option. Forms allow the creation of easy-to-use data entry
and display windows. Panels extend the capabilities of
ncurses to deal with overlapping and stacked windows.</p>
<p>These are just some of the basic things we can do with
ncurses. As we move along, We will see all the capabilities
of these libraries.</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="WHERETOGETIT" id=
"WHERETOGETIT">1.3. Where to get it</a></h3>
<p>All right, now that you know what you can do with
ncurses, you must be rearing to get started. NCURSES is
usually shipped with your installation. In case you don't
have the library or want to compile it on your own, read
on.</p>
<p><span class="emphasis"><i class="EMPHASIS">Compiling the
package</i></span></p>
<p>NCURSES can be obtained from <a href=
"ftp://ftp.gnu.org/pub/gnu/ncurses/ncurses.tar.gz" target=
"_top">ftp://ftp.gnu.org/pub/gnu/ncurses/ncurses.tar.gz</a>
or any of the ftp sites mentioned in <a href=
"http://www.gnu.org/order/ftp.html" target=
"_top">http://www.gnu.org/order/ftp.html</a>.</p>
<p>Read the README and INSTALL files for details on to how
to install it. It usually involves the following
operations.</p>
<pre class="PROGRAMLISTING">
tar zxvf ncurses<version>.tar.gz # unzip and untar the archive
cd ncurses<version> # cd to the directory
./configure # configure the build according to your
# environment
make # make it
su root # become root
make install # install it
</pre>
<p><span class="emphasis"><i class="EMPHASIS">Using the
RPM</i></span></p>
<p>NCURSES RPM can be found and downloaded from <a href=
"http://rpmfind.net" target="_top">http://rpmfind.net</a> .
The RPM can be installed with the following command after
becoming root.</p>
<pre class="PROGRAMLISTING">
rpm -i <downloaded rpm>
</pre>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="PURPOSE" id="PURPOSE">1.4.
Purpose/Scope of the document</a></h3>
<p>This document is intended to be a "All in One" guide for
programming with ncurses and its sister libraries. We
graduate from a simple "Hello World" program to more
complex form manipulation. No prior experience in ncurses
is assumed. The writing is informal, but a lot of detail is
provided for each of the examples.</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="ABOUTPROGRAMS" id=
"ABOUTPROGRAMS">1.5. About the Programs</a></h3>
<p>All the programs in the document are available in zipped
form <a href=
"http://www.tldp.org/HOWTO/NCURSES-Programming-HOWTO/ncurses_programs.tar.gz"
target="_top">here</a>. Unzip and untar it. The directory
structure looks like this.</p>
<pre class="PROGRAMLISTING">
ncurses
|
|----> JustForFun -- just for fun programs
|----> basics -- basic programs
|----> demo -- output files go into this directory after make
| |
| |----> exe -- exe files of all example programs
|----> forms -- programs related to form library
|----> menus -- programs related to menus library
|----> panels -- programs related to panels library
|----> perl -- perl equivalents of the examples (contributed
| by Anuradha Ratnaweera)
|----> Makefile -- the top level Makefile
|----> README -- the top level README file. contains instructions
|----> COPYING -- copyright notice
</pre>
<p>The individual directories contain the following
files.</p>
<pre class="PROGRAMLISTING">
Description of files in each directory
--------------------------------------
JustForFun
|
|----> hanoi.c -- The Towers of Hanoi Solver
|----> life.c -- The Game of Life demo
|----> magic.c -- An Odd Order Magic Square builder
|----> queens.c -- The famous N-Queens Solver
|----> shuffle.c -- A fun game, if you have time to kill
|----> tt.c -- A very trivial typing tutor
basics
|
|----> acs_vars.c -- ACS_ variables example
|----> hello_world.c -- Simple "Hello World" Program
|----> init_func_example.c -- Initialization functions example
|----> key_code.c -- Shows the scan code of the key pressed
|----> mouse_menu.c -- A menu accessible by mouse
|----> other_border.c -- Shows usage of other border functions apa
| -- rt from box()
|----> printw_example.c -- A very simple printw() example
|----> scanw_example.c -- A very simple getstr() example
|----> simple_attr.c -- A program that can print a c file with
| -- comments in attribute
|----> simple_color.c -- A simple example demonstrating colors
|----> simple_key.c -- A menu accessible with keyboard UP, DOWN
| -- arrows
|----> temp_leave.c -- Demonstrates temporarily leaving curses mode
|----> win_border.c -- Shows Creation of windows and borders
|----> with_chgat.c -- chgat() usage example
forms
|
|----> form_attrib.c -- Usage of field attributes
|----> form_options.c -- Usage of field options
|----> form_simple.c -- A simple form example
|----> form_win.c -- Demo of windows associated with forms
menus
|
|----> menu_attrib.c -- Usage of menu attributes
|----> menu_item_data.c -- Usage of item_name() etc.. functions
|----> menu_multi_column.c -- Creates multi columnar menus
|----> menu_scroll.c -- Demonstrates scrolling capability of menus
|----> menu_simple.c -- A simple menu accessed by arrow keys
|----> menu_toggle.c -- Creates multi valued menus and explains
| -- REQ_TOGGLE_ITEM
|----> menu_userptr.c -- Usage of user pointer
|----> menu_win.c -- Demo of windows associated with menus
panels
|
|----> panel_browse.c -- Panel browsing through tab. Usage of user
| -- pointer
|----> panel_hide.c -- Hiding and Un hiding of panels
|----> panel_resize.c -- Moving and resizing of panels
|----> panel_simple.c -- A simple panel example
perl
|----> 01-10.pl -- Perl equivalents of first ten example programs
</pre>
<p>There is a top level Makefile included in the main
directory. It builds all the files and puts the
ready-to-use exes in demo/exe directory. You can also do
selective make by going into the corresponding directory.
Each directory contains a README file explaining the
purpose of each c file in the directory.</p>
<p>For every example, I have included path name for the
file relative to the examples directory.</p>
<p>If you prefer browsing individual programs, point your
browser to <a href=
"http://tldp.org/HOWTO/NCURSES-Programming-HOWTO/ncurses_programs/"
target=
"_top">http://tldp.org/HOWTO/NCURSES-Programming-HOWTO/ncurses_programs/</a></p>
<p>All the programs are released under the same license
that is used by ncurses (MIT-style). This gives you the
ability to do pretty much anything other than claiming them
as yours. Feel free to use them in your programs as
appropriate.</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="OTHERFORMATS" id=
"OTHERFORMATS">1.6. Other Formats of the document</a></h3>
<p>This howto is also availabe in various other formats on
the tldp.org site. Here are the links to other formats of
this document.</p>
<div class="SECT3">
<hr>
<h4 class="SECT3"><a name="LISTFORMATS" id=
"LISTFORMATS">1.6.1. Readily available formats from
tldp.org</a></h4>
<ul>
<li>
<p><a href=
"http://www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/pdf/NCURSES-Programming-HOWTO.pdf"
target="_top">Acrobat PDF Format</a></p>
</li>
<li>
<p><a href=
"http://www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/ps/NCURSES-Programming-HOWTO.ps.gz"
target="_top">PostScript Format</a></p>
</li>
<li>
<p><a href=
"http://www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/html/NCURSES-Programming-HOWTO-html.tar.gz"
target="_top">In Multiple HTML pages</a></p>
</li>
<li>
<p><a href=
"http://www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/html_single/NCURSES-Programming-HOWTO.html"
target="_top">In One big HTML format</a></p>
</li>
</ul>
</div>
<div class="SECT3">
<hr>
<h4 class="SECT3"><a name="BUILDSOURCE" id=
"BUILDSOURCE">1.6.2. Building from source</a></h4>
<p>If above links are broken or if you want to experiment
with sgml read on.</p>
<pre class="PROGRAMLISTING">
Get both the source and the tar,gzipped programs, available at
http://cvsview.tldp.org/index.cgi/LDP/howto/docbook/
NCURSES-HOWTO/NCURSES-Programming-HOWTO.sgml
http://cvsview.tldp.org/index.cgi/LDP/howto/docbook/
NCURSES-HOWTO/ncurses_programs.tar.gz
Unzip ncurses_programs.tar.gz with
tar zxvf ncurses_programs.tar.gz
Use jade to create various formats. For example if you just want to create
the multiple html files, you would use
jade -t sgml -i html -d <path to docbook html stylesheet>
NCURSES-Programming-HOWTO.sgml
to get pdf, first create a single html file of the HOWTO with
jade -t sgml -i html -d <path to docbook html stylesheet> -V nochunks
NCURSES-Programming-HOWTO.sgml > NCURSES-ONE-BIG-FILE.html
then use htmldoc to get pdf file with
htmldoc --size universal -t pdf --firstpage p1 -f <output file name.pdf>
NCURSES-ONE-BIG-FILE.html
for ps, you would use
htmldoc --size universal -t ps --firstpage p1 -f <output file name.ps>
NCURSES-ONE-BIG-FILE.html
</pre>
<p>See <a href=
"http://www.tldp.org/LDP/LDP-Author-Guide/" target=
"_top">LDP Author guide</a> for more details. If all else
failes, mail me at <a href="ppadala@gmail.com" target=
"_top">ppadala@gmail.com</a></p>
</div>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="CREDITS" id="CREDITS">1.7.
Credits</a></h3>
<p>I thank <a href="mailto:sharath_1@usa.net" target=
"_top">Sharath</a> and Emre Akbas for helping me with few
sections. The introduction was initially written by
sharath. I rewrote it with few excerpts taken from his
initial work. Emre helped in writing printw and scanw
sections.</p>
<p>Perl equivalents of the example programs are contributed
by <a href="mailto:Aratnaweera@virtusa.com" target=
"_top">Anuradha Ratnaweera</a>.</p>
<p>Then comes <a href="mailto:parimi@ece.arizona.edu"
target="_top">Ravi Parimi</a>, my dearest friend, who has
been on this project before even one line was written. He
constantly bombarded me with suggestions and patiently
reviewed the whole text. He also checked each program on
Linux and Solaris.</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="WISHLIST" id="WISHLIST">1.8.
Wish List</a></h3>
<p>This is the wish list, in the order of priority. If you
have a wish or you want to work on completing the wish,
mail <a href="mailto:ppadala@gmail.com" target=
"_top">me</a>.</p>
<ul>
<li>
<p>Add examples to last parts of forms section.</p>
</li>
<li>
<p>Prepare a Demo showing all the programs and allow
the user to browse through description of each program.
Let the user compile and see the program in action. A
dialog based interface is preferred.</p>
</li>
<li>
<p>Add debug info. _tracef, _tracemouse stuff.</p>
</li>
<li>
<p>Accessing termcap, terminfo using functions provided
by ncurses package.</p>
</li>
<li>
<p>Working on two terminals simultaneously.</p>
</li>
<li>
<p>Add more stuff to miscellaneous section.</p>
</li>
</ul>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="COPYRIGHT" id="COPYRIGHT">1.9.
Copyright</a></h3>
<p>Copyright © 2001 by Pradeep Padala.</p>
<p>Permission is hereby granted, free of charge, to any
person obtaining a copy of this software and associated
documentation files (the "Software"), to deal in the
Software without restriction, including without limitation
the rights to use, copy, modify, merge, publish,
distribute, distribute with modifications, sublicense,
and/or sell copies of the Software, and to permit persons
to whom the Software is furnished to do so, subject to the
following conditions:</p>
<p>The above copyright notice and this permission notice
shall be included in all copies or substantial portions of
the Software.</p>
<p>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF
ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE ABOVE
COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.</p>
<p>Except as contained in this notice, the name(s) of the
above copyright holders shall not be used in advertising or
otherwise to promote the sale, use or other dealings in
this Software without prior written authorization.</p>
</div>
</div>
<div class="SECT1">
<hr>
<h2 class="SECT1"><a name="HELLOWORLD" id="HELLOWORLD">2.
Hello World !!!</a></h2>
<p>Welcome to the world of curses. Before we plunge into the
library and look into its various features, let's write a
simple program and say hello to the world.</p>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="COMPILECURSES" id=
"COMPILECURSES">2.1. Compiling With the NCURSES
Library</a></h3>
<p>To use ncurses library functions, you have to include
ncurses.h in your programs. To link the program with
ncurses the flag -lncurses should be added.</p>
<pre class="PROGRAMLISTING">
#include <ncurses.h>
.
.
.
compile and link: gcc <program file> -lncurses
</pre>
<div class="EXAMPLE">
<a name="BHW" id="BHW"></a>
<p><b>Example 1. The Hello World !!! Program</b></p>
<pre class="PROGRAMLISTING">
<span class="INLINEMEDIAOBJECT">#include <ncurses.h>
int main()
{
initscr(); /* Start curses mode */
printw("Hello World !!!"); /* Print Hello World */
refresh(); /* Print it on to the real screen */
getch(); /* Wait for user input */
endwin(); /* End curses mode */
return 0;
}</span>
</pre>
</div>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="DISSECTION" id="DISSECTION">2.2.
Dissection</a></h3>
<p>The above program prints "Hello World !!!" to the screen
and exits. This program shows how to initialize curses and
do screen manipulation and end curses mode. Let's dissect
it line by line.</p>
<div class="SECT3">
<hr>
<h4 class="SECT3"><a name="ABOUT-INITSCR" id=
"ABOUT-INITSCR">2.2.1. About initscr()</a></h4>
<p>The function initscr() initializes the terminal in
curses mode. In some implementations, it clears the
screen and presents a blank screen. To do any screen
manipulation using curses package this has to be called
first. This function initializes the curses system and
allocates memory for our present window (called
<tt class="LITERAL">stdscr</tt>) and some other
data-structures. Under extreme cases this function might
fail due to insufficient memory to allocate memory for
curses library's data structures.</p>
<p>After this is done, we can do a variety of
initializations to customize our curses settings. These
details will be explained <a href="#INIT">later</a> .</p>
</div>
<div class="SECT3">
<hr>
<h4 class="SECT3"><a name="MYST-REFRESH" id=
"MYST-REFRESH">2.2.2. The mysterious refresh()</a></h4>
<p>The next line printw prints the string "Hello World
!!!" on to the screen. This function is analogous to
normal printf in all respects except that it prints the
data on a window called stdscr at the current (y,x)
co-ordinates. Since our present co-ordinates are at 0,0
the string is printed at the left hand corner of the
window.</p>
<p>This brings us to that mysterious refresh(). Well,
when we called printw the data is actually written to an
imaginary window, which is not updated on the screen yet.
The job of printw is to update a few flags and data
structures and write the data to a buffer corresponding
to stdscr. In order to show it on the screen, we need to
call refresh() and tell the curses system to dump the
contents on the screen.</p>
<p>The philosophy behind all this is to allow the
programmer to do multiple updates on the imaginary screen
or windows and do a refresh once all his screen update is
done. refresh() checks the window and updates only the
portion which has been changed. This improves performance
and offers greater flexibility too. But, it is sometimes
frustrating to beginners. A common mistake committed by
beginners is to forget to call refresh() after they did
some update through printw() class of functions. I still
forget to add it sometimes :-)</p>
</div>
<div class="SECT3">
<hr>
<h4 class="SECT3"><a name="ABOUT-ENDWIN" id=
"ABOUT-ENDWIN">2.2.3. About endwin()</a></h4>
<p>And finally don't forget to end the curses mode.
Otherwise your terminal might behave strangely after the
program quits. endwin() frees the memory taken by curses
sub-system and its data structures and puts the terminal
in normal mode. This function must be called after you
are done with the curses mode.</p>
</div>
</div>
</div>
<div class="SECT1">
<hr>
<h2 class="SECT1"><a name="GORY" id="GORY">3. The Gory
Details</a></h2>
<p>Now that we have seen how to write a simple curses program
let's get into the details. There are many functions that
help customize what you see on screen and many features which
can be put to full use.</p>
<p>Here we go...</p>
</div>
<div class="SECT1">
<hr>
<h2 class="SECT1"><a name="INIT" id="INIT">4.
Initialization</a></h2>
<p>We now know that to initialize curses system the function
initscr() has to be called. There are functions which can be
called after this initialization to customize our curses
session. We may ask the curses system to set the terminal in
raw mode or initialize color or initialize the mouse etc..
Let's discuss some of the functions that are normally called
immediately after initscr();</p>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="ABOUTINIT" id="ABOUTINIT">4.1.
Initialization functions</a></h3>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="RAWCBREAK" id="RAWCBREAK">4.2.
raw() and cbreak()</a></h3>
<p>Normally the terminal driver buffers the characters a
user types until a new line or carriage return is
encountered. But most programs require that the characters
be available as soon as the user types them. The above two
functions are used to disable line buffering. The
difference between these two functions is in the way
control characters like suspend (CTRL-Z), interrupt and
quit (CTRL-C) are passed to the program. In the raw() mode
these characters are directly passed to the program without
generating a signal. In the <tt class=
"LITERAL">cbreak()</tt> mode these control characters are
interpreted as any other character by the terminal driver.
I personally prefer to use raw() as I can exercise greater
control over what the user does.</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="ECHONOECHO" id="ECHONOECHO">4.3.
echo() and noecho()</a></h3>
<p>These functions control the echoing of characters typed
by the user to the terminal. <tt class=
"LITERAL">noecho()</tt> switches off echoing. The reason
you might want to do this is to gain more control over
echoing or to suppress unnecessary echoing while taking
input from the user through the getch() etc. functions.
Most of the interactive programs call <tt class=
"LITERAL">noecho()</tt> at initialization and do the
echoing of characters in a controlled manner. It gives the
programmer the flexibility of echoing characters at any
place in the window without updating current (y,x)
co-ordinates.</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="KEYPAD" id="KEYPAD">4.4.
keypad()</a></h3>
<p>This is my favorite initialization function. It enables
the reading of function keys like F1, F2, arrow keys etc.
Almost every interactive program enables this, as arrow
keys are a major part of any User Interface. Do <tt class=
"LITERAL">keypad(stdscr, TRUE)</tt> to enable this feature
for the regular screen (stdscr). You will learn more about
key management in later sections of this document.</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="HALFDELAY" id="HALFDELAY">4.5.
halfdelay()</a></h3>
<p>This function, though not used very often, is a useful
one at times. halfdelay()is called to enable the half-delay
mode, which is similar to the cbreak() mode in that
characters typed are immediately available to program.
However, it waits for 'X' tenths of a second for input and
then returns ERR, if no input is available. 'X' is the
timeout value passed to the function halfdelay(). This
function is useful when you want to ask the user for input,
and if he doesn't respond with in certain time, we can do
some thing else. One possible example is a timeout at the
password prompt.</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="MISCINIT" id="MISCINIT">4.6.
Miscellaneous Initialization functions</a></h3>
<p>There are few more functions which are called at
initialization to customize curses behavior. They are not
used as extensively as those mentioned above. Some of them
are explained where appropriate.</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="INITEX" id="INITEX">4.7. An
Example</a></h3>
<p>Let's write a program which will clarify the usage of
these functions.</p>
<div class="EXAMPLE">
<a name="BINFU" id="BINFU"></a>
<p><b>Example 2. Initialization Function Usage
example</b></p>
<pre class="PROGRAMLISTING">
<span class="INLINEMEDIAOBJECT">#include <ncurses.h>
int main()
{ int ch;
initscr(); /* Start curses mode */
raw(); /* Line buffering disabled */
keypad(stdscr, TRUE); /* We get F1, F2 etc.. */
noecho(); /* Don't echo() while we do getch */
printw("Type any character to see it in bold\n");
ch = getch(); /* If raw() hadn't been called
* we have to press enter before it
* gets to the program */
if(ch == KEY_F(1)) /* Without keypad enabled this will */
printw("F1 Key pressed");/* not get to us either */
/* Without noecho() some ugly escape
* charachters might have been printed
* on screen */
else
{ printw("The pressed key is ");
attron(A_BOLD);
printw("%c", ch);
attroff(A_BOLD);
}
refresh(); /* Print it on to the real screen */
getch(); /* Wait for user input */
endwin(); /* End curses mode */
return 0;
}</span>
</pre>
</div>
<p>This program is self-explanatory. But I used functions
which aren't explained yet. The function <tt class=
"LITERAL">getch()</tt> is used to get a character from
user. It is equivalent to normal <tt class=
"LITERAL">getchar()</tt> except that we can disable the
line buffering to avoid <enter> after input. Look for
more about <tt class="LITERAL">getch()</tt>and reading keys
in the <a href="#KEYS">key management section</a> . The
functions attron and attroff are used to switch some
attributes on and off respectively. In the example I used
them to print the character in bold. These functions are
explained in detail later.</p>
</div>
</div>
<div class="SECT1">
<hr>
<h2 class="SECT1"><a name="AWORDWINDOWS" id="AWORDWINDOWS">5.
A Word about Windows</a></h2>
<p>Before we plunge into the myriad ncurses functions, let me
clear few things about windows. Windows are explained in
detail in following <a href="#WINDOWS">sections</a></p>
<p>A Window is an imaginary screen defined by curses system.
A window does not mean a bordered window which you usually
see on Win9X platforms. When curses is initialized, it
creates a default window named <tt class=
"LITERAL">stdscr</tt> which represents your 80x25 (or the
size of window in which you are running) screen. If you are
doing simple tasks like printing few strings, reading input
etc., you can safely use this single window for all of your
purposes. You can also create windows and call functions
which explicitly work on the specified window.</p>
<p>For example, if you call</p>
<pre class="PROGRAMLISTING">
printw("Hi There !!!");
refresh();
</pre>
<p>It prints the string on stdscr at the present cursor
position. Similarly the call to refresh(), works on stdscr
only.</p>
<p>Say you have created <a href="#WINDOWS">windows</a> then
you have to call a function with a 'w' added to the usual
function.</p>
<pre class="PROGRAMLISTING">
wprintw(win, "Hi There !!!");
wrefresh(win);
</pre>
<p>As you will see in the rest of the document, naming of
functions follow the same convention. For each function there
usually are three more functions.</p>
<pre class="PROGRAMLISTING">
printw(string); /* Print on stdscr at present cursor position */
mvprintw(y, x, string);/* Move to (y, x) then print string */
wprintw(win, string); /* Print on window win at present cursor position */
/* in the window */
mvwprintw(win, y, x, string); /* Move to (y, x) relative to window */
/* co-ordinates and then print */
</pre>
<p>Usually the w-less functions are macros which expand to
corresponding w-function with stdscr as the window
parameter.</p>
</div>
<div class="SECT1">
<hr>
<h2 class="SECT1"><a name="PRINTW" id="PRINTW">6. Output
functions</a></h2>
<p>I guess you can't wait any more to see some action. Back
to our odyssey of curses functions. Now that curses is
initialized, let's interact with world.</p>
<p>There are three classes of functions which you can use to
do output on screen.</p>
<ol type="1">
<li>
<p>addch() class: Print single character with
attributes</p>
</li>
<li>
<p>printw() class: Print formatted output similar to
printf()</p>
</li>
<li>
<p>addstr() class: Print strings</p>
</li>
</ol>
<p>These functions can be used interchangeably and it's a
matter of style as to which class is used. Let's see each one
in detail.</p>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="ADDCHCLASS" id="ADDCHCLASS">6.1.
addch() class of functions</a></h3>
<p>These functions put a single character into the current
cursor location and advance the position of the cursor. You
can give the character to be printed but they usually are
used to print a character with some attributes. Attributes
are explained in detail in later <a href=
"#ATTRIB">sections</a> of the document. If a character is
associated with an attribute(bold, reverse video etc.),
when curses prints the character, it is printed in that
attribute.</p>
<p>In order to combine a character with some attributes,
you have two options:</p>
<ul>
<li>
<p>By OR'ing a single character with the desired
attribute macros. These attribute macros could be found
in the header file <tt class="LITERAL">ncurses.h</tt>.
For example, you want to print a character ch(of type
char) bold and underlined, you would call addch() as
below.</p>
<pre class="PROGRAMLISTING">
addch(ch | A_BOLD | A_UNDERLINE);
</pre>
</li>
<li>
<p>By using functions like <tt class=
"LITERAL">attrset(),attron(),attroff()</tt>. These
functions are explained in the <a href=
"#ATTRIB">Attributes</a> section. Briefly, they
manipulate the current attributes of the given window.
Once set, the character printed in the window are
associated with the attributes until it is turned
off.</p>
</li>
</ul>
<p>Additionally, <tt class="LITERAL">curses</tt> provides
some special characters for character-based graphics. You
can draw tables, horizontal or vertical lines, etc. You can
find all avaliable characters in the header file <tt class=
"LITERAL">ncurses.h</tt>. Try looking for macros beginning
with <tt class="LITERAL">ACS_</tt> in this file.</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="AEN298" id="AEN298">6.2.
mvaddch(), waddch() and mvwaddch()</a></h3>
<p><tt class="LITERAL">mvaddch()</tt> is used to move the
cursor to a given point, and then print. Thus, the
calls:</p>
<pre class="PROGRAMLISTING">
move(row,col); /* moves the cursor to row<span class=
"emphasis"><i class=
"EMPHASIS">th</i></span> row and col<span class="emphasis"><i class="EMPHASIS">th</i></span> column */
addch(ch);
</pre>can be replaced by
<pre class="PROGRAMLISTING">
mvaddch(row,col,ch);
</pre>
<p><tt class="LITERAL">waddch()</tt> is similar to
<tt class="LITERAL">addch()</tt>, except that it adds a
character into the given window. (Note that <tt class=
"LITERAL">addch()</tt> adds a character into the window
<tt class="LITERAL">stdscr</tt>.)</p>
<p>In a similar fashion <tt class="LITERAL">mvwaddch()</tt>
function is used to add a character into the given window
at the given coordinates.</p>
<p>Now, we are familiar with the basic output function
<tt class="LITERAL">addch()</tt>. But, if we want to print
a string, it would be very annoying to print it character
by character. Fortunately, <tt class="LITERAL">ncurses</tt>
provides <tt class="LITERAL">printf</tt><span class=
"emphasis"><i class="EMPHASIS">-like</i></span> or
<tt class="LITERAL">puts</tt><span class=
"emphasis"><i class="EMPHASIS">-like</i></span>
functions.</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="PRINTWCLASS" id=
"PRINTWCLASS">6.3. printw() class of functions</a></h3>
<p>These functions are similar to <tt class=
"LITERAL">printf()</tt> with the added capability of
printing at any position on the screen.</p>
<div class="SECT3">
<hr>
<h4 class="SECT3"><a name="PRINTWMVPRINTW" id=
"PRINTWMVPRINTW">6.3.1. printw() and mvprintw</a></h4>
<p>These two functions work much like <tt class=
"LITERAL">printf()</tt>. <tt class=
"LITERAL">mvprintw()</tt> can be used to move the cursor
to a position and then print. If you want to move the
cursor first and then print using <tt class=
"LITERAL">printw()</tt> function, use <tt class=
"LITERAL">move()</tt> first and then use <tt class=
"LITERAL">printw()</tt> though I see no point why one
should avoid using <tt class="LITERAL">mvprintw()</tt>,
you have the flexibility to manipulate.</p>
</div>
<div class="SECT3">
<hr>
<h4 class="SECT3"><a name="WPRINTWMVWPRINTW" id=
"WPRINTWMVWPRINTW">6.3.2. wprintw() and
mvwprintw</a></h4>
<p>These two functions are similar to above two except
that they print in the corresponding window given as
argument.</p>
</div>
<div class="SECT3">
<hr>
<h4 class="SECT3"><a name="VWPRINTW" id="VWPRINTW">6.3.3.
vw_printw()</a></h4>
<p>This function is similar to <tt class=
"LITERAL">vprintf()</tt>. This can be used when variable
number of arguments are to be printed.</p>
</div>
<div class="SECT3">
<hr>
<h4 class="SECT3"><a name="SIMPLEPRINTWEX" id=
"SIMPLEPRINTWEX">6.3.4. A Simple printw example</a></h4>
<div class="EXAMPLE">
<a name="BPREX" id="BPREX"></a>
<p><b>Example 3. A Simple printw example</b></p>
<pre class="PROGRAMLISTING">
<span class=
"INLINEMEDIAOBJECT">#include <ncurses.h> /* ncurses.h includes stdio.h */
#include <string.h>
int main()
{
char mesg[]="Just a string"; /* message to be appeared on the screen */
int row,col; /* to store the number of rows and *
* the number of colums of the screen */
initscr(); /* start the curses mode */
getmaxyx(stdscr,row,col); /* get the number of rows and columns */
mvprintw(row/2,(col-strlen(mesg))/2,"%s",mesg);
/* print the message at the center of the screen */
mvprintw(row-2,0,"This screen has %d rows and %d columns\n",row,col);
printw("Try resizing your window(if possible) and then run this program again");
refresh();
getch();
endwin();
return 0;
}</span>
</pre>
</div>
<p>Above program demonstrates how easy it is to use
<tt class="LITERAL">printw</tt>. You just feed the
coordinates and the message to be appeared on the screen,
then it does what you want.</p>
<p>The above program introduces us to a new function
<tt class="LITERAL">getmaxyx()</tt>, a macro defined in
<tt class="LITERAL">ncurses.h</tt>. It gives the number
of columns and the number of rows in a given window.
<tt class="LITERAL">getmaxyx()</tt> does this by updating
the variables given to it. Since <tt class=
"LITERAL">getmaxyx()</tt> is not a function we don't pass
pointers to it, we just give two integer variables.</p>
</div>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="ADDSTRCLASS" id=
"ADDSTRCLASS">6.4. addstr() class of functions</a></h3>
<p><tt class="LITERAL">addstr()</tt> is used to put a
character string into a given window. This function is
similar to calling <tt class="LITERAL">addch()</tt> once
for each character in a given string. This is true for all
output functions. There are other functions from this
family such as <tt class=
"LITERAL">mvaddstr(),mvwaddstr()</tt> and <tt class=
"LITERAL">waddstr()</tt>, which obey the naming convention
of curses.(e.g. mvaddstr() is similar to the respective
calls move() and then addstr().) Another function of this
family is addnstr(), which takes an integer parameter(say
n) additionally. This function puts at most n characters
into the screen. If n is negative, then the entire string
will be added.</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="ACAUTION" id="ACAUTION">6.5. A
word of caution</a></h3>
<p>All these functions take y co-ordinate first and then x
in their arguments. A common mistake by beginners is to
pass x,y in that order. If you are doing too many
manipulations of (y,x) co-ordinates, think of dividing the
screen into windows and manipulate each one separately.
Windows are explained in the <a href="#WINDOWS">windows</a>
section.</p>
</div>
</div>
<div class="SECT1">
<hr>
<h2 class="SECT1"><a name="SCANW" id="SCANW">7. Input
functions</a></h2>
<p>Well, printing without taking input, is boring. Let's see
functions which allow us to get input from user. These
functions also can be divided into three categories.</p>
<ol type="1">
<li>
<p>getch() class: Get a character</p>
</li>
<li>
<p>scanw() class: Get formatted input</p>
</li>
<li>
<p>getstr() class: Get strings</p>
</li>
</ol>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="GETCHCLASS" id="GETCHCLASS">7.1.
getch() class of functions</a></h3>
<p>These functions read a single character from the
terminal. But there are several subtle facts to consider.
For example if you don't use the function cbreak(), curses
will not read your input characters contiguously but will
begin read them only after a new line or an EOF is
encountered. In order to avoid this, the cbreak() function
must used so that characters are immediately available to
your program. Another widely used function is noecho(). As
the name suggests, when this function is set (used), the
characters that are keyed in by the user will not show up
on the screen. The two functions cbreak() and noecho() are
typical examples of key management. Functions of this genre
are explained in the <a href="#KEYS">key management
section</a> .</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="SCANWCLASS" id="SCANWCLASS">7.2.
scanw() class of functions</a></h3>
<p>These functions are similar to <tt class=
"LITERAL">scanf()</tt> with the added capability of getting
the input from any location on the screen.</p>
<div class="SECT3">
<hr>
<h4 class="SECT3"><a name="SCANWMVSCANW" id=
"SCANWMVSCANW">7.2.1. scanw() and mvscanw</a></h4>
<p>The usage of these functions is similar to that of
<tt class="LITERAL">sscanf()</tt>, where the line to be
scanned is provided by <tt class="LITERAL">wgetstr()</tt>
function. That is, these functions call to <tt class=
"LITERAL">wgetstr()</tt> function(explained below) and
uses the resulting line for a scan.</p>
</div>
<div class="SECT3">
<hr>
<h4 class="SECT3"><a name="WSCANWMVWSCANW" id=
"WSCANWMVWSCANW">7.2.2. wscanw() and mvwscanw()</a></h4>
<p>These are similar to above two functions except that
they read from a window, which is supplied as one of the
arguments to these functions.</p>
</div>
<div class="SECT3">
<hr>
<h4 class="SECT3"><a name="VWSCANW" id="VWSCANW">7.2.3.
vw_scanw()</a></h4>
<p>This function is similar to <tt class=
"LITERAL">vscanf()</tt>. This can be used when a variable
number of arguments are to be scanned.</p>
</div>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="GETSTRCLASS" id=
"GETSTRCLASS">7.3. getstr() class of functions</a></h3>
<p>These functions are used to get strings from the
terminal. In essence, this function performs the same task
as would be achieved by a series of calls to <tt class=
"LITERAL">getch()</tt> until a newline, carriage return, or
end-of-file is received. The resulting string of characters
are pointed to by <tt class="LITERAL">str</tt>, which is a
character pointer provided by the user.</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="GETSTREX" id="GETSTREX">7.4.
Some examples</a></h3>
<div class="EXAMPLE">
<a name="BSCEX" id="BSCEX"></a>
<p><b>Example 4. A Simple scanw example</b></p>
<pre class="PROGRAMLISTING">
<span class=
"INLINEMEDIAOBJECT">#include <ncurses.h> /* ncurses.h includes stdio.h */
#include <string.h>
int main()
{
char mesg[]="Enter a string: "; /* message to be appeared on the screen */
char str[80];
int row,col; /* to store the number of rows and *
* the number of colums of the screen */
initscr(); /* start the curses mode */
getmaxyx(stdscr,row,col); /* get the number of rows and columns */
mvprintw(row/2,(col-strlen(mesg))/2,"%s",mesg);
/* print the message at the center of the screen */
getstr(str);
mvprintw(LINES - 2, 0, "You Entered: %s", str);
getch();
endwin();
return 0;
}</span>
</pre>
</div>
</div>
</div>
<div class="SECT1">
<hr>
<h2 class="SECT1"><a name="ATTRIB" id="ATTRIB">8.
Attributes</a></h2>
<p>We have seen an example of how attributes can be used to
print characters with some special effects. Attributes, when
set prudently, can present information in an easy,
understandable manner. The following program takes a C file
as input and prints the file with comments in bold. Scan
through the code.</p>
<div class="EXAMPLE">
<a name="BSIAT" id="BSIAT"></a>
<p><b>Example 5. A Simple Attributes example</b></p>
<pre class="PROGRAMLISTING">
<span class=
"INLINEMEDIAOBJECT">/* pager functionality by Joseph Spainhour" <spainhou@bellsouth.net> */
#include <ncurses.h>
#include <stdlib.h>
int main(int argc, char *argv[])
{
int ch, prev, row, col;
prev = EOF;
FILE *fp;
int y, x;
if(argc != 2)
{
printf("Usage: %s <a c file name>\n", argv[0]);
exit(1);
}
fp = fopen(argv[1], "r");
if(fp == NULL)
{
perror("Cannot open input file");
exit(1);
}
initscr(); /* Start curses mode */
getmaxyx(stdscr, row, col); /* find the boundaries of the screeen */
while((ch = fgetc(fp)) != EOF) /* read the file till we reach the end */
{
getyx(stdscr, y, x); /* get the current curser position */
if(y == (row - 1)) /* are we are at the end of the screen */
{
printw("<-Press Any Key->"); /* tell the user to press a key */
getch();
clear(); /* clear the screen */
move(0, 0); /* start at the beginning of the screen */
}
if(prev == '/' && ch == '*') /* If it is / and * then only
* switch bold on */
{
attron(A_BOLD); /* cut bold on */
getyx(stdscr, y, x); /* get the current curser position */
move(y, x - 1); /* back up one space */
printw("%c%c", '/', ch); /* The actual printing is done here */
}
else
printw("%c", ch);
refresh();
if(prev == '*' && ch == '/')
attroff(A_BOLD); /* Switch it off once we got *
* and then / */
prev = ch;
}
endwin(); /* End curses mode */
fclose(fp);
return 0;
}</span>
</pre>
</div>
<p>Don't worry about all those initialization and other crap.
Concentrate on the while loop. It reads each character in the
file and searches for the pattern /*. Once it spots the
pattern, it switches the BOLD attribute on with <tt class=
"LITERAL">attron()</tt> . When we get the pattern */ it is
switched off by <tt class="LITERAL">attroff()</tt> .</p>
<p>The above program also introduces us to two useful
functions <tt class="LITERAL">getyx()</tt> and <tt class=
"LITERAL">move()</tt>. The first function gets the
co-ordinates of the present cursor into the variables y, x.
Since getyx() is a macro we don't have to pass pointers to
variables. The function <tt class="LITERAL">move()</tt> moves
the cursor to the co-ordinates given to it.</p>
<p>The above program is really a simple one which doesn't do
much. On these lines one could write a more useful program
which reads a C file, parses it and prints it in different
colors. One could even extend it to other languages as
well.</p>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="ATTRIBDETAILS" id=
"ATTRIBDETAILS">8.1. The details</a></h3>
<p>Let's get into more details of attributes. The functions
<tt class="LITERAL">attron(), attroff(), attrset()</tt> ,
and their sister functions <tt class=
"LITERAL">attr_get()</tt> etc.. can be used to switch
attributes on/off , get attributes and produce a colorful
display.</p>
<p>The functions attron and attroff take a bit-mask of
attributes and switch them on or off, respectively. The
following video attributes, which are defined in
<curses.h> can be passed to these functions.</p>
<pre class="PROGRAMLISTING">
A_NORMAL Normal display (no highlight)
A_STANDOUT Best highlighting mode of the terminal.
A_UNDERLINE Underlining
A_REVERSE Reverse video
A_BLINK Blinking
A_DIM Half bright
A_BOLD Extra bright or bold
A_PROTECT Protected mode
A_INVIS Invisible or blank mode
A_ALTCHARSET Alternate character set
A_CHARTEXT Bit-mask to extract a character
COLOR_PAIR(n) Color-pair number n
</pre>
<p>The last one is the most colorful one :-) Colors are
explained in the <a href="#color" target="_top">next
sections</a>.</p>
<p>We can OR(|) any number of above attributes to get a
combined effect. If you wanted reverse video with blinking
characters you can use</p>
<pre class="PROGRAMLISTING">
attron(A_REVERSE | A_BLINK);
</pre>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="ATTRONVSATTRSET" id=
"ATTRONVSATTRSET">8.2. attron() vs attrset()</a></h3>
<p>Then what is the difference between attron() and
attrset()? attrset sets the attributes of window whereas
attron just switches on the attribute given to it. So
attrset() fully overrides whatever attributes the window
previously had and sets it to the new attribute(s).
Similarly attroff() just switches off the attribute(s)
given to it as an argument. This gives us the flexibility
of managing attributes easily.But if you use them
carelessly you may loose track of what attributes the
window has and garble the display. This is especially true
while managing menus with colors and highlighting. So
decide on a consistent policy and stick to it. You can
always use <tt class="LITERAL">standend()</tt> which is
equivalent to <tt class="LITERAL">attrset(A_NORMAL)</tt>
which turns off all attributes and brings you to normal
mode.</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="ATTRGET" id="ATTRGET">8.3.
attr_get()</a></h3>
<p>The function attr_get() gets the current attributes and
color pair of the window. Though we might not use this as
often as the above functions, this is useful in scanning
areas of screen. Say we wanted to do some complex update on
screen and we are not sure what attribute each character is
associated with. Then this function can be used with either
attrset or attron to produce the desired effect.</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="ATTRFUNCS" id="ATTRFUNCS">8.4.
attr_ functions</a></h3>
<p>There are series of functions like attr_set(), attr_on
etc.. These are similar to above functions except that they
take parameters of type <tt class=
"LITERAL">attr_t</tt>.</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="WATTRFUNCS" id="WATTRFUNCS">8.5.
wattr functions</a></h3>
<p>For each of the above functions we have a corresponding
function with 'w' which operates on a particular window.
The above functions operate on stdscr.</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="CHGAT" id="CHGAT">8.6. chgat()
functions</a></h3>
<p>The function chgat() is listed in the end of the man
page curs_attr. It actually is a useful one. This function
can be used to set attributes for a group of characters
without moving. I mean it !!! without moving the cursor :-)
It changes the attributes of a given number of characters
starting at the current cursor location.</p>
<p>We can give -1 as the character count to update till end
of line. If you want to change attributes of characters
from current position to end of line, just use this.</p>
<pre class="PROGRAMLISTING">
chgat(-1, A_REVERSE, 0, NULL);
</pre>
<p>This function is useful when changing attributes for
characters that are already on the screen. Move to the
character from which you want to change and change the
attribute.</p>
<p>Other functions wchgat(), mvchgat(), wchgat() behave
similarly except that the w functions operate on the
particular window. The mv functions first move the cursor
then perform the work given to them. Actually chgat is a
macro which is replaced by a wchgat() with stdscr as the
window. Most of the "w-less" functions are macros.</p>
<div class="EXAMPLE">
<a name="BWICH" id="BWICH"></a>
<p><b>Example 6. Chgat() Usage example</b></p>
<pre class="PROGRAMLISTING">
<span class="INLINEMEDIAOBJECT">#include <ncurses.h>
int main(int argc, char *argv[])
{ initscr(); /* Start curses mode */
start_color(); /* Start color functionality */
init_pair(1, COLOR_CYAN, COLOR_BLACK);
printw("A Big string which i didn't care to type fully ");
mvchgat(0, 0, -1, A_BLINK, 1, NULL);
/*
* First two parameters specify the position at which to start
* Third parameter number of characters to update. -1 means till
* end of line
* Forth parameter is the normal attribute you wanted to give
* to the charcter
* Fifth is the color index. It is the index given during init_pair()
* use 0 if you didn't want color
* Sixth one is always NULL
*/
refresh();
getch();
endwin(); /* End curses mode */
return 0;
}</span>
</pre>
</div>
<p>This example also introduces us to the color world of
curses. Colors will be explained in detail later. Use 0 for
no color.</p>
</div>
</div>
<div class="SECT1">
<hr>
<h2 class="SECT1"><a name="WINDOWS" id="WINDOWS">9.
Windows</a></h2>
<p>Windows form the most important concept in curses. You
have seen the standard window stdscr above where all the
functions implicitly operated on this window. Now to make
design even a simplest GUI, you need to resort to windows.
The main reason you may want to use windows is to manipulate
parts of the screen separately, for better efficiency, by
updating only the windows that need to be changed and for a
better design. I would say the last reason is the most
important in going for windows. You should always strive for
a better and easy-to-manage design in your programs. If you
are writing big, complex GUIs this is of pivotal importance
before you start doing anything.</p>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="WINDOWBASICS" id=
"WINDOWBASICS">9.1. The basics</a></h3>
<p>A Window can be created by calling the function
<tt class="LITERAL">newwin()</tt>. It doesn't create any
thing on the screen actually. It allocates memory for a
structure to manipulate the window and updates the
structure with data regarding the window like it's size,
beginy, beginx etc.. Hence in curses, a window is just an
abstraction of an imaginary window, which can be
manipulated independent of other parts of screen. The
function newwin() returns a pointer to structure WINDOW,
which can be passed to window related functions like
wprintw() etc.. Finally the window can be destroyed with
delwin(). It will deallocate the memory associated with the
window structure.</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="LETBEWINDOW" id=
"LETBEWINDOW">9.2. Let there be a Window !!!</a></h3>
<p>What fun is it, if a window is created and we can't see
it. So the fun part begins by displaying the window. The
function <tt class="LITERAL">box()</tt> can be used to draw
a border around the window. Let's explore these functions
in more detail in this example.</p>
<div class="EXAMPLE">
<a name="BWIBO" id="BWIBO"></a>
<p><b>Example 7. Window Border example</b></p>
<pre class="PROGRAMLISTING">
<span class="INLINEMEDIAOBJECT">#include <ncurses.h>
WINDOW *create_newwin(int height, int width, int starty, int startx);
void destroy_win(WINDOW *local_win);
int main(int argc, char *argv[])
{ WINDOW *my_win;
int startx, starty, width, height;
int ch;
initscr(); /* Start curses mode */
cbreak(); /* Line buffering disabled, Pass on
* everty thing to me */
keypad(stdscr, TRUE); /* I need that nifty F1 */
height = 3;
width = 10;
starty = (LINES - height) / 2; /* Calculating for a center placement */
startx = (COLS - width) / 2; /* of the window */
printw("Press F1 to exit");
refresh();
my_win = create_newwin(height, width, starty, startx);
while((ch = getch()) != KEY_F(1))
{ switch(ch)
{ case KEY_LEFT:
destroy_win(my_win);
my_win = create_newwin(height, width, starty,--startx);
break;
case KEY_RIGHT:
destroy_win(my_win);
my_win = create_newwin(height, width, starty,++startx);
break;
case KEY_UP:
destroy_win(my_win);
my_win = create_newwin(height, width, --starty,startx);
break;
case KEY_DOWN:
destroy_win(my_win);
my_win = create_newwin(height, width, ++starty,startx);
break;
}
}
endwin(); /* End curses mode */
return 0;
}
WINDOW *create_newwin(int height, int width, int starty, int startx)
{ WINDOW *local_win;
local_win = newwin(height, width, starty, startx);
box(local_win, 0 , 0); /* 0, 0 gives default characters
* for the vertical and horizontal
* lines */
wrefresh(local_win); /* Show that box */
return local_win;
}
void destroy_win(WINDOW *local_win)
{
/* box(local_win, ' ', ' '); : This won't produce the desired
* result of erasing the window. It will leave it's four corners
* and so an ugly remnant of window.
*/
wborder(local_win, ' ', ' ', ' ',' ',' ',' ',' ',' ');
/* The parameters taken are
* 1. win: the window on which to operate
* 2. ls: character to be used for the left side of the window
* 3. rs: character to be used for the right side of the window
* 4. ts: character to be used for the top side of the window
* 5. bs: character to be used for the bottom side of the window
* 6. tl: character to be used for the top left corner of the window
* 7. tr: character to be used for the top right corner of the window
* 8. bl: character to be used for the bottom left corner of the window
* 9. br: character to be used for the bottom right corner of the window
*/
wrefresh(local_win);
delwin(local_win);
}</span>
</pre>
</div>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="BORDEREXEXPL" id=
"BORDEREXEXPL">9.3. Explanation</a></h3>
<p>Don't scream. I know it's a big example. But I have to
explain some important things here :-). This program
creates a rectangular window that can be moved with left,
right, up, down arrow keys. It repeatedly creates and
destroys windows as user press a key. Don't go beyond the
screen limits. Checking for those limits is left as an
exercise for the reader. Let's dissect it by line by
line.</p>
<p>The <tt class="LITERAL">create_newwin()</tt> function
creates a window with <tt class="LITERAL">newwin()</tt> and
displays a border around it with box. The function
<tt class="LITERAL">destroy_win()</tt> first erases the
window from screen by painting a border with ' ' character
and then calling <tt class="LITERAL">delwin()</tt> to
deallocate memory related to it. Depending on the key the
user presses, starty or startx is changed and a new window
is created.</p>
<p>In the destroy_win, as you can see, I used wborder
instead of box. The reason is written in the comments (You
missed it. I know. Read the code :-)). wborder draws a
border around the window with the characters given to it as
the 4 corner points and the 4 lines. To put it clearly, if
you have called wborder as below:</p>
<pre class="PROGRAMLISTING">
wborder(win, '|', '|', '-', '-', '+', '+', '+', '+');
</pre>
<p>it produces some thing like</p>
<pre class="PROGRAMLISTING">
+------------+
| |
| |
| |
| |
| |
| |
+------------+
</pre>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="OTHERSTUFF" id="OTHERSTUFF">9.4.
The other stuff in the example</a></h3>
<p>You can also see in the above examples, that I have used
the variables COLS, LINES which are initialized to the
screen sizes after initscr(). They can be useful in finding
screen dimensions and finding the center co-ordinate of the
screen as above. The function <tt class=
"LITERAL">getch()</tt> as usual gets the key from keyboard
and according to the key it does the corresponding work.
This type of switch- case is very common in any GUI based
programs.</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="OTHERBORDERFUNCS" id=
"OTHERBORDERFUNCS">9.5. Other Border functions</a></h3>
<p>Above program is grossly inefficient in that with each
press of a key, a window is destroyed and another is
created. So let's write a more efficient program which uses
other border related functions.</p>
<p>The following program uses <tt class=
"LITERAL">mvhline()</tt> and <tt class=
"LITERAL">mvvline()</tt> to achieve similar effect. These
two functions are simple. They create a horizontal or
vertical line of the specified length at the specified
position.</p>
<div class="EXAMPLE">
<a name="BOTBO" id="BOTBO"></a>
<p><b>Example 8. More border functions</b></p>
<pre class="PROGRAMLISTING">
<span class="INLINEMEDIAOBJECT">#include <ncurses.h>
typedef struct _win_border_struct {
chtype ls, rs, ts, bs,
tl, tr, bl, br;
}WIN_BORDER;
typedef struct _WIN_struct {
int startx, starty;
int height, width;
WIN_BORDER border;
}WIN;
void init_win_params(WIN *p_win);
void print_win_params(WIN *p_win);
void create_box(WIN *win, bool flag);
int main(int argc, char *argv[])
{ WIN win;
int ch;
initscr(); /* Start curses mode */
start_color(); /* Start the color functionality */
cbreak(); /* Line buffering disabled, Pass on
* everty thing to me */
keypad(stdscr, TRUE); /* I need that nifty F1 */
noecho();
init_pair(1, COLOR_CYAN, COLOR_BLACK);
/* Initialize the window parameters */
init_win_params(&win);
print_win_params(&win);
attron(COLOR_PAIR(1));
printw("Press F1 to exit");
refresh();
attroff(COLOR_PAIR(1));
create_box(&win, TRUE);
while((ch = getch()) != KEY_F(1))
{ switch(ch)
{ case KEY_LEFT:
create_box(&win, FALSE);
--win.startx;
create_box(&win, TRUE);
break;
case KEY_RIGHT:
create_box(&win, FALSE);
++win.startx;
create_box(&win, TRUE);
break;
case KEY_UP:
create_box(&win, FALSE);
--win.starty;
create_box(&win, TRUE);
break;
case KEY_DOWN:
create_box(&win, FALSE);
++win.starty;
create_box(&win, TRUE);
break;
}
}
endwin(); /* End curses mode */
return 0;
}
void init_win_params(WIN *p_win)
{
p_win->height = 3;
p_win->width = 10;
p_win->starty = (LINES - p_win->height)/2;
p_win->startx = (COLS - p_win->width)/2;
p_win->border.ls = '|';
p_win->border.rs = '|';
p_win->border.ts = '-';
p_win->border.bs = '-';
p_win->border.tl = '+';
p_win->border.tr = '+';
p_win->border.bl = '+';
p_win->border.br = '+';
}
void print_win_params(WIN *p_win)
{
#ifdef _DEBUG
mvprintw(25, 0, "%d %d %d %d", p_win->startx, p_win->starty,
p_win->width, p_win->height);
refresh();
#endif
}
void create_box(WIN *p_win, bool flag)
{ int i, j;
int x, y, w, h;
x = p_win->startx;
y = p_win->starty;
w = p_win->width;
h = p_win->height;
if(flag == TRUE)
{ mvaddch(y, x, p_win->border.tl);
mvaddch(y, x + w, p_win->border.tr);
mvaddch(y + h, x, p_win->border.bl);
mvaddch(y + h, x + w, p_win->border.br);
mvhline(y, x + 1, p_win->border.ts, w - 1);
mvhline(y + h, x + 1, p_win->border.bs, w - 1);
mvvline(y + 1, x, p_win->border.ls, h - 1);
mvvline(y + 1, x + w, p_win->border.rs, h - 1);
}
else
for(j = y; j <= y + h; ++j)
for(i = x; i <= x + w; ++i)
mvaddch(j, i, ' ');
refresh();
}</span>
</pre>
</div>
</div>
</div>
<div class="SECT1">
<hr>
<h2 class="SECT1"><a name="COLOR" id="COLOR">10.
Colors</a></h2>
<div class="SECT2">
<h3 class="SECT2"><a name="COLORBASICS" id=
"COLORBASICS">10.1. The basics</a></h3>
<p>Life seems dull with no colors. Curses has a nice
mechanism to handle colors. Let's get into the thick of the
things with a small program.</p>
<div class="EXAMPLE">
<a name="BSICO" id="BSICO"></a>
<p><b>Example 9. A Simple Color example</b></p>
<pre class="PROGRAMLISTING">
<span class="INLINEMEDIAOBJECT">#include <ncurses.h>
void print_in_middle(WINDOW *win, int starty, int startx, int width, char *string);
int main(int argc, char *argv[])
{ initscr(); /* Start curses mode */
if(has_colors() == FALSE)
{ endwin();
printf("Your terminal does not support color\n");
exit(1);
}
start_color(); /* Start color */
init_pair(1, COLOR_RED, COLOR_BLACK);
attron(COLOR_PAIR(1));
print_in_middle(stdscr, LINES / 2, 0, 0, "Viola !!! In color ...");
attroff(COLOR_PAIR(1));
getch();
endwin();
}
void print_in_middle(WINDOW *win, int starty, int startx, int width, char *string)
{ int length, x, y;
float temp;
if(win == NULL)
win = stdscr;
getyx(win, y, x);
if(startx != 0)
x = startx;
if(starty != 0)
y = starty;
if(width == 0)
width = 80;
length = strlen(string);
temp = (width - length)/ 2;
x = startx + (int)temp;
mvwprintw(win, y, x, "%s", string);
refresh();
}
</span>
</pre>
</div>
<p>As you can see, to start using color, you should first
call the function <tt class="LITERAL">start_color()</tt>.
After that, you can use color capabilities of your
terminals using various functions. To find out whether a
terminal has color capabilities or not, you can use
<tt class="LITERAL">has_colors()</tt> function, which
returns FALSE if the terminal does not support color.</p>
<p>Curses initializes all the colors supported by terminal
when start_color() is called. These can be accessed by the
define constants like <tt class="LITERAL">COLOR_BLACK</tt>
etc. Now to actually start using colors, you have to define
pairs. Colors are always used in pairs. That means you have
to use the function <tt class="LITERAL">init_pair()</tt> to
define the foreground and background for the pair number
you give. After that that pair number can be used as a
normal attribute with <tt class=
"LITERAL">COLOR_PAIR()</tt>function. This may seem to be
cumbersome at first. But this elegant solution allows us to
manage color pairs very easily. To appreciate it, you have
to look into the the source code of "dialog", a utility for
displaying dialog boxes from shell scripts. The developers
have defined foreground and background combinations for all
the colors they might need and initialized at the
beginning. This makes it very easy to set attributes just
by accessing a pair which we already have defined as a
constant.</p>
<p>The following colors are defined in <tt class=
"LITERAL">curses.h</tt>. You can use these as parameters
for various color functions.</p>
<pre class="PROGRAMLISTING">
COLOR_BLACK 0
COLOR_RED 1
COLOR_GREEN 2
COLOR_YELLOW 3
COLOR_BLUE 4
COLOR_MAGENTA 5
COLOR_CYAN 6
COLOR_WHITE 7
</pre>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="CHANGECOLORDEFS" id=
"CHANGECOLORDEFS">10.2. Changing Color Definitions</a></h3>
<p>The function <tt class="LITERAL">init_color()</tt>can be
used to change the rgb values for the colors defined by
curses initially. Say you wanted to lighten the intensity
of red color by a minuscule. Then you can use this function
as</p>
<pre class="PROGRAMLISTING">
init_color(COLOR_RED, 700, 0, 0);
/* param 1 : color name
* param 2, 3, 4 : rgb content min = 0, max = 1000 */
</pre>
<p>If your terminal cannot change the color definitions,
the function returns ERR. The function <tt class=
"LITERAL">can_change_color()</tt> can be used to find out
whether the terminal has the capability of changing color
content or not. The rgb content is scaled from 0 to 1000.
Initially RED color is defined with content 1000(r), 0(g),
0(b).</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="COLORCONTENT" id=
"COLORCONTENT">10.3. Color Content</a></h3>
<p>The functions <tt class="LITERAL">color_content()</tt>
and <tt class="LITERAL">pair_content()</tt> can be used to
find the color content and foreground, background
combination for the pair.</p>
</div>
</div>
<div class="SECT1">
<hr>
<h2 class="SECT1"><a name="KEYS" id="KEYS">11. Interfacing
with the key board</a></h2>
<div class="SECT2">
<h3 class="SECT2"><a name="KEYSBASICS" id=
"KEYSBASICS">11.1. The Basics</a></h3>
<p>No GUI is complete without a strong user interface and
to interact with the user, a curses program should be
sensitive to key presses or the mouse actions done by the
user. Let's deal with the keys first.</p>
<p>As you have seen in almost all of the above examples,
it's very easy to get key input from the user. A simple way
of getting key presses is to use <tt class=
"LITERAL">getch()</tt> function. The cbreak mode should be
enabled to read keys when you are interested in reading
individual key hits rather than complete lines of text
(which usually end with a carriage return). keypad should
be enabled to get the Functions keys, arrow keys etc. See
the initialization section for details.</p>
<p><tt class="LITERAL">getch()</tt> returns an integer
corresponding to the key pressed. If it is a normal
character, the integer value will be equivalent to the
character. Otherwise it returns a number which can be
matched with the constants defined in <tt class=
"LITERAL">curses.h</tt>. For example if the user presses
F1, the integer returned is 265. This can be checked using
the macro KEY_F() defined in curses.h. This makes reading
keys portable and easy to manage.</p>
<p>For example, if you call getch() like this</p>
<pre class="PROGRAMLISTING">
int ch;
ch = getch();
</pre>
<p>getch() will wait for the user to press a key, (unless
you specified a timeout) and when user presses a key, the
corresponding integer is returned. Then you can check the
value returned with the constants defined in curses.h to
match against the keys you want.</p>
<p>The following code piece will do that job.</p>
<pre class="PROGRAMLISTING">
if(ch == KEY_LEFT)
printw("Left arrow is pressed\n");
</pre>
<p>Let's write a small program which creates a menu which
can be navigated by up and down arrows.</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="SIMPLEKEYEX" id=
"SIMPLEKEYEX">11.2. A Simple Key Usage example</a></h3>
<div class="EXAMPLE">
<a name="BSIKE" id="BSIKE"></a>
<p><b>Example 10. A Simple Key Usage example</b></p>
<pre class="PROGRAMLISTING">
<span class="INLINEMEDIAOBJECT">#include <stdio.h>
#include <ncurses.h>
#define WIDTH 30
#define HEIGHT 10
int startx = 0;
int starty = 0;
char *choices[] = {
"Choice 1",
"Choice 2",
"Choice 3",
"Choice 4",
"Exit",
};
int n_choices = sizeof(choices) / sizeof(char *);
void print_menu(WINDOW *menu_win, int highlight);
int main()
{ WINDOW *menu_win;
int highlight = 1;
int choice = 0;
int c;
initscr();
clear();
noecho();
cbreak(); /* Line buffering disabled. pass on everything */
startx = (80 - WIDTH) / 2;
starty = (24 - HEIGHT) / 2;
menu_win = newwin(HEIGHT, WIDTH, starty, startx);
keypad(menu_win, TRUE);
mvprintw(0, 0, "Use arrow keys to go up and down, Press enter to select a choice");
refresh();
print_menu(menu_win, highlight);
while(1)
{ c = wgetch(menu_win);
switch(c)
{ case KEY_UP:
if(highlight == 1)
highlight = n_choices;
else
--highlight;
break;
case KEY_DOWN:
if(highlight == n_choices)
highlight = 1;
else
++highlight;
break;
case 10:
choice = highlight;
break;
default:
mvprintw(24, 0, "Charcter pressed is = %3d Hopefully it can be printed as '%c'", c, c);
refresh();
break;
}
print_menu(menu_win, highlight);
if(choice != 0) /* User did a choice come out of the infinite loop */
break;
}
mvprintw(23, 0, "You chose choice %d with choice string %s\n", choice, choices[choice - 1]);
clrtoeol();
refresh();
endwin();
return 0;
}
void print_menu(WINDOW *menu_win, int highlight)
{
int x, y, i;
x = 2;
y = 2;
box(menu_win, 0, 0);
for(i = 0; i < n_choices; ++i)
{ if(highlight == i + 1) /* High light the present choice */
{ wattron(menu_win, A_REVERSE);
mvwprintw(menu_win, y, x, "%s", choices[i]);
wattroff(menu_win, A_REVERSE);
}
else
mvwprintw(menu_win, y, x, "%s", choices[i]);
++y;
}
wrefresh(menu_win);
}
</span>
</pre>
</div>
</div>
</div>
<div class="SECT1">
<hr>
<h2 class="SECT1"><a name="MOUSE" id="MOUSE">12. Interfacing
with the mouse</a></h2>
<p>Now that you have seen how to get keys, lets do the same
thing from mouse. Usually each UI allows the user to interact
with both keyboard and mouse.</p>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="MOUSEBASICS" id=
"MOUSEBASICS">12.1. The Basics</a></h3>
<p>Before you do any thing else, the events you want to
receive have to be enabled with <tt class=
"LITERAL">mousemask()</tt>.</p>
<pre class="PROGRAMLISTING">
mousemask( mmask_t newmask, /* The events you want to listen to */
mmask_t *oldmask) /* The old events mask */
</pre>
<p>The first parameter to above function is a bit mask of
events you would like to listen. By default, all the events
are turned off. The bit mask <tt class=
"LITERAL">ALL_MOUSE_EVENTS</tt> can be used to get all the
events.</p>
<p>The following are all the event masks:</p>
<pre class="PROGRAMLISTING">
Name Description
---------------------------------------------------------------------
BUTTON1_PRESSED mouse button 1 down
BUTTON1_RELEASED mouse button 1 up
BUTTON1_CLICKED mouse button 1 clicked
BUTTON1_DOUBLE_CLICKED mouse button 1 double clicked
BUTTON1_TRIPLE_CLICKED mouse button 1 triple clicked
BUTTON2_PRESSED mouse button 2 down
BUTTON2_RELEASED mouse button 2 up
BUTTON2_CLICKED mouse button 2 clicked
BUTTON2_DOUBLE_CLICKED mouse button 2 double clicked
BUTTON2_TRIPLE_CLICKED mouse button 2 triple clicked
BUTTON3_PRESSED mouse button 3 down
BUTTON3_RELEASED mouse button 3 up
BUTTON3_CLICKED mouse button 3 clicked
BUTTON3_DOUBLE_CLICKED mouse button 3 double clicked
BUTTON3_TRIPLE_CLICKED mouse button 3 triple clicked
BUTTON4_PRESSED mouse button 4 down
BUTTON4_RELEASED mouse button 4 up
BUTTON4_CLICKED mouse button 4 clicked
BUTTON4_DOUBLE_CLICKED mouse button 4 double clicked
BUTTON4_TRIPLE_CLICKED mouse button 4 triple clicked
BUTTON_SHIFT shift was down during button state change
BUTTON_CTRL control was down during button state change
BUTTON_ALT alt was down during button state change
ALL_MOUSE_EVENTS report all button state changes
REPORT_MOUSE_POSITION report mouse movement
</pre>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="GETTINGEVENTS" id=
"GETTINGEVENTS">12.2. Getting the events</a></h3>
<p>Once a class of mouse events have been enabled, getch()
class of functions return KEY_MOUSE every time some mouse
event happens. Then the mouse event can be retrieved with
<tt class="LITERAL">getmouse()</tt>.</p>
<p>The code approximately looks like this:</p>
<pre class="PROGRAMLISTING">
MEVENT event;
ch = getch();
if(ch == KEY_MOUSE)
if(getmouse(&event) == OK)
. /* Do some thing with the event */
.
.
</pre>
<p>getmouse() returns the event into the pointer given to
it. It's a structure which contains</p>
<pre class="PROGRAMLISTING">
typedef struct
{
short id; /* ID to distinguish multiple devices */
int x, y, z; /* event coordinates */
mmask_t bstate; /* button state bits */
}
</pre>
<p>The <tt class="LITERAL">bstate</tt> is the main variable
we are interested in. It tells the button state of the
mouse.</p>
<p>Then with a code snippet like the following, we can find
out what happened.</p>
<pre class="PROGRAMLISTING">
if(event.bstate & BUTTON1_PRESSED)
printw("Left Button Pressed");
</pre>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="MOUSETOGETHER" id=
"MOUSETOGETHER">12.3. Putting it all Together</a></h3>
<p>That's pretty much interfacing with mouse. Let's create
the same menu and enable mouse interaction. To make things
simpler, key handling is removed.</p>
<div class="EXAMPLE">
<a name="BMOME" id="BMOME"></a>
<p><b>Example 11. Access the menu with mouse !!!</b></p>
<pre class="PROGRAMLISTING">
<span class="INLINEMEDIAOBJECT">#include <ncurses.h>
#define WIDTH 30
#define HEIGHT 10
int startx = 0;
int starty = 0;
char *choices[] = { "Choice 1",
"Choice 2",
"Choice 3",
"Choice 4",
"Exit",
};
int n_choices = sizeof(choices) / sizeof(char *);
void print_menu(WINDOW *menu_win, int highlight);
void report_choice(int mouse_x, int mouse_y, int *p_choice);
int main()
{ int c, choice = 0;
WINDOW *menu_win;
MEVENT event;
/* Initialize curses */
initscr();
clear();
noecho();
cbreak(); //Line buffering disabled. pass on everything
/* Try to put the window in the middle of screen */
startx = (80 - WIDTH) / 2;
starty = (24 - HEIGHT) / 2;
attron(A_REVERSE);
mvprintw(23, 1, "Click on Exit to quit (Works best in a virtual console)");
refresh();
attroff(A_REVERSE);
/* Print the menu for the first time */
menu_win = newwin(HEIGHT, WIDTH, starty, startx);
print_menu(menu_win, 1);
/* Get all the mouse events */
mousemask(ALL_MOUSE_EVENTS, NULL);
while(1)
{ c = wgetch(menu_win);
switch(c)
{ case KEY_MOUSE:
if(getmouse(&event) == OK)
{ /* When the user clicks left mouse button */
if(event.bstate & BUTTON1_PRESSED)
{ report_choice(event.x + 1, event.y + 1, &choice);
if(choice == -1) //Exit chosen
goto end;
mvprintw(22, 1, "Choice made is : %d String Chosen is \"%10s\"", choice, choices[choice - 1]);
refresh();
}
}
print_menu(menu_win, choice);
break;
}
}
end:
endwin();
return 0;
}
void print_menu(WINDOW *menu_win, int highlight)
{
int x, y, i;
x = 2;
y = 2;
box(menu_win, 0, 0);
for(i = 0; i < n_choices; ++i)
{ if(highlight == i + 1)
{ wattron(menu_win, A_REVERSE);
mvwprintw(menu_win, y, x, "%s", choices[i]);
wattroff(menu_win, A_REVERSE);
}
else
mvwprintw(menu_win, y, x, "%s", choices[i]);
++y;
}
wrefresh(menu_win);
}
/* Report the choice according to mouse position */
void report_choice(int mouse_x, int mouse_y, int *p_choice)
{ int i,j, choice;
i = startx + 2;
j = starty + 3;
for(choice = 0; choice < n_choices; ++choice)
if(mouse_y == j + choice && mouse_x >= i && mouse_x <= i + strlen(choices[choice]))
{ if(choice == n_choices - 1)
*p_choice = -1;
else
*p_choice = choice + 1;
break;
}
}</span>
</pre>
</div>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="MISCMOUSEFUNCS" id=
"MISCMOUSEFUNCS">12.4. Miscellaneous Functions</a></h3>
<p>The functions mouse_trafo() and wmouse_trafo() can be
used to convert to mouse co-ordinates to screen relative
co-ordinates. See curs_mouse(3X) man page for details.</p>
<p>The mouseinterval function sets the maximum time (in
thousands of a second) that can elapse between press and
release events in order for them to be recognized as a
click. This function returns the previous interval value.
The default is one fifth of a second.</p>
</div>
</div>
<div class="SECT1">
<hr>
<h2 class="SECT1"><a name="SCREEN" id="SCREEN">13. Screen
Manipulation</a></h2>
<p>In this section, we will look into some functions, which
allow us to manage the screen efficiently and to write some
fancy programs. This is especially important in writing
games.</p>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="GETYX" id="GETYX">13.1. getyx()
functions</a></h3>
<p>The function <tt class="LITERAL">getyx()</tt> can be
used to find out the present cursor co-ordinates. It will
fill the values of x and y co-ordinates in the arguments
given to it. Since getyx() is a macro you don't have to
pass the address of the variables. It can be called as</p>
<pre class="PROGRAMLISTING">
getyx(win, y, x);
/* win: window pointer
* y, x: y, x co-ordinates will be put into this variables
*/
</pre>
<p>The function getparyx() gets the beginning co-ordinates
of the sub window relative to the main window. This is some
times useful to update a sub window. When designing fancy
stuff like writing multiple menus, it becomes difficult to
store the menu positions, their first option co-ordinates
etc. A simple solution to this problem, is to create menus
in sub windows and later find the starting co-ordinates of
the menus by using getparyx().</p>
<p>The functions getbegyx() and getmaxyx() store current
window's beginning and maximum co-ordinates. These
functions are useful in the same way as above in managing
the windows and sub windows effectively.</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="SCREENDUMP" id=
"SCREENDUMP">13.2. Screen Dumping</a></h3>
<p>While writing games, some times it becomes necessary to
store the state of the screen and restore it back to the
same state. The function scr_dump() can be used to dump the
screen contents to a file given as an argument. Later it
can be restored by scr_restore function. These two simple
functions can be used effectively to maintain a fast moving
game with changing scenarios.</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="WINDOWDUMP" id=
"WINDOWDUMP">13.3. Window Dumping</a></h3>
<p>To store and restore windows, the functions <tt class=
"LITERAL">putwin()</tt> and <tt class=
"LITERAL">getwin()</tt> can be used. <tt class=
"LITERAL">putwin()</tt> puts the present window state into
a file, which can be later restored by <tt class=
"LITERAL">getwin()</tt>.</p>
<p>The function <tt class="LITERAL">copywin()</tt> can be
used to copy a window completely onto another window. It
takes the source and destination windows as parameters and
according to the rectangle specified, it copies the
rectangular region from source to destination window. It's
last parameter specifies whether to overwrite or just
overlay the contents on to the destination window. If this
argument is true, then the copying is non-destructive.</p>
</div>
</div>
<div class="SECT1">
<hr>
<h2 class="SECT1"><a name="MISC" id="MISC">14. Miscellaneous
features</a></h2>
<p>Now you know enough features to write a good curses
program, with all bells and whistles. There are some
miscellaneous functions which are useful in various cases.
Let's go headlong into some of those.</p>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="CURSSET" id="CURSSET">14.1.
curs_set()</a></h3>
<p>This function can be used to make the cursor invisible.
The parameter to this function should be</p>
<pre class="PROGRAMLISTING">
0 : invisible or
1 : normal or
2 : very visible.
</pre>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="TEMPLEAVE" id="TEMPLEAVE">14.2.
Temporarily Leaving Curses mode</a></h3>
<p>Some times you may want to get back to cooked mode
(normal line buffering mode) temporarily. In such a case
you will first need to save the tty modes with a call to
<tt class="LITERAL">def_prog_mode()</tt> and then call
<tt class="LITERAL">endwin()</tt> to end the curses mode.
This will leave you in the original tty mode. To get back
to curses once you are done, call <tt class=
"LITERAL">reset_prog_mode()</tt> . This function returns
the tty to the state stored by <tt class=
"LITERAL">def_prog_mode()</tt>. Then do refresh(), and you
are back to the curses mode. Here is an example showing the
sequence of things to be done.</p>
<div class="EXAMPLE">
<a name="BTELE" id="BTELE"></a>
<p><b>Example 12. Temporarily Leaving Curses Mode</b></p>
<pre class="PROGRAMLISTING">
<span class="INLINEMEDIAOBJECT">#include <ncurses.h>
int main()
{
initscr(); /* Start curses mode */
printw("Hello World !!!\n"); /* Print Hello World */
refresh(); /* Print it on to the real screen */
def_prog_mode(); /* Save the tty modes */
endwin(); /* End curses mode temporarily */
system("/bin/sh"); /* Do whatever you like in cooked mode */
reset_prog_mode(); /* Return to the previous tty mode*/
/* stored by def_prog_mode() */
refresh(); /* Do refresh() to restore the */
/* Screen contents */
printw("Another String\n"); /* Back to curses use the full */
refresh(); /* capabilities of curses */
endwin(); /* End curses mode */
return 0;
}</span>
</pre>
</div>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="ACSVARS" id="ACSVARS">14.3. ACS_
variables</a></h3>
<p>If you have ever programmed in DOS, you know about those
nifty characters in extended character set. They are
printable only on some terminals. NCURSES functions like
<tt class="LITERAL">box()</tt> use these characters. All
these variables start with ACS meaning alternative
character set. You might have noticed me using these
characters in some of the programs above. Here's an example
showing all the characters.</p>
<div class="EXAMPLE">
<a name="BACSVARS" id="BACSVARS"></a>
<p><b>Example 13. ACS Variables Example</b></p>
<pre class="PROGRAMLISTING">
<span class="INLINEMEDIAOBJECT">#include <ncurses.h>
int main()
{
initscr();
printw("Upper left corner "); addch(ACS_ULCORNER); printw("\n");
printw("Lower left corner "); addch(ACS_LLCORNER); printw("\n");
printw("Lower right corner "); addch(ACS_LRCORNER); printw("\n");
printw("Tee pointing right "); addch(ACS_LTEE); printw("\n");
printw("Tee pointing left "); addch(ACS_RTEE); printw("\n");
printw("Tee pointing up "); addch(ACS_BTEE); printw("\n");
printw("Tee pointing down "); addch(ACS_TTEE); printw("\n");
printw("Horizontal line "); addch(ACS_HLINE); printw("\n");
printw("Vertical line "); addch(ACS_VLINE); printw("\n");
printw("Large Plus or cross over "); addch(ACS_PLUS); printw("\n");
printw("Scan Line 1 "); addch(ACS_S1); printw("\n");
printw("Scan Line 3 "); addch(ACS_S3); printw("\n");
printw("Scan Line 7 "); addch(ACS_S7); printw("\n");
printw("Scan Line 9 "); addch(ACS_S9); printw("\n");
printw("Diamond "); addch(ACS_DIAMOND); printw("\n");
printw("Checker board (stipple) "); addch(ACS_CKBOARD); printw("\n");
printw("Degree Symbol "); addch(ACS_DEGREE); printw("\n");
printw("Plus/Minus Symbol "); addch(ACS_PLMINUS); printw("\n");
printw("Bullet "); addch(ACS_BULLET); printw("\n");
printw("Arrow Pointing Left "); addch(ACS_LARROW); printw("\n");
printw("Arrow Pointing Right "); addch(ACS_RARROW); printw("\n");
printw("Arrow Pointing Down "); addch(ACS_DARROW); printw("\n");
printw("Arrow Pointing Up "); addch(ACS_UARROW); printw("\n");
printw("Board of squares "); addch(ACS_BOARD); printw("\n");
printw("Lantern Symbol "); addch(ACS_LANTERN); printw("\n");
printw("Solid Square Block "); addch(ACS_BLOCK); printw("\n");
printw("Less/Equal sign "); addch(ACS_LEQUAL); printw("\n");
printw("Greater/Equal sign "); addch(ACS_GEQUAL); printw("\n");
printw("Pi "); addch(ACS_PI); printw("\n");
printw("Not equal "); addch(ACS_NEQUAL); printw("\n");
printw("UK pound sign "); addch(ACS_STERLING); printw("\n");
refresh();
getch();
endwin();
return 0;
}</span>
</pre>
</div>
</div>
</div>
<div class="SECT1">
<hr>
<h2 class="SECT1"><a name="OTHERLIB" id="OTHERLIB">15. Other
libraries</a></h2>
<p>Apart from the curses library, there are few text mode
libraries, which provide more functionality and a lot of
features. The following sections explain three standard
libraries which are usually distributed along with
curses.</p>
</div>
<div class="SECT1">
<hr>
<h2 class="SECT1"><a name="PANELS" id="PANELS">16. Panel
Library</a></h2>
<p>Now that you are proficient in curses, you wanted to do
some thing big. You created a lot of overlapping windows to
give a professional windows-type look. Unfortunately, it soon
becomes difficult to manage these. The multiple refreshes,
updates plunge you into a nightmare. The overlapping windows
create blotches, whenever you forget to refresh the windows
in the proper order.</p>
<p>Don't despair. There's an elegant solution provided in
panels library. In the words of developers of ncurses</p>
<p><span class="emphasis"><i class="EMPHASIS">When your
interface design is such that windows may dive deeper into
the visibility stack or pop to the top at runtime, the
resulting book-keeping can be tedious and difficult to get
right. Hence the panels library.</i></span></p>
<p>If you have lot of overlapping windows, then panels
library is the way to go. It obviates the need of doing
series of wnoutrefresh(), doupdate() and relieves the burden
of doing it correctly(bottom up). The library maintains
information about the order of windows, their overlapping and
update the screen properly. So why wait? Let's take a close
peek into panels.</p>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="PANELBASICS" id=
"PANELBASICS">16.1. The Basics</a></h3>
<p>Panel object is a window that is implicitly treated as
part of a deck including all other panel objects. The deck
is treated as a stack with the top panel being completely
visible and the other panels may or may not be obscured
according to their positions. So the basic idea is to
create a stack of overlapping panels and use panels library
to display them correctly. There is a function similar to
refresh() which, when called , displays panels in the
correct order. Functions are provided to hide or show
panels, move panels, change its size etc.. The overlapping
problem is managed by the panels library during all the
calls to these functions.</p>
<p>The general flow of a panel program goes like this:</p>
<ol type="1">
<li>
<p>Create the windows (with newwin()) to be attached to
the panels.</p>
</li>
<li>
<p>Create panels with the chosen visibility order.
Stack them up according to the desired visibility. The
function new_panel() is used to created panels.</p>
</li>
<li>
<p>Call update_panels() to write the panels to the
virtual screen in correct visibility order. Do a
doupdate() to show it on the screen.</p>
</li>
<li>
<p>Mainpulate the panels with show_panel(),
hide_panel(), move_panel() etc. Make use of helper
functions like panel_hidden() and panel_window(). Make
use of user pointer to store custom data for a panel.
Use the functions set_panel_userptr() and
panel_userptr() to set and get the user pointer for a
panel.</p>
</li>
<li>
<p>When you are done with the panel use del_panel() to
delete the panel.</p>
</li>
</ol>
<p>Let's make the concepts clear, with some programs. The
following is a simple program which creates 3 overlapping
panels and shows them on the screen.</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="COMPILEPANELS" id=
"COMPILEPANELS">16.2. Compiling With the Panels
Library</a></h3>
<p>To use panels library functions, you have to include
panel.h and to link the program with panels library the
flag -lpanel should be added along with -lncurses in that
order.</p>
<pre class="PROGRAMLISTING">
#include <panel.h>
.
.
.
compile and link: gcc <program file> -lpanel -lncurses
</pre>
<div class="EXAMPLE">
<a name="PPASI" id="PPASI"></a>
<p><b>Example 14. Panel basics</b></p>
<pre class="PROGRAMLISTING">
<span class="INLINEMEDIAOBJECT">#include <panel.h>
int main()
{ WINDOW *my_wins[3];
PANEL *my_panels[3];
int lines = 10, cols = 40, y = 2, x = 4, i;
initscr();
cbreak();
noecho();
/* Create windows for the panels */
my_wins[0] = newwin(lines, cols, y, x);
my_wins[1] = newwin(lines, cols, y + 1, x + 5);
my_wins[2] = newwin(lines, cols, y + 2, x + 10);
/*
* Create borders around the windows so that you can see the effect
* of panels
*/
for(i = 0; i < 3; ++i)
box(my_wins[i], 0, 0);
/* Attach a panel to each window */ /* Order is bottom up */
my_panels[0] = new_panel(my_wins[0]); /* Push 0, order: stdscr-0 */
my_panels[1] = new_panel(my_wins[1]); /* Push 1, order: stdscr-0-1 */
my_panels[2] = new_panel(my_wins[2]); /* Push 2, order: stdscr-0-1-2 */
/* Update the stacking order. 2nd panel will be on top */
update_panels();
/* Show it on the screen */
doupdate();
getch();
endwin();
}
</span>
</pre>
</div>
<p>As you can see, above program follows a simple flow as
explained. The windows are created with newwin() and then
they are attached to panels with new_panel(). As we attach
one panel after another, the stack of panels gets updated.
To put them on screen update_panels() and doupdate() are
called.</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="PANELBROWSING" id=
"PANELBROWSING">16.3. Panel Window Browsing</a></h3>
<p>A slightly complicated example is given below. This
program creates 3 windows which can be cycled through using
tab. Have a look at the code.</p>
<div class="EXAMPLE">
<a name="PPABR" id="PPABR"></a>
<p><b>Example 15. Panel Window Browsing Example</b></p>
<pre class="PROGRAMLISTING">
<span class="INLINEMEDIAOBJECT">#include <panel.h>
#define NLINES 10
#define NCOLS 40
void init_wins(WINDOW **wins, int n);
void win_show(WINDOW *win, char *label, int label_color);
void print_in_middle(WINDOW *win, int starty, int startx, int width, char *string, chtype color);
int main()
{ WINDOW *my_wins[3];
PANEL *my_panels[3];
PANEL *top;
int ch;
/* Initialize curses */
initscr();
start_color();
cbreak();
noecho();
keypad(stdscr, TRUE);
/* Initialize all the colors */
init_pair(1, COLOR_RED, COLOR_BLACK);
init_pair(2, COLOR_GREEN, COLOR_BLACK);
init_pair(3, COLOR_BLUE, COLOR_BLACK);
init_pair(4, COLOR_CYAN, COLOR_BLACK);
init_wins(my_wins, 3);
/* Attach a panel to each window */ /* Order is bottom up */
my_panels[0] = new_panel(my_wins[0]); /* Push 0, order: stdscr-0 */
my_panels[1] = new_panel(my_wins[1]); /* Push 1, order: stdscr-0-1 */
my_panels[2] = new_panel(my_wins[2]); /* Push 2, order: stdscr-0-1-2 */
/* Set up the user pointers to the next panel */
set_panel_userptr(my_panels[0], my_panels[1]);
set_panel_userptr(my_panels[1], my_panels[2]);
set_panel_userptr(my_panels[2], my_panels[0]);
/* Update the stacking order. 2nd panel will be on top */
update_panels();
/* Show it on the screen */
attron(COLOR_PAIR(4));
mvprintw(LINES - 2, 0, "Use tab to browse through the windows (F1 to Exit)");
attroff(COLOR_PAIR(4));
doupdate();
top = my_panels[2];
while((ch = getch()) != KEY_F(1))
{ switch(ch)
{ case 9:
top = (PANEL *)panel_userptr(top);
top_panel(top);
break;
}
update_panels();
doupdate();
}
endwin();
return 0;
}
/* Put all the windows */
void init_wins(WINDOW **wins, int n)
{ int x, y, i;
char label[80];
y = 2;
x = 10;
for(i = 0; i < n; ++i)
{ wins[i] = newwin(NLINES, NCOLS, y, x);
sprintf(label, "Window Number %d", i + 1);
win_show(wins[i], label, i + 1);
y += 3;
x += 7;
}
}
/* Show the window with a border and a label */
void win_show(WINDOW *win, char *label, int label_color)
{ int startx, starty, height, width;
getbegyx(win, starty, startx);
getmaxyx(win, height, width);
box(win, 0, 0);
mvwaddch(win, 2, 0, ACS_LTEE);
mvwhline(win, 2, 1, ACS_HLINE, width - 2);
mvwaddch(win, 2, width - 1, ACS_RTEE);
print_in_middle(win, 1, 0, width, label, COLOR_PAIR(label_color));
}
void print_in_middle(WINDOW *win, int starty, int startx, int width, char *string, chtype color)
{ int length, x, y;
float temp;
if(win == NULL)
win = stdscr;
getyx(win, y, x);
if(startx != 0)
x = startx;
if(starty != 0)
y = starty;
if(width == 0)
width = 80;
length = strlen(string);
temp = (width - length)/ 2;
x = startx + (int)temp;
wattron(win, color);
mvwprintw(win, y, x, "%s", string);
wattroff(win, color);
refresh();
}</span>
</pre>
</div>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="USERPTRUSING" id=
"USERPTRUSING">16.4. Using User Pointers</a></h3>
<p>In the above example I used user pointers to find out
the next window in the cycle. We can attach custom
information to the panel by specifying a user pointer,
which can point to any information you want to store. In
this case I stored the pointer to the next panel in the
cycle. User pointer for a panel can be set with the
function <tt class="LITERAL">set_panel_userptr()</tt>. It
can be accessed using the function <tt class=
"LITERAL">panel_userptr()</tt> which will return the user
pointer for the panel given as argument. After finding the
next panel in the cycle It's brought to the top by the
function top_panel(). This function brings the panel given
as argument to the top of the panel stack.</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="PANELMOVERESIZE" id=
"PANELMOVERESIZE">16.5. Moving and Resizing Panels</a></h3>
<p>The function <tt class="LITERAL">move_panel()</tt> can
be used to move a panel to the desired location. It does
not change the position of the panel in the stack. Make
sure that you use move_panel() instead mvwin() on the
window associated with the panel.</p>
<p>Resizing a panel is slightly complex. There is no
straight forward function just to resize the window
associated with a panel. A solution to resize a panel is to
create a new window with the desired sizes, change the
window associated with the panel using replace_panel().
Don't forget to delete the old window. The window
associated with a panel can be found by using the function
panel_window().</p>
<p>The following program shows these concepts, in
supposedly simple program. You can cycle through the window
with <TAB> as usual. To resize or move the active
panel press 'r' for resize 'm' for moving. Then use arrow
keys to resize or move it to the desired way and press
enter to end your resizing or moving. This example makes
use of user data to get the required data to do the
operations.</p>
<div class="EXAMPLE">
<a name="PPARE" id="PPARE"></a>
<p><b>Example 16. Panel Moving and Resizing
example</b></p>
<pre class="PROGRAMLISTING">
<span class="INLINEMEDIAOBJECT">#include <panel.h>
typedef struct _PANEL_DATA {
int x, y, w, h;
char label[80];
int label_color;
PANEL *next;
}PANEL_DATA;
#define NLINES 10
#define NCOLS 40
void init_wins(WINDOW **wins, int n);
void win_show(WINDOW *win, char *label, int label_color);
void print_in_middle(WINDOW *win, int starty, int startx, int width, char *string, chtype color);
void set_user_ptrs(PANEL **panels, int n);
int main()
{ WINDOW *my_wins[3];
PANEL *my_panels[3];
PANEL_DATA *top;
PANEL *stack_top;
WINDOW *temp_win, *old_win;
int ch;
int newx, newy, neww, newh;
int size = FALSE, move = FALSE;
/* Initialize curses */
initscr();
start_color();
cbreak();
noecho();
keypad(stdscr, TRUE);
/* Initialize all the colors */
init_pair(1, COLOR_RED, COLOR_BLACK);
init_pair(2, COLOR_GREEN, COLOR_BLACK);
init_pair(3, COLOR_BLUE, COLOR_BLACK);
init_pair(4, COLOR_CYAN, COLOR_BLACK);
init_wins(my_wins, 3);
/* Attach a panel to each window */ /* Order is bottom up */
my_panels[0] = new_panel(my_wins[0]); /* Push 0, order: stdscr-0 */
my_panels[1] = new_panel(my_wins[1]); /* Push 1, order: stdscr-0-1 */
my_panels[2] = new_panel(my_wins[2]); /* Push 2, order: stdscr-0-1-2 */
set_user_ptrs(my_panels, 3);
/* Update the stacking order. 2nd panel will be on top */
update_panels();
/* Show it on the screen */
attron(COLOR_PAIR(4));
mvprintw(LINES - 3, 0, "Use 'm' for moving, 'r' for resizing");
mvprintw(LINES - 2, 0, "Use tab to browse through the windows (F1 to Exit)");
attroff(COLOR_PAIR(4));
doupdate();
stack_top = my_panels[2];
top = (PANEL_DATA *)panel_userptr(stack_top);
newx = top->x;
newy = top->y;
neww = top->w;
newh = top->h;
while((ch = getch()) != KEY_F(1))
{ switch(ch)
{ case 9: /* Tab */
top = (PANEL_DATA *)panel_userptr(stack_top);
top_panel(top->next);
stack_top = top->next;
top = (PANEL_DATA *)panel_userptr(stack_top);
newx = top->x;
newy = top->y;
neww = top->w;
newh = top->h;
break;
case 'r': /* Re-Size*/
size = TRUE;
attron(COLOR_PAIR(4));
mvprintw(LINES - 4, 0, "Entered Resizing :Use Arrow Keys to resize and press <ENTER> to end resizing");
refresh();
attroff(COLOR_PAIR(4));
break;
case 'm': /* Move */
attron(COLOR_PAIR(4));
mvprintw(LINES - 4, 0, "Entered Moving: Use Arrow Keys to Move and press <ENTER> to end moving");
refresh();
attroff(COLOR_PAIR(4));
move = TRUE;
break;
case KEY_LEFT:
if(size == TRUE)
{ --newx;
++neww;
}
if(move == TRUE)
--newx;
break;
case KEY_RIGHT:
if(size == TRUE)
{ ++newx;
--neww;
}
if(move == TRUE)
++newx;
break;
case KEY_UP:
if(size == TRUE)
{ --newy;
++newh;
}
if(move == TRUE)
--newy;
break;
case KEY_DOWN:
if(size == TRUE)
{ ++newy;
--newh;
}
if(move == TRUE)
++newy;
break;
case 10: /* Enter */
move(LINES - 4, 0);
clrtoeol();
refresh();
if(size == TRUE)
{ old_win = panel_window(stack_top);
temp_win = newwin(newh, neww, newy, newx);
replace_panel(stack_top, temp_win);
win_show(temp_win, top->label, top->label_color);
delwin(old_win);
size = FALSE;
}
if(move == TRUE)
{ move_panel(stack_top, newy, newx);
move = FALSE;
}
break;
}
attron(COLOR_PAIR(4));
mvprintw(LINES - 3, 0, "Use 'm' for moving, 'r' for resizing");
mvprintw(LINES - 2, 0, "Use tab to browse through the windows (F1 to Exit)");
attroff(COLOR_PAIR(4));
refresh();
update_panels();
doupdate();
}
endwin();
return 0;
}
/* Put all the windows */
void init_wins(WINDOW **wins, int n)
{ int x, y, i;
char label[80];
y = 2;
x = 10;
for(i = 0; i < n; ++i)
{ wins[i] = newwin(NLINES, NCOLS, y, x);
sprintf(label, "Window Number %d", i + 1);
win_show(wins[i], label, i + 1);
y += 3;
x += 7;
}
}
/* Set the PANEL_DATA structures for individual panels */
void set_user_ptrs(PANEL **panels, int n)
{ PANEL_DATA *ptrs;
WINDOW *win;
int x, y, w, h, i;
char temp[80];
ptrs = (PANEL_DATA *)calloc(n, sizeof(PANEL_DATA));
for(i = 0;i < n; ++i)
{ win = panel_window(panels[i]);
getbegyx(win, y, x);
getmaxyx(win, h, w);
ptrs[i].x = x;
ptrs[i].y = y;
ptrs[i].w = w;
ptrs[i].h = h;
sprintf(temp, "Window Number %d", i + 1);
strcpy(ptrs[i].label, temp);
ptrs[i].label_color = i + 1;
if(i + 1 == n)
ptrs[i].next = panels[0];
else
ptrs[i].next = panels[i + 1];
set_panel_userptr(panels[i], &ptrs[i]);
}
}
/* Show the window with a border and a label */
void win_show(WINDOW *win, char *label, int label_color)
{ int startx, starty, height, width;
getbegyx(win, starty, startx);
getmaxyx(win, height, width);
box(win, 0, 0);
mvwaddch(win, 2, 0, ACS_LTEE);
mvwhline(win, 2, 1, ACS_HLINE, width - 2);
mvwaddch(win, 2, width - 1, ACS_RTEE);
print_in_middle(win, 1, 0, width, label, COLOR_PAIR(label_color));
}
void print_in_middle(WINDOW *win, int starty, int startx, int width, char *string, chtype color)
{ int length, x, y;
float temp;
if(win == NULL)
win = stdscr;
getyx(win, y, x);
if(startx != 0)
x = startx;
if(starty != 0)
y = starty;
if(width == 0)
width = 80;
length = strlen(string);
temp = (width - length)/ 2;
x = startx + (int)temp;
wattron(win, color);
mvwprintw(win, y, x, "%s", string);
wattroff(win, color);
refresh();
}</span>
</pre>
</div>
<p>Concentrate on the main while loop. Once it finds out
the type of key pressed, it takes appropriate action. If
'r' is pressed resizing mode is started. After this the new
sizes are updated as the user presses the arrow keys. When
the user presses <ENTER> present selection ends and
panel is resized by using the concept explained. While in
resizing mode the program doesn't show how the window is
getting resized. It's left as an exercise to the reader to
print a dotted border while it gets resized to a new
position.</p>
<p>When the user presses 'm' the move mode starts. This is
a bit simpler than resizing. As the arrow keys are pressed
the new position is updated and pressing of <ENTER>
causes the panel to be moved by calling the function
move_panel().</p>
<p>In this program the user data which is represented as
PANEL_DATA, plays very important role in finding the
associated information with a panel. As written in the
comments, the PANEL_DATA stores the panel sizes, label,
label color and a pointer to the next panel in the
cycle.</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="PANELSHOWHIDE" id=
"PANELSHOWHIDE">16.6. Hiding and Showing Panels</a></h3>
<p>A Panel can be hidden by using the function
hide_panel(). This function merely removes it form the
stack of panels, thus hiding it on the screen once you do
update_panels() and doupdate(). It doesn't destroy the
PANEL structure associated with the hidden panel. It can be
shown again by using the show_panel() function.</p>
<p>The following program shows the hiding of panels. Press
'a' or 'b' or 'c' to show or hide first, second and third
windows respectively. It uses a user data with a small
variable hide, which keeps track of whether the window is
hidden or not. For some reason the function <tt class=
"LITERAL">panel_hidden()</tt> which tells whether a panel
is hidden or not is not working. A bug report was also
presented by Michael Andres <a href=
"http://www.geocrawler.com/archives/3/344/1999/9/0/2643549/"
target="_top">here</a></p>
<div class="EXAMPLE">
<a name="PPAHI" id="PPAHI"></a>
<p><b>Example 17. Panel Hiding and Showing
example</b></p>
<pre class="PROGRAMLISTING">
<span class="INLINEMEDIAOBJECT">#include <panel.h>
typedef struct _PANEL_DATA {
int hide; /* TRUE if panel is hidden */
}PANEL_DATA;
#define NLINES 10
#define NCOLS 40
void init_wins(WINDOW **wins, int n);
void win_show(WINDOW *win, char *label, int label_color);
void print_in_middle(WINDOW *win, int starty, int startx, int width, char *string, chtype color);
int main()
{ WINDOW *my_wins[3];
PANEL *my_panels[3];
PANEL_DATA panel_datas[3];
PANEL_DATA *temp;
int ch;
/* Initialize curses */
initscr();
start_color();
cbreak();
noecho();
keypad(stdscr, TRUE);
/* Initialize all the colors */
init_pair(1, COLOR_RED, COLOR_BLACK);
init_pair(2, COLOR_GREEN, COLOR_BLACK);
init_pair(3, COLOR_BLUE, COLOR_BLACK);
init_pair(4, COLOR_CYAN, COLOR_BLACK);
init_wins(my_wins, 3);
/* Attach a panel to each window */ /* Order is bottom up */
my_panels[0] = new_panel(my_wins[0]); /* Push 0, order: stdscr-0 */
my_panels[1] = new_panel(my_wins[1]); /* Push 1, order: stdscr-0-1 */
my_panels[2] = new_panel(my_wins[2]); /* Push 2, order: stdscr-0-1-2 */
/* Initialize panel datas saying that nothing is hidden */
panel_datas[0].hide = FALSE;
panel_datas[1].hide = FALSE;
panel_datas[2].hide = FALSE;
set_panel_userptr(my_panels[0], &panel_datas[0]);
set_panel_userptr(my_panels[1], &panel_datas[1]);
set_panel_userptr(my_panels[2], &panel_datas[2]);
/* Update the stacking order. 2nd panel will be on top */
update_panels();
/* Show it on the screen */
attron(COLOR_PAIR(4));
mvprintw(LINES - 3, 0, "Show or Hide a window with 'a'(first window) 'b'(Second Window) 'c'(Third Window)");
mvprintw(LINES - 2, 0, "F1 to Exit");
attroff(COLOR_PAIR(4));
doupdate();
while((ch = getch()) != KEY_F(1))
{ switch(ch)
{ case 'a':
temp = (PANEL_DATA *)panel_userptr(my_panels[0]);
if(temp->hide == FALSE)
{ hide_panel(my_panels[0]);
temp->hide = TRUE;
}
else
{ show_panel(my_panels[0]);
temp->hide = FALSE;
}
break;
case 'b':
temp = (PANEL_DATA *)panel_userptr(my_panels[1]);
if(temp->hide == FALSE)
{ hide_panel(my_panels[1]);
temp->hide = TRUE;
}
else
{ show_panel(my_panels[1]);
temp->hide = FALSE;
}
break;
case 'c':
temp = (PANEL_DATA *)panel_userptr(my_panels[2]);
if(temp->hide == FALSE)
{ hide_panel(my_panels[2]);
temp->hide = TRUE;
}
else
{ show_panel(my_panels[2]);
temp->hide = FALSE;
}
break;
}
update_panels();
doupdate();
}
endwin();
return 0;
}
/* Put all the windows */
void init_wins(WINDOW **wins, int n)
{ int x, y, i;
char label[80];
y = 2;
x = 10;
for(i = 0; i < n; ++i)
{ wins[i] = newwin(NLINES, NCOLS, y, x);
sprintf(label, "Window Number %d", i + 1);
win_show(wins[i], label, i + 1);
y += 3;
x += 7;
}
}
/* Show the window with a border and a label */
void win_show(WINDOW *win, char *label, int label_color)
{ int startx, starty, height, width;
getbegyx(win, starty, startx);
getmaxyx(win, height, width);
box(win, 0, 0);
mvwaddch(win, 2, 0, ACS_LTEE);
mvwhline(win, 2, 1, ACS_HLINE, width - 2);
mvwaddch(win, 2, width - 1, ACS_RTEE);
print_in_middle(win, 1, 0, width, label, COLOR_PAIR(label_color));
}
void print_in_middle(WINDOW *win, int starty, int startx, int width, char *string, chtype color)
{ int length, x, y;
float temp;
if(win == NULL)
win = stdscr;
getyx(win, y, x);
if(startx != 0)
x = startx;
if(starty != 0)
y = starty;
if(width == 0)
width = 80;
length = strlen(string);
temp = (width - length)/ 2;
x = startx + (int)temp;
wattron(win, color);
mvwprintw(win, y, x, "%s", string);
wattroff(win, color);
refresh();
}</span>
</pre>
</div>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="PANELABOVE" id=
"PANELABOVE">16.7. panel_above() and panel_below()
Functions</a></h3>
<p>The functions <tt class="LITERAL">panel_above()</tt> and
<tt class="LITERAL">panel_below()</tt> can be used to find
out the panel above and below a panel. If the argument to
these functions is NULL, then they return a pointer to
bottom panel and top panel respectively.</p>
</div>
</div>
<div class="SECT1">
<hr>
<h2 class="SECT1"><a name="MENUS" id="MENUS">17. Menus
Library</a></h2>
<p>The menus library provides a nice extension to basic
curses, through which you can create menus. It provides a set
of functions to create menus. But they have to be customized
to give a nicer look, with colors etc. Let's get into the
details.</p>
<p>A menu is a screen display that assists the user to choose
some subset of a given set of items. To put it simple, a menu
is a collection of items from which one or more items can be
chosen. Some readers might not be aware of multiple item
selection capability. Menu library provides functionality to
write menus from which the user can chose more than one item
as the preferred choice. This is dealt with in a later
section. Now it is time for some rudiments.</p>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="MENUBASICS" id=
"MENUBASICS">17.1. The Basics</a></h3>
<p>To create menus, you first create items, and then post
the menu to the display. After that, all the processing of
user responses is done in an elegant function menu_driver()
which is the work horse of any menu program.</p>
<p>The general flow of control of a menu program looks like
this.</p>
<ol type="1">
<li>
<p>Initialize curses</p>
</li>
<li>
<p>Create items using new_item(). You can specify a
name and description for the items.</p>
</li>
<li>
<p>Create the menu with new_menu() by specifying the
items to be attached with.</p>
</li>
<li>
<p>Post the menu with menu_post() and refresh the
screen.</p>
</li>
<li>
<p>Process the user requests with a loop and do
necessary updates to menu with menu_driver.</p>
</li>
<li>
<p>Unpost the menu with menu_unpost()</p>
</li>
<li>
<p>Free the memory allocated to menu by free_menu()</p>
</li>
<li>
<p>Free the memory allocated to the items with
free_item()</p>
</li>
<li>
<p>End curses</p>
</li>
</ol>
<p>Let's see a program which prints a simple menu and
updates the current selection with up, down arrows.</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="COMPILEMENUS" id=
"COMPILEMENUS">17.2. Compiling With the Menu
Library</a></h3>
<p>To use menu library functions, you have to include
menu.h and to link the program with menu library the flag
-lmenu should be added along with -lncurses in that
order.</p>
<pre class="PROGRAMLISTING">
#include <menu.h>
.
.
.
compile and link: gcc <program file> -lmenu -lncurses
</pre>
<div class="EXAMPLE">
<a name="MMESI" id="MMESI"></a>
<p><b>Example 18. Menu Basics</b></p>
<pre class="PROGRAMLISTING">
<span class="INLINEMEDIAOBJECT">#include <curses.h>
#include <menu.h>
#define ARRAY_SIZE(a) (sizeof(a) / sizeof(a[0]))
#define CTRLD 4
char *choices[] = {
"Choice 1",
"Choice 2",
"Choice 3",
"Choice 4",
"Exit",
};
int main()
{ ITEM **my_items;
int c;
MENU *my_menu;
int n_choices, i;
ITEM *cur_item;
initscr();
cbreak();
noecho();
keypad(stdscr, TRUE);
n_choices = ARRAY_SIZE(choices);
my_items = (ITEM **)calloc(n_choices + 1, sizeof(ITEM *));
for(i = 0; i < n_choices; ++i)
my_items[i] = new_item(choices[i], choices[i]);
my_items[n_choices] = (ITEM *)NULL;
my_menu = new_menu((ITEM **)my_items);
mvprintw(LINES - 2, 0, "F1 to Exit");
post_menu(my_menu);
refresh();
while((c = getch()) != KEY_F(1))
{ switch(c)
{ case KEY_DOWN:
menu_driver(my_menu, REQ_DOWN_ITEM);
break;
case KEY_UP:
menu_driver(my_menu, REQ_UP_ITEM);
break;
}
}
free_item(my_items[0]);
free_item(my_items[1]);
free_menu(my_menu);
endwin();
}
</span>
</pre>
</div>
<p>This program demonstrates the basic concepts involved in
creating a menu using menus library. First we create the
items using new_item() and then attach them to the menu
with new_menu() function. After posting the menu and
refreshing the screen, the main processing loop starts. It
reads user input and takes corresponding action. The
function menu_driver() is the main work horse of the menu
system. The second parameter to this function tells what's
to be done with the menu. According to the parameter,
menu_driver() does the corresponding task. The value can be
either a menu navigational request, an ascii character, or
a KEY_MOUSE special key associated with a mouse event.</p>
<p>The menu_driver accepts following navigational
requests.</p>
<pre class="PROGRAMLISTING">
REQ_LEFT_ITEM Move left to an item.
REQ_RIGHT_ITEM Move right to an item.
REQ_UP_ITEM Move up to an item.
REQ_DOWN_ITEM Move down to an item.
REQ_SCR_ULINE Scroll up a line.
REQ_SCR_DLINE Scroll down a line.
REQ_SCR_DPAGE Scroll down a page.
REQ_SCR_UPAGE Scroll up a page.
REQ_FIRST_ITEM Move to the first item.
REQ_LAST_ITEM Move to the last item.
REQ_NEXT_ITEM Move to the next item.
REQ_PREV_ITEM Move to the previous item.
REQ_TOGGLE_ITEM Select/deselect an item.
REQ_CLEAR_PATTERN Clear the menu pattern buffer.
REQ_BACK_PATTERN Delete the previous character from the pattern buffer.
REQ_NEXT_MATCH Move to the next item matching the pattern match.
REQ_PREV_MATCH Move to the previous item matching the pattern match.
</pre>
<p>Don't get overwhelmed by the number of options. We will
see them slowly one after another. The options of interest
in this example are REQ_UP_ITEM and REQ_DOWN_ITEM. These
two options when passed to menu_driver, menu driver updates
the current item to one item up or down respectively.</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="MENUDRIVER" id=
"MENUDRIVER">17.3. Menu Driver: The work horse of the menu
system</a></h3>
<p>As you have seen in the above example, menu_driver plays
an important role in updating the menu. It is very
important to understand various options it takes and what
they do. As explained above, the second parameter to
menu_driver() can be either a navigational request, a
printable character or a KEY_MOUSE key. Let's dissect the
different navigational requests.</p>
<ul>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_LEFT_ITEM and
REQ_RIGHT_ITEM</i></span></p>
<p>A Menu can be displayed with multiple columns for
more than one item. This can be done by using the
<tt class="LITERAL">menu_format()</tt>function. When a
multi columnar menu is displayed these requests cause
the menu driver to move the current selection to left
or right.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_UP_ITEM and REQ_DOWN_ITEM</i></span></p>
<p>These two options you have seen in the above
example. These options when given, makes the
menu_driver to move the current selection to an item up
or down.</p>
</li>
<li>
<p><span class="emphasis"><i class="EMPHASIS">REQ_SCR_*
options</i></span></p>
<p>The four options REQ_SCR_ULINE, REQ_SCR_DLINE,
REQ_SCR_DPAGE, REQ_SCR_UPAGE are related to scrolling.
If all the items in the menu cannot be displayed in the
menu sub window, then the menu is scrollable. These
requests can be given to the menu_driver to do the
scrolling either one line up, down or one page down or
up respectively.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_FIRST_ITEM, REQ_LAST_ITEM, REQ_NEXT_ITEM
and REQ_PREV_ITEM</i></span></p>
<p>These requests are self explanatory.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_TOGGLE_ITEM</i></span></p>
<p>This request when given, toggles the present
selection. This option is to be used only in a multi
valued menu. So to use this request the option
O_ONEVALUE must be off. This option can be made off or
on with set_menu_opts().</p>
</li>
<li>
<p><span class="emphasis"><i class="EMPHASIS">Pattern
Requests</i></span></p>
<p>Every menu has an associated pattern buffer, which
is used to find the nearest match to the ascii
characters entered by the user. Whenever ascii
characters are given to menu_driver, it puts in to the
pattern buffer. It also tries to find the nearest match
to the pattern in the items list and moves current
selection to that item. The request REQ_CLEAR_PATTERN
clears the pattern buffer. The request REQ_BACK_PATTERN
deletes the previous character in the pattern buffer.
In case the pattern matches more than one item then the
matched items can be cycled through REQ_NEXT_MATCH and
REQ_PREV_MATCH which move the current selection to the
next and previous matches respectively.</p>
</li>
<li>
<p><span class="emphasis"><i class="EMPHASIS">Mouse
Requests</i></span></p>
<p>In case of KEY_MOUSE requests, according to the
mouse position an action is taken accordingly. The
action to be taken is explained in the man page as,</p>
<pre class="PROGRAMLISTING">
<span class="emphasis"><i class=
"EMPHASIS"> If the second argument is the KEY_MOUSE special key, the
associated mouse event is translated into one of the above
pre-defined requests. Currently only clicks in the user
window (e.g. inside the menu display area or the decora­
tion window) are handled. If you click above the display
region of the menu, a REQ_SCR_ULINE is generated, if you
doubleclick a REQ_SCR_UPAGE is generated and if you
tripleclick a REQ_FIRST_ITEM is generated. If you click
below the display region of the menu, a REQ_SCR_DLINE is
generated, if you doubleclick a REQ_SCR_DPAGE is generated
and if you tripleclick a REQ_LAST_ITEM is generated. If
you click at an item inside the display area of the menu,
the menu cursor is positioned to that item.</i></span>
</pre>
</li>
</ul>
<p>Each of the above requests will be explained in the
following lines with several examples whenever
appropriate.</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="MENUWINDOWS" id=
"MENUWINDOWS">17.4. Menu Windows</a></h3>
<p>Every menu created is associated with a window and a sub
window. The menu window displays any title or border
associated with the menu. The menu sub window displays the
menu items currently available for selection. But we didn't
specify any window or sub window in the simple example.
When a window is not specified, stdscr is taken as the main
window, and then menu system calculates the sub window size
required for the display of items. Then items are displayed
in the calculated sub window. So let's play with these
windows and display a menu with a border and a title.</p>
<div class="EXAMPLE">
<a name="MMEWI" id="MMEWI"></a>
<p><b>Example 19. Menu Windows Usage example</b></p>
<pre class="PROGRAMLISTING">
<span class="INLINEMEDIAOBJECT">#include <menu.h>
#define ARRAY_SIZE(a) (sizeof(a) / sizeof(a[0]))
#define CTRLD 4
char *choices[] = {
"Choice 1",
"Choice 2",
"Choice 3",
"Choice 4",
"Exit",
(char *)NULL,
};
void print_in_middle(WINDOW *win, int starty, int startx, int width, char *string, chtype color);
int main()
{ ITEM **my_items;
int c;
MENU *my_menu;
WINDOW *my_menu_win;
int n_choices, i;
/* Initialize curses */
initscr();
start_color();
cbreak();
noecho();
keypad(stdscr, TRUE);
init_pair(1, COLOR_RED, COLOR_BLACK);
/* Create items */
n_choices = ARRAY_SIZE(choices);
my_items = (ITEM **)calloc(n_choices, sizeof(ITEM *));
for(i = 0; i < n_choices; ++i)
my_items[i] = new_item(choices[i], choices[i]);
/* Crate menu */
my_menu = new_menu((ITEM **)my_items);
/* Create the window to be associated with the menu */
my_menu_win = newwin(10, 40, 4, 4);
keypad(my_menu_win, TRUE);
/* Set main window and sub window */
set_menu_win(my_menu, my_menu_win);
set_menu_sub(my_menu, derwin(my_menu_win, 6, 38, 3, 1));
/* Set menu mark to the string " * " */
set_menu_mark(my_menu, " * ");
/* Print a border around the main window and print a title */
box(my_menu_win, 0, 0);
print_in_middle(my_menu_win, 1, 0, 40, "My Menu", COLOR_PAIR(1));
mvwaddch(my_menu_win, 2, 0, ACS_LTEE);
mvwhline(my_menu_win, 2, 1, ACS_HLINE, 38);
mvwaddch(my_menu_win, 2, 39, ACS_RTEE);
mvprintw(LINES - 2, 0, "F1 to exit");
refresh();
/* Post the menu */
post_menu(my_menu);
wrefresh(my_menu_win);
while((c = wgetch(my_menu_win)) != KEY_F(1))
{ switch(c)
{ case KEY_DOWN:
menu_driver(my_menu, REQ_DOWN_ITEM);
break;
case KEY_UP:
menu_driver(my_menu, REQ_UP_ITEM);
break;
}
wrefresh(my_menu_win);
}
/* Unpost and free all the memory taken up */
unpost_menu(my_menu);
free_menu(my_menu);
for(i = 0; i < n_choices; ++i)
free_item(my_items[i]);
endwin();
}
void print_in_middle(WINDOW *win, int starty, int startx, int width, char *string, chtype color)
{ int length, x, y;
float temp;
if(win == NULL)
win = stdscr;
getyx(win, y, x);
if(startx != 0)
x = startx;
if(starty != 0)
y = starty;
if(width == 0)
width = 80;
length = strlen(string);
temp = (width - length)/ 2;
x = startx + (int)temp;
wattron(win, color);
mvwprintw(win, y, x, "%s", string);
wattroff(win, color);
refresh();
}</span>
</pre>
</div>
<p>This example creates a menu with a title, border, a
fancy line separating title and the items. As you can see,
in order to attach a window to a menu the function
set_menu_win() has to be used. Then we attach the sub
window also. This displays the items in the sub window. You
can also set the mark string which gets displayed to the
left of the selected item with set_menu_mark().</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="SCROLLMENUS" id=
"SCROLLMENUS">17.5. Scrolling Menus</a></h3>
<p>If the sub window given for a window is not big enough
to show all the items, then the menu will be scrollable.
When you are on the last item in the present list, if you
send REQ_DOWN_ITEM, it gets translated into REQ_SCR_DLINE
and the menu scrolls by one item. You can manually give
REQ_SCR_ operations to do scrolling. Let's see how it can
be done.</p>
<div class="EXAMPLE">
<a name="MMESC" id="MMESC"></a>
<p><b>Example 20. Scrolling Menus example</b></p>
<pre class="PROGRAMLISTING">
<span class="INLINEMEDIAOBJECT">#include <curses.h>
#include <menu.h>
#define ARRAY_SIZE(a) (sizeof(a) / sizeof(a[0]))
#define CTRLD 4
char *choices[] = {
"Choice 1",
"Choice 2",
"Choice 3",
"Choice 4",
"Choice 5",
"Choice 6",
"Choice 7",
"Choice 8",
"Choice 9",
"Choice 10",
"Exit",
(char *)NULL,
};
void print_in_middle(WINDOW *win, int starty, int startx, int width, char *string, chtype color);
int main()
{ ITEM **my_items;
int c;
MENU *my_menu;
WINDOW *my_menu_win;
int n_choices, i;
/* Initialize curses */
initscr();
start_color();
cbreak();
noecho();
keypad(stdscr, TRUE);
init_pair(1, COLOR_RED, COLOR_BLACK);
init_pair(2, COLOR_CYAN, COLOR_BLACK);
/* Create items */
n_choices = ARRAY_SIZE(choices);
my_items = (ITEM **)calloc(n_choices, sizeof(ITEM *));
for(i = 0; i < n_choices; ++i)
my_items[i] = new_item(choices[i], choices[i]);
/* Crate menu */
my_menu = new_menu((ITEM **)my_items);
/* Create the window to be associated with the menu */
my_menu_win = newwin(10, 40, 4, 4);
keypad(my_menu_win, TRUE);
/* Set main window and sub window */
set_menu_win(my_menu, my_menu_win);
set_menu_sub(my_menu, derwin(my_menu_win, 6, 38, 3, 1));
set_menu_format(my_menu, 5, 1);
/* Set menu mark to the string " * " */
set_menu_mark(my_menu, " * ");
/* Print a border around the main window and print a title */
box(my_menu_win, 0, 0);
print_in_middle(my_menu_win, 1, 0, 40, "My Menu", COLOR_PAIR(1));
mvwaddch(my_menu_win, 2, 0, ACS_LTEE);
mvwhline(my_menu_win, 2, 1, ACS_HLINE, 38);
mvwaddch(my_menu_win, 2, 39, ACS_RTEE);
/* Post the menu */
post_menu(my_menu);
wrefresh(my_menu_win);
attron(COLOR_PAIR(2));
mvprintw(LINES - 2, 0, "Use PageUp and PageDown to scoll down or up a page of items");
mvprintw(LINES - 1, 0, "Arrow Keys to navigate (F1 to Exit)");
attroff(COLOR_PAIR(2));
refresh();
while((c = wgetch(my_menu_win)) != KEY_F(1))
{ switch(c)
{ case KEY_DOWN:
menu_driver(my_menu, REQ_DOWN_ITEM);
break;
case KEY_UP:
menu_driver(my_menu, REQ_UP_ITEM);
break;
case KEY_NPAGE:
menu_driver(my_menu, REQ_SCR_DPAGE);
break;
case KEY_PPAGE:
menu_driver(my_menu, REQ_SCR_UPAGE);
break;
}
wrefresh(my_menu_win);
}
/* Unpost and free all the memory taken up */
unpost_menu(my_menu);
free_menu(my_menu);
for(i = 0; i < n_choices; ++i)
free_item(my_items[i]);
endwin();
}
void print_in_middle(WINDOW *win, int starty, int startx, int width, char *string, chtype color)
{ int length, x, y;
float temp;
if(win == NULL)
win = stdscr;
getyx(win, y, x);
if(startx != 0)
x = startx;
if(starty != 0)
y = starty;
if(width == 0)
width = 80;
length = strlen(string);
temp = (width - length)/ 2;
x = startx + (int)temp;
wattron(win, color);
mvwprintw(win, y, x, "%s", string);
wattroff(win, color);
refresh();
}</span>
</pre>
</div>
<p>This program is self-explanatory. In this example the
number of choices has been increased to ten, which is
larger than our sub window size which can hold 6 items.
This message has to be explicitly conveyed to the menu
system with the function set_menu_format(). In here we
specify the number of rows and columns we want to be
displayed for a single page. We can specify any number of
items to be shown, in the rows variables, if it is less
than the height of the sub window. If the key pressed by
the user is a PAGE UP or PAGE DOWN, the menu is scrolled a
page due to the requests (REQ_SCR_DPAGE and REQ_SCR_UPAGE)
given to menu_driver().</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="MULTICOLUMN" id=
"MULTICOLUMN">17.6. Multi Columnar Menus</a></h3>
<p>In the above example you have seen how to use the
function set_menu_format(). I didn't mention what the cols
variable (third parameter) does. Well, If your sub window
is wide enough, you can opt to display more than one item
per row. This can be specified in the cols variable. To
make things simpler, the following example doesn't show
descriptions for the items.</p>
<div class="EXAMPLE">
<a name="MMEMUCO" id="MMEMUCO"></a>
<p><b>Example 21. Milt Columnar Menus Example</b></p>
<pre class="PROGRAMLISTING">
<span class="INLINEMEDIAOBJECT">#include <curses.h>
#include <menu.h>
#define ARRAY_SIZE(a) (sizeof(a) / sizeof(a[0]))
#define CTRLD 4
char *choices[] = {
"Choice 1", "Choice 2", "Choice 3", "Choice 4", "Choice 5",
"Choice 6", "Choice 7", "Choice 8", "Choice 9", "Choice 10",
"Choice 11", "Choice 12", "Choice 13", "Choice 14", "Choice 15",
"Choice 16", "Choice 17", "Choice 18", "Choice 19", "Choice 20",
"Exit",
(char *)NULL,
};
int main()
{ ITEM **my_items;
int c;
MENU *my_menu;
WINDOW *my_menu_win;
int n_choices, i;
/* Initialize curses */
initscr();
start_color();
cbreak();
noecho();
keypad(stdscr, TRUE);
init_pair(1, COLOR_RED, COLOR_BLACK);
init_pair(2, COLOR_CYAN, COLOR_BLACK);
/* Create items */
n_choices = ARRAY_SIZE(choices);
my_items = (ITEM **)calloc(n_choices, sizeof(ITEM *));
for(i = 0; i < n_choices; ++i)
my_items[i] = new_item(choices[i], choices[i]);
/* Crate menu */
my_menu = new_menu((ITEM **)my_items);
/* Set menu option not to show the description */
menu_opts_off(my_menu, O_SHOWDESC);
/* Create the window to be associated with the menu */
my_menu_win = newwin(10, 70, 4, 4);
keypad(my_menu_win, TRUE);
/* Set main window and sub window */
set_menu_win(my_menu, my_menu_win);
set_menu_sub(my_menu, derwin(my_menu_win, 6, 68, 3, 1));
set_menu_format(my_menu, 5, 3);
set_menu_mark(my_menu, " * ");
/* Print a border around the main window and print a title */
box(my_menu_win, 0, 0);
attron(COLOR_PAIR(2));
mvprintw(LINES - 3, 0, "Use PageUp and PageDown to scroll");
mvprintw(LINES - 2, 0, "Use Arrow Keys to navigate (F1 to Exit)");
attroff(COLOR_PAIR(2));
refresh();
/* Post the menu */
post_menu(my_menu);
wrefresh(my_menu_win);
while((c = wgetch(my_menu_win)) != KEY_F(1))
{ switch(c)
{ case KEY_DOWN:
menu_driver(my_menu, REQ_DOWN_ITEM);
break;
case KEY_UP:
menu_driver(my_menu, REQ_UP_ITEM);
break;
case KEY_LEFT:
menu_driver(my_menu, REQ_LEFT_ITEM);
break;
case KEY_RIGHT:
menu_driver(my_menu, REQ_RIGHT_ITEM);
break;
case KEY_NPAGE:
menu_driver(my_menu, REQ_SCR_DPAGE);
break;
case KEY_PPAGE:
menu_driver(my_menu, REQ_SCR_UPAGE);
break;
}
wrefresh(my_menu_win);
}
/* Unpost and free all the memory taken up */
unpost_menu(my_menu);
free_menu(my_menu);
for(i = 0; i < n_choices; ++i)
free_item(my_items[i]);
endwin();
}</span>
</pre>
</div>
<p>Watch the function call to set_menu_format(). It
specifies the number of columns to be 3, thus displaying 3
items per row. We have also switched off the showing
descriptions with the function menu_opts_off(). There are
couple of functions set_menu_opts(), menu_opts_on() and
menu_opts() which can be used to manipulate menu options.
The following menu options can be specified.</p>
<pre class="PROGRAMLISTING">
O_ONEVALUE
Only one item can be selected for this menu.
O_SHOWDESC
Display the item descriptions when the menu is
posted.
O_ROWMAJOR
Display the menu in row-major order.
O_IGNORECASE
Ignore the case when pattern-matching.
O_SHOWMATCH
Move the cursor to within the item name while pat­
tern-matching.
O_NONCYCLIC
Don't wrap around next-item and previous-item,
requests to the other end of the menu.
</pre>
<p>All options are on by default. You can switch specific
attributes on or off with menu_opts_on() and
menu_opts_off() functions. You can also use set_menu_opts()
to directly specify the options. The argument to this
function should be a OR ed value of some of those above
constants. The function menu_opts() can be used to find out
a menu's present options.</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="MULTIVALUEMENUS" id=
"MULTIVALUEMENUS">17.7. Multi Valued Menus</a></h3>
<p>You might be wondering what if you switch off the option
O_ONEVALUE. Then the menu becomes multi-valued. That means
you can select more than one item. This brings us to the
request REQ_TOGGLE_ITEM. Let's see it in action.</p>
<div class="EXAMPLE">
<a name="MMETO" id="MMETO"></a>
<p><b>Example 22. Multi Valued Menus example</b></p>
<pre class="PROGRAMLISTING">
<span class="INLINEMEDIAOBJECT">#include <curses.h>
#include <menu.h>
#define ARRAY_SIZE(a) (sizeof(a) / sizeof(a[0]))
#define CTRLD 4
char *choices[] = {
"Choice 1",
"Choice 2",
"Choice 3",
"Choice 4",
"Choice 5",
"Choice 6",
"Choice 7",
"Exit",
};
int main()
{ ITEM **my_items;
int c;
MENU *my_menu;
int n_choices, i;
ITEM *cur_item;
/* Initialize curses */
initscr();
cbreak();
noecho();
keypad(stdscr, TRUE);
/* Initialize items */
n_choices = ARRAY_SIZE(choices);
my_items = (ITEM **)calloc(n_choices + 1, sizeof(ITEM *));
for(i = 0; i < n_choices; ++i)
my_items[i] = new_item(choices[i], choices[i]);
my_items[n_choices] = (ITEM *)NULL;
my_menu = new_menu((ITEM **)my_items);
/* Make the menu multi valued */
menu_opts_off(my_menu, O_ONEVALUE);
mvprintw(LINES - 3, 0, "Use <SPACE> to select or unselect an item.");
mvprintw(LINES - 2, 0, "<ENTER> to see presently selected items(F1 to Exit)");
post_menu(my_menu);
refresh();
while((c = getch()) != KEY_F(1))
{ switch(c)
{ case KEY_DOWN:
menu_driver(my_menu, REQ_DOWN_ITEM);
break;
case KEY_UP:
menu_driver(my_menu, REQ_UP_ITEM);
break;
case ' ':
menu_driver(my_menu, REQ_TOGGLE_ITEM);
break;
case 10: /* Enter */
{ char temp[200];
ITEM **items;
items = menu_items(my_menu);
temp[0] = '\0';
for(i = 0; i < item_count(my_menu); ++i)
if(item_value(items[i]) == TRUE)
{ strcat(temp, item_name(items[i]));
strcat(temp, " ");
}
move(20, 0);
clrtoeol();
mvprintw(20, 0, temp);
refresh();
}
break;
}
}
free_item(my_items[0]);
free_item(my_items[1]);
free_menu(my_menu);
endwin();
}
</span>
</pre>
</div>
<p>Whew, A lot of new functions. Let's take them one after
another. Firstly, the REQ_TOGGLE_ITEM. In a multi-valued
menu, the user should be allowed to select or un select
more than one item. The request REQ_TOGGLE_ITEM toggles the
present selection. In this case when space is pressed
REQ_TOGGLE_ITEM request is sent to menu_driver to achieve
the result.</p>
<p>Now when the user presses <ENTER> we show the
items he presently selected. First we find out the items
associated with the menu using the function menu_items().
Then we loop through the items to find out if the item is
selected or not. The function item_value() returns TRUE if
an item is selected. The function item_count() returns the
number of items in the menu. The item name can be found
with item_name(). You can also find the description
associated with an item using item_description().</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="MENUOPT" id="MENUOPT">17.8. Menu
Options</a></h3>
<p>Well, by this time you must be itching for some
difference in your menu, with lots of functionality. I
know. You want Colors !!!. You want to create nice menus
similar to those text mode <a href=
"http://www.jersey.net/~debinjoe/games/" target="_top">dos
games</a>. The functions set_menu_fore() and
set_menu_back() can be used to change the attribute of the
selected item and unselected item. The names are
misleading. They don't change menu's foreground or
background which would have been useless.</p>
<p>The function set_menu_grey() can be used to set the
display attribute for the non-selectable items in the menu.
This brings us to the interesting option for an item the
one and only O_SELECTABLE. We can turn it off by the
function item_opts_off() and after that that item is not
selectable. It's like a grayed item in those fancy windows
menus. Let's put these concepts in practice with this
example</p>
<div class="EXAMPLE">
<a name="MMEAT" id="MMEAT"></a>
<p><b>Example 23. Menu Options example</b></p>
<pre class="PROGRAMLISTING">
<span class="INLINEMEDIAOBJECT">#include <menu.h>
#define ARRAY_SIZE(a) (sizeof(a) / sizeof(a[0]))
#define CTRLD 4
char *choices[] = {
"Choice 1",
"Choice 2",
"Choice 3",
"Choice 4",
"Choice 5",
"Choice 6",
"Choice 7",
"Exit",
};
int main()
{ ITEM **my_items;
int c;
MENU *my_menu;
int n_choices, i;
ITEM *cur_item;
/* Initialize curses */
initscr();
start_color();
cbreak();
noecho();
keypad(stdscr, TRUE);
init_pair(1, COLOR_RED, COLOR_BLACK);
init_pair(2, COLOR_GREEN, COLOR_BLACK);
init_pair(3, COLOR_MAGENTA, COLOR_BLACK);
/* Initialize items */
n_choices = ARRAY_SIZE(choices);
my_items = (ITEM **)calloc(n_choices + 1, sizeof(ITEM *));
for(i = 0; i < n_choices; ++i)
my_items[i] = new_item(choices[i], choices[i]);
my_items[n_choices] = (ITEM *)NULL;
item_opts_off(my_items[3], O_SELECTABLE);
item_opts_off(my_items[6], O_SELECTABLE);
/* Create menu */
my_menu = new_menu((ITEM **)my_items);
/* Set fore ground and back ground of the menu */
set_menu_fore(my_menu, COLOR_PAIR(1) | A_REVERSE);
set_menu_back(my_menu, COLOR_PAIR(2));
set_menu_grey(my_menu, COLOR_PAIR(3));
/* Post the menu */
mvprintw(LINES - 3, 0, "Press <ENTER> to see the option selected");
mvprintw(LINES - 2, 0, "Up and Down arrow keys to naviage (F1 to Exit)");
post_menu(my_menu);
refresh();
while((c = getch()) != KEY_F(1))
{ switch(c)
{ case KEY_DOWN:
menu_driver(my_menu, REQ_DOWN_ITEM);
break;
case KEY_UP:
menu_driver(my_menu, REQ_UP_ITEM);
break;
case 10: /* Enter */
move(20, 0);
clrtoeol();
mvprintw(20, 0, "Item selected is : %s",
item_name(current_item(my_menu)));
pos_menu_cursor(my_menu);
break;
}
}
unpost_menu(my_menu);
for(i = 0; i < n_choices; ++i)
free_item(my_items[i]);
free_menu(my_menu);
endwin();
}
</span>
</pre>
</div>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="MENUUSERPTR" id=
"MENUUSERPTR">17.9. The useful User Pointer</a></h3>
<p>We can associate a user pointer with each item in the
menu. It works the same way as user pointer in panels. It's
not touched by menu system. You can store any thing you
like in that. I usually use it to store the function to be
executed when the menu option is chosen (It's selected and
may be the user pressed <ENTER>);</p>
<div class="EXAMPLE">
<a name="MMEUS" id="MMEUS"></a>
<p><b>Example 24. Menu User Pointer Usage</b></p>
<pre class="PROGRAMLISTING">
<span class="INLINEMEDIAOBJECT">#include <curses.h>
#include <menu.h>
#define ARRAY_SIZE(a) (sizeof(a) / sizeof(a[0]))
#define CTRLD 4
char *choices[] = {
"Choice 1",
"Choice 2",
"Choice 3",
"Choice 4",
"Choice 5",
"Choice 6",
"Choice 7",
"Exit",
};
void func(char *name);
int main()
{ ITEM **my_items;
int c;
MENU *my_menu;
int n_choices, i;
ITEM *cur_item;
/* Initialize curses */
initscr();
start_color();
cbreak();
noecho();
keypad(stdscr, TRUE);
init_pair(1, COLOR_RED, COLOR_BLACK);
init_pair(2, COLOR_GREEN, COLOR_BLACK);
init_pair(3, COLOR_MAGENTA, COLOR_BLACK);
/* Initialize items */
n_choices = ARRAY_SIZE(choices);
my_items = (ITEM **)calloc(n_choices + 1, sizeof(ITEM *));
for(i = 0; i < n_choices; ++i)
{ my_items[i] = new_item(choices[i], choices[i]);
/* Set the user pointer */
set_item_userptr(my_items[i], func);
}
my_items[n_choices] = (ITEM *)NULL;
/* Create menu */
my_menu = new_menu((ITEM **)my_items);
/* Post the menu */
mvprintw(LINES - 3, 0, "Press <ENTER> to see the option selected");
mvprintw(LINES - 2, 0, "Up and Down arrow keys to naviage (F1 to Exit)");
post_menu(my_menu);
refresh();
while((c = getch()) != KEY_F(1))
{ switch(c)
{ case KEY_DOWN:
menu_driver(my_menu, REQ_DOWN_ITEM);
break;
case KEY_UP:
menu_driver(my_menu, REQ_UP_ITEM);
break;
case 10: /* Enter */
{ ITEM *cur;
void (*p)(char *);
cur = current_item(my_menu);
p = item_userptr(cur);
p((char *)item_name(cur));
pos_menu_cursor(my_menu);
break;
}
break;
}
}
unpost_menu(my_menu);
for(i = 0; i < n_choices; ++i)
free_item(my_items[i]);
free_menu(my_menu);
endwin();
}
void func(char *name)
{ move(20, 0);
clrtoeol();
mvprintw(20, 0, "Item selected is : %s", name);
} </span>
</pre>
</div>
</div>
</div>
<div class="SECT1">
<hr>
<h2 class="SECT1"><a name="FORMS" id="FORMS">18. Forms
Library</a></h2>
<p>Well. If you have seen those forms on web pages which take
input from users and do various kinds of things, you might be
wondering how would any one create such forms in text mode
display. It's quite difficult to write those nifty forms in
plain ncurses. Forms library tries to provide a basic frame
work to build and maintain forms with ease. It has lot of
features(functions) which manage validation, dynamic
expansion of fields etc.. Let's see it in full flow.</p>
<p>A form is a collection of fields; each field can be either
a label(static text) or a data-entry location. The forms also
library provides functions to divide forms into multiple
pages.</p>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="FORMBASICS" id=
"FORMBASICS">18.1. The Basics</a></h3>
<p>Forms are created in much the same way as menus. First
the fields related to the form are created with
new_field(). You can set options for the fields, so that
they can be displayed with some fancy attributes, validated
before the field looses focus etc.. Then the fields are
attached to form. After this, the form can be posted to
display and is ready to receive inputs. On the similar
lines to menu_driver(), the form is manipulated with
form_driver(). We can send requests to form_driver to move
focus to a certain field, move cursor to end of the field
etc.. After the user enters values in the fields and
validation done, form can be unposted and memory allocated
can be freed.</p>
<p>The general flow of control of a forms program looks
like this.</p>
<ol type="1">
<li>
<p>Initialize curses</p>
</li>
<li>
<p>Create fields using new_field(). You can specify the
height and width of the field, and its position on the
form.</p>
</li>
<li>
<p>Create the forms with new_form() by specifying the
fields to be attached with.</p>
</li>
<li>
<p>Post the form with form_post() and refresh the
screen.</p>
</li>
<li>
<p>Process the user requests with a loop and do
necessary updates to form with form_driver.</p>
</li>
<li>
<p>Unpost the menu with form_unpost()</p>
</li>
<li>
<p>Free the memory allocated to menu by free_form()</p>
</li>
<li>
<p>Free the memory allocated to the items with
free_field()</p>
</li>
<li>
<p>End curses</p>
</li>
</ol>
<p>As you can see, working with forms library is much
similar to handling menu library. The following examples
will explore various aspects of form processing. Let's
start the journey with a simple example. first.</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="COMPILEFORMS" id=
"COMPILEFORMS">18.2. Compiling With the Forms
Library</a></h3>
<p>To use forms library functions, you have to include
form.h and to link the program with forms library the flag
-lform should be added along with -lncurses in that
order.</p>
<pre class="PROGRAMLISTING">
#include <form.h>
.
.
.
compile and link: gcc <program file> -lform -lncurses
</pre>
<div class="EXAMPLE">
<a name="FFOSI" id="FFOSI"></a>
<p><b>Example 25. Forms Basics</b></p>
<pre class="PROGRAMLISTING">
<span class="INLINEMEDIAOBJECT">#include <form.h>
int main()
{ FIELD *field[3];
FORM *my_form;
int ch;
/* Initialize curses */
initscr();
cbreak();
noecho();
keypad(stdscr, TRUE);
/* Initialize the fields */
field[0] = new_field(1, 10, 4, 18, 0, 0);
field[1] = new_field(1, 10, 6, 18, 0, 0);
field[2] = NULL;
/* Set field options */
set_field_back(field[0], A_UNDERLINE); /* Print a line for the option */
field_opts_off(field[0], O_AUTOSKIP); /* Don't go to next field when this */
/* Field is filled up */
set_field_back(field[1], A_UNDERLINE);
field_opts_off(field[1], O_AUTOSKIP);
/* Create the form and post it */
my_form = new_form(field);
post_form(my_form);
refresh();
mvprintw(4, 10, "Value 1:");
mvprintw(6, 10, "Value 2:");
refresh();
/* Loop through to get user requests */
while((ch = getch()) != KEY_F(1))
{ switch(ch)
{ case KEY_DOWN:
/* Go to next field */
form_driver(my_form, REQ_NEXT_FIELD);
/* Go to the end of the present buffer */
/* Leaves nicely at the last character */
form_driver(my_form, REQ_END_LINE);
break;
case KEY_UP:
/* Go to previous field */
form_driver(my_form, REQ_PREV_FIELD);
form_driver(my_form, REQ_END_LINE);
break;
default:
/* If this is a normal character, it gets */
/* Printed */
form_driver(my_form, ch);
break;
}
}
/* Un post form and free the memory */
unpost_form(my_form);
free_form(my_form);
free_field(field[0]);
free_field(field[1]);
endwin();
return 0;
}</span>
</pre>
</div>
<p>Above example is pretty straight forward. It creates two
fields with <tt class="LITERAL">new_field()</tt>.
new_field() takes height, width, starty, startx, number of
offscreen rows and number of additional working buffers.
The fifth argument number of offscreen rows specifies how
much of the field to be shown. If it is zero, the entire
field is always displayed otherwise the form will be
scrollable when the user accesses not displayed parts of
the field. The forms library allocates one buffer per field
to store the data user enters. Using the last parameter to
new_field() we can specify it to allocate some additional
buffers. These can be used for any purpose you like.</p>
<p>After creating the fields, back ground attribute of both
of them is set to an underscore with set_field_back(). The
AUTOSKIP option is turned off using field_opts_off(). If
this option is turned on, focus will move to the next field
in the form once the active field is filled up
completely.</p>
<p>After attaching the fields to the form, it is posted.
Here on, user inputs are processed in the while loop, by
making corresponding requests to form_driver. The details
of all the requests to the form_driver() are explained
later.</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="PLAYFIELDS" id=
"PLAYFIELDS">18.3. Playing with Fields</a></h3>
<p>Each form field is associated with a lot of attributes.
They can be manipulated to get the required effect and to
have fun !!!. So why wait?</p>
<div class="SECT3">
<hr>
<h4 class="SECT3"><a name="FETCHINFO" id=
"FETCHINFO">18.3.1. Fetching Size and Location of
Field</a></h4>
<p>The parameters we have given at the time of creation
of a field can be retrieved with field_info(). It returns
height, width, starty, startx, number of offscreen rows,
and number of additional buffers into the parameters
given to it. It is a sort of inverse of new_field().</p>
<pre class="PROGRAMLISTING">
int field_info( FIELD *field, /* field from which to fetch */
int *height, *int width, /* field size */
int *top, int *left, /* upper left corner */
int *offscreen, /* number of offscreen rows */
int *nbuf); /* number of working buffers */
</pre>
</div>
<div class="SECT3">
<hr>
<h4 class="SECT3"><a name="MOVEFIELD" id=
"MOVEFIELD">18.3.2. Moving the field</a></h4>
<p>The location of the field can be moved to a different
position with move_field().</p>
<pre class="PROGRAMLISTING">
int move_field( FIELD *field, /* field to alter */
int top, int left); /* new upper-left corner */
</pre>
<p>As usual, the changed position can be queried with
field_infor().</p>
</div>
<div class="SECT3">
<hr>
<h4 class="SECT3"><a name="JUSTIFYFIELD" id=
"JUSTIFYFIELD">18.3.3. Field Justification</a></h4>
<p>The justification to be done for the field can be
fixed using the function set_field_just().</p>
<pre class="PROGRAMLISTING">
int set_field_just(FIELD *field, /* field to alter */
int justmode); /* mode to set */
int field_just(FIELD *field); /* fetch justify mode of field */
</pre>
<p>The justification mode valued accepted and returned by
these functions are NO_JUSTIFICATION, JUSTIFY_RIGHT,
JUSTIFY_LEFT, or JUSTIFY_CENTER.</p>
</div>
<div class="SECT3">
<hr>
<h4 class="SECT3"><a name="FIELDDISPATTRIB" id=
"FIELDDISPATTRIB">18.3.4. Field Display
Attributes</a></h4>
<p>As you have seen, in the above example, display
attribute for the fields can be set with set_field_fore()
and setfield_back(). These functions set foreground and
background attribute of the fields. You can also specify
a pad character which will be filled in the unfilled
portion of the field. The pad character is set with a
call to set_field_pad(). Default pad value is a space.
The functions field_fore(), field_back, field_pad() can
be used to query the present foreground, background
attributes and pad character for the field. The following
list gives the usage of functions.</p>
<pre class="PROGRAMLISTING">
int set_field_fore(FIELD *field, /* field to alter */
chtype attr); /* attribute to set */
chtype field_fore(FIELD *field); /* field to query */
/* returns foreground attribute */
int set_field_back(FIELD *field, /* field to alter */
chtype attr); /* attribute to set */
chtype field_back(FIELD *field); /* field to query */
/* returns background attribute */
int set_field_pad(FIELD *field, /* field to alter */
int pad); /* pad character to set */
chtype field_pad(FIELD *field); /* field to query */
/* returns present pad character */
</pre>
<p>Though above functions seem quite simple, using colors
with set_field_fore() may be frustrating in the
beginning. Let me first explain about foreground and
background attributes of a field. The foreground
attribute is associated with the character. That means a
character in the field is printed with the attribute you
have set with set_field_fore(). Background attribute is
the attribute used to fill background of field, whether
any character is there or not. So what about colors?
Since colors are always defined in pairs, what is the
right way to display colored fields? Here's an example
clarifying color attributes.</p>
<div class="EXAMPLE">
<a name="FFOAT" id="FFOAT"></a>
<p><b>Example 26. Form Attributes example</b></p>
<pre class="PROGRAMLISTING">
<span class="INLINEMEDIAOBJECT">#include <form.h>
int main()
{ FIELD *field[3];
FORM *my_form;
int ch;
/* Initialize curses */
initscr();
start_color();
cbreak();
noecho();
keypad(stdscr, TRUE);
/* Initialize few color pairs */
init_pair(1, COLOR_WHITE, COLOR_BLUE);
init_pair(2, COLOR_WHITE, COLOR_BLUE);
/* Initialize the fields */
field[0] = new_field(1, 10, 4, 18, 0, 0);
field[1] = new_field(1, 10, 6, 18, 0, 0);
field[2] = NULL;
/* Set field options */
set_field_fore(field[0], COLOR_PAIR(1));/* Put the field with blue background */
set_field_back(field[0], COLOR_PAIR(2));/* and white foreground (characters */
/* are printed in white */
field_opts_off(field[0], O_AUTOSKIP); /* Don't go to next field when this */
/* Field is filled up */
set_field_back(field[1], A_UNDERLINE);
field_opts_off(field[1], O_AUTOSKIP);
/* Create the form and post it */
my_form = new_form(field);
post_form(my_form);
refresh();
set_current_field(my_form, field[0]); /* Set focus to the colored field */
mvprintw(4, 10, "Value 1:");
mvprintw(6, 10, "Value 2:");
mvprintw(LINES - 2, 0, "Use UP, DOWN arrow keys to switch between fields");
refresh();
/* Loop through to get user requests */
while((ch = getch()) != KEY_F(1))
{ switch(ch)
{ case KEY_DOWN:
/* Go to next field */
form_driver(my_form, REQ_NEXT_FIELD);
/* Go to the end of the present buffer */
/* Leaves nicely at the last character */
form_driver(my_form, REQ_END_LINE);
break;
case KEY_UP:
/* Go to previous field */
form_driver(my_form, REQ_PREV_FIELD);
form_driver(my_form, REQ_END_LINE);
break;
default:
/* If this is a normal character, it gets */
/* Printed */
form_driver(my_form, ch);
break;
}
}
/* Un post form and free the memory */
unpost_form(my_form);
free_form(my_form);
free_field(field[0]);
free_field(field[1]);
endwin();
return 0;
}</span>
</pre>
</div>
<p>Play with the color pairs and try to understand the
foreground and background attributes. In my programs
using color attributes, I usually set only the background
with set_field_back(). Curses simply doesn't allow
defining individual color attributes.</p>
</div>
<div class="SECT3">
<hr>
<h4 class="SECT3"><a name="FIELDOPTIONBITS" id=
"FIELDOPTIONBITS">18.3.5. Field Option Bits</a></h4>
<p>There is also a large collection of field option bits
you can set to control various aspects of forms
processing. You can manipulate them with these
functions:</p>
<pre class="PROGRAMLISTING">
int set_field_opts(FIELD *field, /* field to alter */
int attr); /* attribute to set */
int field_opts_on(FIELD *field, /* field to alter */
int attr); /* attributes to turn on */
int field_opts_off(FIELD *field, /* field to alter */
int attr); /* attributes to turn off */
int field_opts(FIELD *field); /* field to query */
</pre>
<p>The function set_field_opts() can be used to directly
set attributes of a field or you can choose to switch a
few attributes on and off with field_opts_on() and
field_opts_off() selectively. Anytime you can query the
attributes of a field with field_opts(). The following is
the list of available options. By default, all options
are on.</p>
<div class="VARIABLELIST">
<dl>
<dt>O_VISIBLE</dt>
<dd>
<p>Controls whether the field is visible on the
screen. Can be used during form processing to hide
or pop up fields depending on the value of parent
fields.</p>
</dd>
<dt>O_ACTIVE</dt>
<dd>
<p>Controls whether the field is active during
forms processing (i.e. visited by form navigation
keys). Can be used to make labels or derived fields
with buffer values alterable by the forms
application, not the user.</p>
</dd>
<dt>O_PUBLIC</dt>
<dd>
<p>Controls whether data is displayed during field
entry. If this option is turned off on a field, the
library will accept and edit data in that field,
but it will not be displayed and the visible field
cursor will not move. You can turn off the O_PUBLIC
bit to define password fields.</p>
</dd>
<dt>O_EDIT</dt>
<dd>
<p>Controls whether the field's data can be
modified. When this option is off, all editing
requests except <tt class=
"LITERAL">REQ_PREV_CHOICE</tt> and <tt class=
"LITERAL">REQ_NEXT_CHOICE</tt>will fail. Such
read-only fields may be useful for help
messages.</p>
</dd>
<dt>O_WRAP</dt>
<dd>
<p>Controls word-wrapping in multi-line fields.
Normally, when any character of a (blank-separated)
word reaches the end of the current line, the
entire word is wrapped to the next line (assuming
there is one). When this option is off, the word
will be split across the line break.</p>
</dd>
<dt>O_BLANK</dt>
<dd>
<p>Controls field blanking. When this option is on,
entering a character at the first field position
erases the entire field (except for the
just-entered character).</p>
</dd>
<dt>O_AUTOSKIP</dt>
<dd>
<p>Controls automatic skip to next field when this
one fills. Normally, when the forms user tries to
type more data into a field than will fit, the
editing location jumps to next field. When this
option is off, the user's cursor will hang at the
end of the field. This option is ignored in dynamic
fields that have not reached their size limit.</p>
</dd>
<dt>O_NULLOK</dt>
<dd>
<p>Controls whether validation is applied to blank
fields. Normally, it is not; the user can leave a
field blank without invoking the usual validation
check on exit. If this option is off on a field,
exit from it will invoke a validation check.</p>
</dd>
<dt>O_PASSOK</dt>
<dd>
<p>Controls whether validation occurs on every
exit, or only after the field is modified. Normally
the latter is true. Setting O_PASSOK may be useful
if your field's validation function may change
during forms processing.</p>
</dd>
<dt>O_STATIC</dt>
<dd>
<p>Controls whether the field is fixed to its
initial dimensions. If you turn this off, the field
becomes dynamic and will stretch to fit entered
data.</p>
</dd>
</dl>
</div>
<p>A field's options cannot be changed while the field is
currently selected. However, options may be changed on
posted fields that are not current.</p>
<p>The option values are bit-masks and can be composed
with logical-or in the obvious way. You have seen the
usage of switching off O_AUTOSKIP option. The following
example clarifies usage of some more options. Other
options are explained where appropriate.</p>
<div class="EXAMPLE">
<a name="FFOOP" id="FFOOP"></a>
<p><b>Example 27. Field Options Usage example</b></p>
<pre class="PROGRAMLISTING">
<span class="INLINEMEDIAOBJECT">#include <form.h>
#define STARTX 15
#define STARTY 4
#define WIDTH 25
#define N_FIELDS 3
int main()
{ FIELD *field[N_FIELDS];
FORM *my_form;
int ch, i;
/* Initialize curses */
initscr();
cbreak();
noecho();
keypad(stdscr, TRUE);
/* Initialize the fields */
for(i = 0; i < N_FIELDS - 1; ++i)
field[i] = new_field(1, WIDTH, STARTY + i * 2, STARTX, 0, 0);
field[N_FIELDS - 1] = NULL;
/* Set field options */
set_field_back(field[1], A_UNDERLINE); /* Print a line for the option */
field_opts_off(field[0], O_ACTIVE); /* This field is a static label */
field_opts_off(field[1], O_PUBLIC); /* This filed is like a password field*/
field_opts_off(field[1], O_AUTOSKIP); /* To avoid entering the same field */
/* after last character is entered */
/* Create the form and post it */
my_form = new_form(field);
post_form(my_form);
refresh();
set_field_just(field[0], JUSTIFY_CENTER); /* Center Justification */
set_field_buffer(field[0], 0, "This is a static Field");
/* Initialize the field */
mvprintw(STARTY, STARTX - 10, "Field 1:");
mvprintw(STARTY + 2, STARTX - 10, "Field 2:");
refresh();
/* Loop through to get user requests */
while((ch = getch()) != KEY_F(1))
{ switch(ch)
{ case KEY_DOWN:
/* Go to next field */
form_driver(my_form, REQ_NEXT_FIELD);
/* Go to the end of the present buffer */
/* Leaves nicely at the last character */
form_driver(my_form, REQ_END_LINE);
break;
case KEY_UP:
/* Go to previous field */
form_driver(my_form, REQ_PREV_FIELD);
form_driver(my_form, REQ_END_LINE);
break;
default:
/* If this is a normal character, it gets */
/* Printed */
form_driver(my_form, ch);
break;
}
}
/* Un post form and free the memory */
unpost_form(my_form);
free_form(my_form);
free_field(field[0]);
free_field(field[1]);
endwin();
return 0;
}</span>
</pre>
</div>
<p>This example, though useless, shows the usage of
options. If used properly, they can present information
very effectively in a form. The second field being not
O_PUBLIC, does not show the characters you are
typing.</p>
</div>
<div class="SECT3">
<hr>
<h4 class="SECT3"><a name="FIELDSTATUS" id=
"FIELDSTATUS">18.3.6. Field Status</a></h4>
<p>The field status specifies whether the field has got
edited or not. It is initially set to FALSE and when user
enters something and the data buffer gets modified it
becomes TRUE. So a field's status can be queried to find
out whether it has been modified or not. The following
functions can assist in those operations.</p>
<pre class="PROGRAMLISTING">
int set_field_status(FIELD *field, /* field to alter */
int status); /* status to set */
int field_status(FIELD *field); /* fetch status of field */
</pre>
<p>It's better to check the field's status only after
after leaving the field, as data buffer might not have
been updated yet as the validation is still due. To
guarantee that right status is returned, call
field_status() either (1) in the field's exit validation
check routine, (2) from the field's or form's
initialization or termination hooks, or (3) just after a
REQ_VALIDATION request has been processed by the forms
driver</p>
</div>
<div class="SECT3">
<hr>
<h4 class="SECT3"><a name="FIELDUSERPTR" id=
"FIELDUSERPTR">18.3.7. Field User Pointer</a></h4>
<p>Every field structure contains one pointer that can be
used by the user for various purposes. It is not touched
by forms library and can be used for any purpose by the
user. The following functions set and fetch user
pointer.</p>
<pre class="PROGRAMLISTING">
int set_field_userptr(FIELD *field,
char *userptr); /* the user pointer you wish to associate */
/* with the field */
char *field_userptr(FIELD *field); /* fetch user pointer of the field */
</pre>
</div>
<div class="SECT3">
<hr>
<h4 class="SECT3"><a name="VARIABLESIZEFIELDS" id=
"VARIABLESIZEFIELDS">18.3.8. Variable-Sized
Fields</a></h4>
<p>If you want a dynamically changing field with variable
width, this is the feature you want to put to full use.
This will allow the user to enter more data than the
original size of the field and let the field grow.
According to the field orientation it will scroll
horizontally or vertically to incorporate the new
data.</p>
<p>To make a field dynamically growable, the option
O_STATIC should be turned off. This can be done with
a</p>
<pre class="PROGRAMLISTING">
field_opts_off(field_pointer, O_STATIC);
</pre>
<p>But it's usually not advisable to allow a field to
grow infinitely. You can set a maximum limit to the
growth of the field with</p>
<pre class="PROGRAMLISTING">
int set_max_field(FIELD *field, /* Field on which to operate */
int max_growth); /* maximum growth allowed for the field */
</pre>
<p>The field info for a dynamically growable field can be
retrieved by</p>
<pre class="PROGRAMLISTING">
int dynamic_field_info( FIELD *field, /* Field on which to operate */
int *prows, /* number of rows will be filled in this */
int *pcols, /* number of columns will be filled in this*/
int *pmax) /* maximum allowable growth will be filled */
/* in this */
</pre>Though field_info work as usual, it is advisable to use this
function to get the proper attributes of a dynamically growable
field.
<p>Recall the library routine new_field; a new field
created with height set to one will be defined to be a
one line field. A new field created with height greater
than one will be defined to be a multi line field.</p>
<p>A one line field with O_STATIC turned off (dynamically
growable field) will contain a single fixed row, but the
number of columns can increase if the user enters more
data than the initial field will hold. The number of
columns displayed will remain fixed and the additional
data will scroll horizontally.</p>
<p>A multi line field with O_STATIC turned off
(dynamically growable field) will contain a fixed number
of columns, but the number of rows can increase if the
user enters more data than the initial field will hold.
The number of rows displayed will remain fixed and the
additional data will scroll vertically.</p>
<p>The above two paragraphs pretty much describe a
dynamically growable field's behavior. The way other
parts of forms library behaves is described below:</p>
<ol type="1">
<li>
<p>The field option O_AUTOSKIP will be ignored if the
option O_STATIC is off and there is no maximum growth
specified for the field. Currently, O_AUTOSKIP
generates an automatic REQ_NEXT_FIELD form driver
request when the user types in the last character
position of a field. On a growable field with no
maximum growth specified, there is no last character
position. If a maximum growth is specified, the
O_AUTOSKIP option will work as normal if the field
has grown to its maximum size.</p>
</li>
<li>
<p>The field justification will be ignored if the
option O_STATIC is off. Currently, set_field_just can
be used to JUSTIFY_LEFT, JUSTIFY_RIGHT,
JUSTIFY_CENTER the contents of a one line field. A
growable one line field will, by definition, grow and
scroll horizontally and may contain more data than
can be justified. The return from field_just will be
unchanged.</p>
</li>
<li>
<p>The overloaded form driver request REQ_NEW_LINE
will operate the same way regardless of the
O_NL_OVERLOAD form option if the field option
O_STATIC is off and there is no maximum growth
specified for the field. Currently, if the form
option O_NL_OVERLOAD is on, REQ_NEW_LINE implicitly
generates a REQ_NEXT_FIELD if called from the last
line of a field. If a field can grow without bound,
there is no last line, so REQ_NEW_LINE will never
implicitly generate a REQ_NEXT_FIELD. If a maximum
growth limit is specified and the O_NL_OVERLOAD form
option is on, REQ_NEW_LINE will only implicitly
generate REQ_NEXT_FIELD if the field has grown to its
maximum size and the user is on the last line.</p>
</li>
<li>
<p>The library call dup_field will work as usual; it
will duplicate the field, including the current
buffer size and contents of the field being
duplicated. Any specified maximum growth will also be
duplicated.</p>
</li>
<li>
<p>The library call link_field will work as usual; it
will duplicate all field attributes and share buffers
with the field being linked. If the O_STATIC field
option is subsequently changed by a field sharing
buffers, how the system reacts to an attempt to enter
more data into the field than the buffer will
currently hold will depend on the setting of the
option in the current field.</p>
</li>
<li>
<p>The library call field_info will work as usual;
the variable nrow will contain the value of the
original call to new_field. The user should use
dynamic_field_info, described above, to query the
current size of the buffer.</p>
</li>
</ol>
<p>Some of the above points make sense only after
explaining form driver. We will be looking into that in
next few sections.</p>
</div>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="FORMWINDOWS" id=
"FORMWINDOWS">18.4. Form Windows</a></h3>
<p>The form windows concept is pretty much similar to menu
windows. Every form is associated with a main window and a
sub window. The form main window displays any title or
border associated or whatever the user wishes. Then the sub
window contains all the fields and displays them according
to their position. This gives the flexibility of
manipulating fancy form displaying very easily.</p>
<p>Since this is pretty much similar to menu windows, I am
providing an example with out much explanation. The
functions are similar and they work the same way.</p>
<div class="EXAMPLE">
<a name="FFOWI" id="FFOWI"></a>
<p><b>Example 28. Form Windows Example</b></p>
<pre class="PROGRAMLISTING">
<span class="INLINEMEDIAOBJECT">#include <form.h>
void print_in_middle(WINDOW *win, int starty, int startx, int width, char *string, chtype color);
int main()
{
FIELD *field[3];
FORM *my_form;
WINDOW *my_form_win;
int ch, rows, cols;
/* Initialize curses */
initscr();
start_color();
cbreak();
noecho();
keypad(stdscr, TRUE);
/* Initialize few color pairs */
init_pair(1, COLOR_RED, COLOR_BLACK);
/* Initialize the fields */
field[0] = new_field(1, 10, 6, 1, 0, 0);
field[1] = new_field(1, 10, 8, 1, 0, 0);
field[2] = NULL;
/* Set field options */
set_field_back(field[0], A_UNDERLINE);
field_opts_off(field[0], O_AUTOSKIP); /* Don't go to next field when this */
/* Field is filled up */
set_field_back(field[1], A_UNDERLINE);
field_opts_off(field[1], O_AUTOSKIP);
/* Create the form and post it */
my_form = new_form(field);
/* Calculate the area required for the form */
scale_form(my_form, &rows, &cols);
/* Create the window to be associated with the form */
my_form_win = newwin(rows + 4, cols + 4, 4, 4);
keypad(my_form_win, TRUE);
/* Set main window and sub window */
set_form_win(my_form, my_form_win);
set_form_sub(my_form, derwin(my_form_win, rows, cols, 2, 2));
/* Print a border around the main window and print a title */
box(my_form_win, 0, 0);
print_in_middle(my_form_win, 1, 0, cols + 4, "My Form", COLOR_PAIR(1));
post_form(my_form);
wrefresh(my_form_win);
mvprintw(LINES - 2, 0, "Use UP, DOWN arrow keys to switch between fields");
refresh();
/* Loop through to get user requests */
while((ch = wgetch(my_form_win)) != KEY_F(1))
{ switch(ch)
{ case KEY_DOWN:
/* Go to next field */
form_driver(my_form, REQ_NEXT_FIELD);
/* Go to the end of the present buffer */
/* Leaves nicely at the last character */
form_driver(my_form, REQ_END_LINE);
break;
case KEY_UP:
/* Go to previous field */
form_driver(my_form, REQ_PREV_FIELD);
form_driver(my_form, REQ_END_LINE);
break;
default:
/* If this is a normal character, it gets */
/* Printed */
form_driver(my_form, ch);
break;
}
}
/* Un post form and free the memory */
unpost_form(my_form);
free_form(my_form);
free_field(field[0]);
free_field(field[1]);
endwin();
return 0;
}
void print_in_middle(WINDOW *win, int starty, int startx, int width, char *string, chtype color)
{ int length, x, y;
float temp;
if(win == NULL)
win = stdscr;
getyx(win, y, x);
if(startx != 0)
x = startx;
if(starty != 0)
y = starty;
if(width == 0)
width = 80;
length = strlen(string);
temp = (width - length)/ 2;
x = startx + (int)temp;
wattron(win, color);
mvwprintw(win, y, x, "%s", string);
wattroff(win, color);
refresh();
}</span>
</pre>
</div>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="FILEDVALIDATE" id=
"FILEDVALIDATE">18.5. Field Validation</a></h3>
<p>By default, a field will accept any data input by the
user. It is possible to attach validation to the field.
Then any attempt by the user to leave the field, while it
contains data that doesn't match the validation type will
fail. Some validation types also have a character-validity
check for each time a character is entered in the
field.</p>
<p>Validation can be attached to a field with the following
function.</p>
<pre class="PROGRAMLISTING">
int set_field_type(FIELD *field, /* field to alter */
FIELDTYPE *ftype, /* type to associate */
...); /* additional arguments*/
</pre>Once set, the validation type for a field can be queried with
<pre class="PROGRAMLISTING">
FIELDTYPE *field_type(FIELD *field); /* field to query */
</pre>
<p>The form driver validates the data in a field only when
data is entered by the end-user. Validation does not occur
when</p>
<ul>
<li>
<p>the application program changes the field value by
calling set_field_buffer.</p>
</li>
<li>
<p>linked field values are changed indirectly -- by
changing the field to which they are linked</p>
</li>
</ul>
<p>The following are the pre-defined validation types. You
can also specify custom validation, though it's a bit
tricky and cumbersome.</p>
<h1 class="BRIDGEHEAD"><a name="AEN1069" id=
"AEN1069"></a>TYPE_ALPHA</h1>
<p>This field type accepts alphabetic data; no blanks, no
digits, no special characters (this is checked at
character-entry time). It is set up with:</p>
<pre class="PROGRAMLISTING">
int set_field_type(FIELD *field, /* field to alter */
TYPE_ALPHA, /* type to associate */
int width); /* minimum width of field */
</pre>
<p>The width argument sets a minimum width of data. The
user has to enter at-least width number of characters
before he can leave the field. Typically you'll want to set
this to the field width; if it's greater than the field
width, the validation check will always fail. A minimum
width of zero makes field completion optional.</p>
<h1 class="BRIDGEHEAD"><a name="AEN1073" id=
"AEN1073"></a>TYPE_ALNUM</h1>
<p>This field type accepts alphabetic data and digits; no
blanks, no special characters (this is checked at
character-entry time). It is set up with:</p>
<pre class="PROGRAMLISTING">
int set_field_type(FIELD *field, /* field to alter */
TYPE_ALNUM, /* type to associate */
int width); /* minimum width of field */
</pre>
<p>The width argument sets a minimum width of data. As with
TYPE_ALPHA, typically you'll want to set this to the field
width; if it's greater than the field width, the validation
check will always fail. A minimum width of zero makes field
completion optional.</p>
<h1 class="BRIDGEHEAD"><a name="AEN1077" id=
"AEN1077"></a>TYPE_ENUM</h1>
<p>This type allows you to restrict a field's values to be
among a specified set of string values (for example, the
two-letter postal codes for U.S. states). It is set up
with:</p>
<pre class="PROGRAMLISTING">
int set_field_type(FIELD *field, /* field to alter */
TYPE_ENUM, /* type to associate */
char **valuelist; /* list of possible values */
int checkcase; /* case-sensitive? */
int checkunique); /* must specify uniquely? */
</pre>
<p>The valuelist parameter must point at a NULL-terminated
list of valid strings. The checkcase argument, if true,
makes comparison with the string case-sensitive.</p>
<p>When the user exits a TYPE_ENUM field, the validation
procedure tries to complete the data in the buffer to a
valid entry. If a complete choice string has been entered,
it is of course valid. But it is also possible to enter a
prefix of a valid string and have it completed for you.</p>
<p>By default, if you enter such a prefix and it matches
more than one value in the string list, the prefix will be
completed to the first matching value. But the checkunique
argument, if true, requires prefix matches to be unique in
order to be valid.</p>
<p>The REQ_NEXT_CHOICE and REQ_PREV_CHOICE input requests
can be particularly useful with these fields.</p>
<h1 class="BRIDGEHEAD"><a name="AEN1084" id=
"AEN1084"></a>TYPE_INTEGER</h1>
<p>This field type accepts an integer. It is set up as
follows:</p>
<pre class="PROGRAMLISTING">
int set_field_type(FIELD *field, /* field to alter */
TYPE_INTEGER, /* type to associate */
int padding, /* # places to zero-pad to */
int vmin, int vmax); /* valid range */
</pre>
<p>Valid characters consist of an optional leading minus
and digits. The range check is performed on exit. If the
range maximum is less than or equal to the minimum, the
range is ignored.</p>
<p>If the value passes its range check, it is padded with
as many leading zero digits as necessary to meet the
padding argument.</p>
<p>A TYPE_INTEGER value buffer can conveniently be
interpreted with the C library function atoi(3).</p>
<h1 class="BRIDGEHEAD"><a name="AEN1090" id=
"AEN1090"></a>TYPE_NUMERIC</h1>
<p>This field type accepts a decimal number. It is set up
as follows:</p>
<pre class="PROGRAMLISTING">
int set_field_type(FIELD *field, /* field to alter */
TYPE_NUMERIC, /* type to associate */
int padding, /* # places of precision */
int vmin, int vmax); /* valid range */
</pre>
<p>Valid characters consist of an optional leading minus
and digits. possibly including a decimal point. The range
check is performed on exit. If the range maximum is less
than or equal to the minimum, the range is ignored.</p>
<p>If the value passes its range check, it is padded with
as many trailing zero digits as necessary to meet the
padding argument.</p>
<p>A TYPE_NUMERIC value buffer can conveniently be
interpreted with the C library function atof(3).</p>
<h1 class="BRIDGEHEAD"><a name="AEN1096" id=
"AEN1096"></a>TYPE_REGEXP</h1>
<p>This field type accepts data matching a regular
expression. It is set up as follows:</p>
<pre class="PROGRAMLISTING">
int set_field_type(FIELD *field, /* field to alter */
TYPE_REGEXP, /* type to associate */
char *regexp); /* expression to match */
</pre>
<p>The syntax for regular expressions is that of
regcomp(3). The check for regular-expression match is
performed on exit.</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="FORMDRIVER" id=
"FORMDRIVER">18.6. Form Driver: The work horse of the forms
system</a></h3>
<p>As in the menu system, form_driver() plays a very
important role in forms system. All types of requests to
forms system should be funneled through form_driver().</p>
<pre class="PROGRAMLISTING">
int form_driver(FORM *form, /* form on which to operate */
int request) /* form request code */
</pre>
<p>As you have seen some of the examples above, you have to
be in a loop looking for user input and then decide whether
it's a field data or a form request. The form requests are
then passed to form_driver() to do the work.</p>
<p>The requests roughly can be divided into following
categories. Different requests and their usage is explained
below:</p>
<div class="SECT3">
<hr>
<h4 class="SECT3"><a name="PAGENAVREQ" id=
"PAGENAVREQ">18.6.1. Page Navigation Requests</a></h4>
<p>These requests cause page-level moves through the
form, triggering display of a new form screen. A form can
be made of multiple pages. If you have a big form with
lot of fields and logical sections, then you can divide
the form into pages. The function set_new_page() to set a
new page at the field specified.</p>
<pre class="PROGRAMLISTING">
int set_new_page(FIELD *field,/* Field at which page break to be set or unset */
bool new_page_flag); /* should be TRUE to put a break */
</pre>
<p>The following requests allow you to move to different
pages</p>
<ul>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_NEXT_PAGE</i></span> Move to the next
form page.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_PREV_PAGE</i></span> Move to the
previous form page.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_FIRST_PAGE</i></span> Move to the
first form page.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_LAST_PAGE</i></span> Move to the last
form page.</p>
</li>
</ul>
<p>These requests treat the list as cyclic; that is,
REQ_NEXT_PAGE from the last page goes to the first, and
REQ_PREV_PAGE from the first page goes to the last.</p>
</div>
<div class="SECT3">
<hr>
<h4 class="SECT3"><a name="INTERFIELDNAVREQ" id=
"INTERFIELDNAVREQ">18.6.2. Inter-Field Navigation
Requests</a></h4>
<p>These requests handle navigation between fields on the
same page.</p>
<ul>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_NEXT_FIELD</i></span> Move to next
field.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_PREV_FIELD</i></span> Move to previous
field.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_FIRST_FIELD</i></span> Move to the
first field.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_LAST_FIELD</i></span> Move to the last
field.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_SNEXT_FIELD</i></span> Move to sorted
next field.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_SPREV_FIELD</i></span> Move to sorted
previous field.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_SFIRST_FIELD</i></span> Move to the
sorted first field.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_SLAST_FIELD</i></span> Move to the
sorted last field.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_LEFT_FIELD</i></span> Move left to
field.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_RIGHT_FIELD</i></span> Move right to
field.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_UP_FIELD</i></span> Move up to
field.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_DOWN_FIELD</i></span> Move down to
field.</p>
</li>
</ul>
<p>These requests treat the list of fields on a page as
cyclic; that is, REQ_NEXT_FIELD from the last field goes
to the first, and REQ_PREV_FIELD from the first field
goes to the last. The order of the fields for these (and
the REQ_FIRST_FIELD and REQ_LAST_FIELD requests) is
simply the order of the field pointers in the form array
(as set up by new_form() or set_form_fields()</p>
<p>It is also possible to traverse the fields as if they
had been sorted in screen-position order, so the sequence
goes left-to-right and top-to-bottom. To do this, use the
second group of four sorted-movement requests.</p>
<p>Finally, it is possible to move between fields using
visual directions up, down, right, and left. To
accomplish this, use the third group of four requests.
Note, however, that the position of a form for purposes
of these requests is its upper-left corner.</p>
<p>For example, suppose you have a multi-line field B,
and two single-line fields A and C on the same line with
B, with A to the left of B and C to the right of B. A
REQ_MOVE_RIGHT from A will go to B only if A, B, and C
all share the same first line; otherwise it will skip
over B to C.</p>
</div>
<div class="SECT3">
<hr>
<h4 class="SECT3"><a name="INTRAFIELDNAVREQ" id=
"INTRAFIELDNAVREQ">18.6.3. Intra-Field Navigation
Requests</a></h4>
<p>These requests drive movement of the edit cursor
within the currently selected field.</p>
<ul>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_NEXT_CHAR</i></span> Move to next
character.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_PREV_CHAR</i></span> Move to previous
character.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_NEXT_LINE</i></span> Move to next
line.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_PREV_LINE</i></span> Move to previous
line.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_NEXT_WORD</i></span> Move to next
word.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_PREV_WORD</i></span> Move to previous
word.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_BEG_FIELD</i></span> Move to beginning
of field.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_END_FIELD</i></span> Move to end of
field.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_BEG_LINE</i></span> Move to beginning
of line.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_END_LINE</i></span> Move to end of
line.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_LEFT_CHAR</i></span> Move left in
field.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_RIGHT_CHAR</i></span> Move right in
field.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_UP_CHAR</i></span> Move up in
field.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_DOWN_CHAR</i></span> Move down in
field.</p>
</li>
</ul>
<p>Each word is separated from the previous and next
characters by whitespace. The commands to move to
beginning and end of line or field look for the first or
last non-pad character in their ranges.</p>
</div>
<div class="SECT3">
<hr>
<h4 class="SECT3"><a name="SCROLLREQ" id=
"SCROLLREQ">18.6.4. Scrolling Requests</a></h4>
<p>Fields that are dynamic and have grown and fields
explicitly created with offscreen rows are scrollable.
One-line fields scroll horizontally; multi-line fields
scroll vertically. Most scrolling is triggered by editing
and intra-field movement (the library scrolls the field
to keep the cursor visible). It is possible to explicitly
request scrolling with the following requests:</p>
<ul>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_SCR_FLINE</i></span> Scroll vertically
forward a line.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_SCR_BLINE</i></span> Scroll vertically
backward a line.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_SCR_FPAGE</i></span> Scroll vertically
forward a page.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_SCR_BPAGE</i></span> Scroll vertically
backward a page.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_SCR_FHPAGE</i></span> Scroll
vertically forward half a page.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_SCR_BHPAGE</i></span> Scroll
vertically backward half a page.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_SCR_FCHAR</i></span> Scroll
horizontally forward a character.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_SCR_BCHAR</i></span> Scroll
horizontally backward a character.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_SCR_HFLINE</i></span> Scroll
horizontally one field width forward.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_SCR_HBLINE</i></span> Scroll
horizontally one field width backward.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_SCR_HFHALF</i></span> Scroll
horizontally one half field width forward.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_SCR_HBHALF</i></span> Scroll
horizontally one half field width backward.</p>
</li>
</ul>
<p>For scrolling purposes, a page of a field is the
height of its visible part.</p>
</div>
<div class="SECT3">
<hr>
<h4 class="SECT3"><a name="EDITREQ" id="EDITREQ">18.6.5.
Editing Requests</a></h4>
<p>When you pass the forms driver an ASCII character, it
is treated as a request to add the character to the
field's data buffer. Whether this is an insertion or a
replacement depends on the field's edit mode (insertion
is the default.</p>
<p>The following requests support editing the field and
changing the edit mode:</p>
<ul>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_INS_MODE</i></span> Set insertion
mode.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_OVL_MODE</i></span> Set overlay
mode.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_NEW_LINE</i></span> New line request
(see below for explanation).</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_INS_CHAR</i></span> Insert space at
character location.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_INS_LINE</i></span> Insert blank line
at character location.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_DEL_CHAR</i></span> Delete character
at cursor.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_DEL_PREV</i></span> Delete previous
word at cursor.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_DEL_LINE</i></span> Delete line at
cursor.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_DEL_WORD</i></span> Delete word at
cursor.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_CLR_EOL</i></span> Clear to end of
line.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_CLR_EOF</i></span> Clear to end of
field.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_CLR_FIELD</i></span> Clear entire
field.</p>
</li>
</ul>
<p>The behavior of the REQ_NEW_LINE and REQ_DEL_PREV
requests is complicated and partly controlled by a pair
of forms options. The special cases are triggered when
the cursor is at the beginning of a field, or on the last
line of the field.</p>
<p>First, we consider REQ_NEW_LINE:</p>
<p>The normal behavior of REQ_NEW_LINE in insert mode is
to break the current line at the position of the edit
cursor, inserting the portion of the current line after
the cursor as a new line following the current and moving
the cursor to the beginning of that new line (you may
think of this as inserting a newline in the field
buffer).</p>
<p>The normal behavior of REQ_NEW_LINE in overlay mode is
to clear the current line from the position of the edit
cursor to end of line. The cursor is then moved to the
beginning of the next line.</p>
<p>However, REQ_NEW_LINE at the beginning of a field, or
on the last line of a field, instead does a
REQ_NEXT_FIELD. O_NL_OVERLOAD option is off, this special
action is disabled.</p>
<p>Now, let us consider REQ_DEL_PREV:</p>
<p>The normal behavior of REQ_DEL_PREV is to delete the
previous character. If insert mode is on, and the cursor
is at the start of a line, and the text on that line will
fit on the previous one, it instead appends the contents
of the current line to the previous one and deletes the
current line (you may think of this as deleting a newline
from the field buffer).</p>
<p>However, REQ_DEL_PREV at the beginning of a field is
instead treated as a REQ_PREV_FIELD.</p>
<p>If the O_BS_OVERLOAD option is off, this special
action is disabled and the forms driver just returns
E_REQUEST_DENIED.</p>
</div>
<div class="SECT3">
<hr>
<h4 class="SECT3"><a name="ORDERREQ" id=
"ORDERREQ">18.6.6. Order Requests</a></h4>
<p>If the type of your field is ordered, and has
associated functions for getting the next and previous
values of the type from a given value, there are requests
that can fetch that value into the field buffer:</p>
<ul>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_NEXT_CHOICE</i></span> Place the
successor value of the current value in the
buffer.</p>
</li>
<li>
<p><span class="emphasis"><i class=
"EMPHASIS">REQ_PREV_CHOICE</i></span> Place the
predecessor value of the current value in the
buffer.</p>
</li>
</ul>
<p>Of the built-in field types, only TYPE_ENUM has
built-in successor and predecessor functions. When you
define a field type of your own (see Custom Validation
Types), you can associate our own ordering functions.</p>
</div>
<div class="SECT3">
<hr>
<h4 class="SECT3"><a name="APPLICCOMMANDS" id=
"APPLICCOMMANDS">18.6.7. Application Commands</a></h4>
<p>Form requests are represented as integers above the
curses value greater than KEY_MAX and less than or equal
to the constant MAX_COMMAND. A value within this range
gets ignored by form_driver(). So this can be used for
any purpose by the application. It can be treated as an
application specific action and take corresponding
action.</p>
</div>
</div>
</div>
<div class="SECT1">
<hr>
<h2 class="SECT1"><a name="TOOLS" id="TOOLS">19. Tools and
Widget Libraries</a></h2>
<p>Now that you have seen the capabilities of ncurses and its
sister libraries, you are rolling your sleeves up and gearing
for a project that heavily manipulates screen. But wait.. It
can be pretty difficult to write and maintain complex GUI
widgets in plain ncurses or even with the additional
libraries. There are some ready-to-use tools and widget
libraries that can be used instead of writing your own
widgets. You can use some of them, get ideas from the code,
or even extend them.</p>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="CDK" id="CDK">19.1. CDK (Curses
Development Kit)</a></h3>
<p>In the author's words</p>
<p><span class="emphasis"><i class="EMPHASIS">CDK stands
for 'Curses Development Kit' and it currently contains 21
ready to use widgets which facilitate the speedy
development of full screen curses programs.</i></span></p>
<p>The kit provides some useful widgets, which can be used
in your programs directly. It's pretty well written and the
documentation is very good. The examples in the examples
directory can be a good place to start for beginners. The
CDK can be downloaded from <a href=
"https://invisible-island.net/cdk/" target=
"_top">https://invisible-island.net/cdk/</a> . Follow the
instructions in README file to install it.</p>
<div class="SECT3">
<hr>
<h4 class="SECT3"><a name="WIDGETLIST" id=
"WIDGETLIST">19.1.1. Widget List</a></h4>
<p>The following is the list of widgets provided with cdk
and their description.</p>
<pre class="PROGRAMLISTING">
Widget Type Quick Description
===========================================================================
Alphalist Allows a user to select from a list of words, with
the ability to narrow the search list by typing in a
few characters of the desired word.
Buttonbox This creates a multiple button widget.
Calendar Creates a little simple calendar widget.
Dialog Prompts the user with a message, and the user
can pick an answer from the buttons provided.
Entry Allows the user to enter various types of information.
File Selector A file selector built from Cdk base widgets. This
example shows how to create more complicated widgets
using the Cdk widget library.
Graph Draws a graph.
Histogram Draws a histogram.
Item List Creates a pop up field which allows the user to select
one of several choices in a small field. Very useful
for things like days of the week or month names.
Label Displays messages in a pop up box, or the label can be
considered part of the screen.
Marquee Displays a message in a scrolling marquee.
Matrix Creates a complex matrix with lots of options.
Menu Creates a pull-down menu interface.
Multiple Line Entry A multiple line entry field. Very useful
for long fields. (like a description
field)
Radio List Creates a radio button list.
Scale Creates a numeric scale. Used for allowing a user to
pick a numeric value and restrict them to a range of
values.
Scrolling List Creates a scrolling list/menu list.
Scrolling Window Creates a scrolling log file viewer. Can add
information into the window while its running.
A good widget for displaying the progress of
something. (akin to a console window)
Selection List Creates a multiple option selection list.
Slider Akin to the scale widget, this widget provides a
visual slide bar to represent the numeric value.
Template Creates a entry field with character sensitive
positions. Used for pre-formatted fields like
dates and phone numbers.
Viewer This is a file/information viewer. Very useful
when you need to display loads of information.
===========================================================================
</pre>
<p>A few of the widgets are modified by Thomas Dickey in
recent versions.</p>
</div>
<div class="SECT3">
<hr>
<h4 class="SECT3"><a name="CDKATTRACT" id=
"CDKATTRACT">19.1.2. Some Attractive Features</a></h4>
<p>Apart from making our life easier with readily usable
widgets, cdk solves one frustrating problem with printing
multi colored strings, justified strings elegantly.
Special formatting tags can be embedded in the strings
which are passed to CDK functions. For Example</p>
<p>If the string</p>
<pre class="PROGRAMLISTING">
"</B/1>This line should have a yellow foreground and a blue
background.<!1>"
</pre>
<p>given as a parameter to newCDKLabel(), it prints the
line with yellow foreground and blue background. There
are other tags available for justifying string, embedding
special drawing characters etc.. Please refer to the man
page cdk_display(3X) for details. The man page explains
the usage with nice examples.</p>
</div>
<div class="SECT3">
<hr>
<h4 class="SECT3"><a name="CDKCONCLUSION" id=
"CDKCONCLUSION">19.1.3. Conclusion</a></h4>
<p>All in all, CDK is a well-written package of widgets,
which if used properly can form a strong frame work for
developing complex GUI.</p>
</div>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="DIALOG" id="DIALOG">19.2. The
dialog</a></h3>
<p>Long long ago, in September 1994, when few people knew
linux, Jeff Tranter wrote an <a href=
"http://www2.linuxjournal.com/lj-issues/issue5/2807.html"
target="_top">article</a> on dialog in Linux Journal. He
starts the article with these words..</p>
<p><span class="emphasis"><i class="EMPHASIS">Linux is
based on the Unix operating system, but also features a
number of unique and useful kernel features and application
programs that often go beyond what is available under Unix.
One little-known gem is "dialog", a utility for creating
professional-looking dialog boxes from within shell
scripts. This article presents a tutorial introduction to
the dialog utility, and shows examples of how and where it
can be used</i></span></p>
<p>As he explains, dialog is a real gem in making
professional-looking dialog boxes with ease. It creates a
variety of dialog boxes, menus, check lists etc.. It is
usually installed by default. If not, you can download it
from <a href="https://invisible-island.net/dialog/" target=
"_top">Thomas Dickey</a>'s site.</p>
<p>The above-mentioned article gives a very good overview
of its uses and capabilites. The man page has more details.
It can be used in variety of situations. One good example
is building of linux kernel in text mode. Linux kernel uses
a modified version of dialog tailored for its needs.</p>
<p>dialog was initially designed to be used with shell
scripts. If you want to use its functionality in a c
program, then you can use libdialog. The documentation
regarding this is sparse. Definitive reference is the
dialog.h header file which comes with the library. You may
need to hack here and there to get the required output. The
source is easily customizable. I have used it on a number
of occasions by modifying the code.</p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="PERLCURSES" id=
"PERLCURSES">19.3. Perl Curses Modules CURSES::FORM and
CURSES::WIDGETS</a></h3>
<p>The perl module Curses, Curses::Form and Curses::Widgets
give access to curses from perl. If you have curses and
basic perl is installed, you can get these modules from
<a href="http://www.cpan.org/modules/01modules.index.html"
target="_top">CPAN All Modules page</a>. Get the three
zipped modules in the Curses category. Once installed you
can use these modules from perl scripts like any other
module. For more information on perl modules see perlmod
man page. The above modules come with good documentation
and they have some demo scripts to test the functionality.
Though the widgets provided are very rudimentary, these
modules provide good access to curses library from
perl.</p>
<p>Some of my code examples are converted to perl by
Anuradha Ratnaweera and they are available in the
<tt class="LITERAL">perl</tt> directory.</p>
<p>For more information see man pages Curses(3) ,
Curses::Form(3) and Curses::Widgets(3). These pages are
installed only when the above modules are acquired and
installed.</p>
</div>
</div>
<div class="SECT1">
<hr>
<h2 class="SECT1"><a name="JUSTFORFUN" id="JUSTFORFUN">20.
Just For Fun !!!</a></h2>
<p>This section contains few programs written by me just for
fun. They don't signify a better programming practice or the
best way of using ncurses. They are provided here so as to
allow beginners to get ideas and add more programs to this
section. If you have written a couple of nice, simple
programs in curses and want them to included here, contact
<a href="mailto:ppadala@gmail.com" target="_top">me</a>.</p>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="GAMEOFLIFE" id=
"GAMEOFLIFE">20.1. The Game of Life</a></h3>
<p>Game of life is a wonder of math. In <a href=
"http://www.math.com/students/wonders/life/life.html"
target="_top">Paul Callahan</a>'s words</p>
<pre class="PROGRAMLISTING">
<span class="emphasis"><i class=
"EMPHASIS">The Game of Life (or simply Life) is not a game in the conventional sense. There
are no players, and no winning or losing. Once the "pieces" are placed in the
starting position, the rules determine everything that happens later.
Nevertheless, Life is full of surprises! In most cases, it is impossible to look
at a starting position (or pattern) and see what will happen in the future. The
only way to find out is to follow the rules of the game.</i></span>
</pre>
<p>This program starts with a simple inverted U pattern and
shows how wonderful life works. There is a lot of room for
improvement in the program. You can let the user enter
pattern of his choice or even take input from a file. You
can also change rules and play with a lot of variations.
Search on <a href="http://www.google.com" target=
"_top">google</a> for interesting information on game of
life.</p>
<p><span class="emphasis"><i class="EMPHASIS">File Path:
JustForFun/life.c</i></span></p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="MAGIC" id="MAGIC">20.2. Magic
Square</a></h3>
<p>Magic Square, another wonder of math, is very simple to
understand but very difficult to make. In a magic square
sum of the numbers in each row, each column is equal. Even
diagnol sum can be equal. There are many variations which
have special properties.</p>
<p>This program creates a simple magic square of odd
order.</p>
<p><span class="emphasis"><i class="EMPHASIS">File Path:
JustForFun/magic.c</i></span></p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="HANOI" id="HANOI">20.3. Towers
of Hanoi</a></h3>
<p>The famous towers of hanoi solver. The aim of the game
is to move the disks on the first peg to last peg, using
middle peg as a temporary stay. The catch is not to place a
larger disk over a small disk at any time.</p>
<p><span class="emphasis"><i class="EMPHASIS">File Path:
JustForFun/hanoi.c</i></span></p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="QUEENS" id="QUEENS">20.4. Queens
Puzzle</a></h3>
<p>The objective of the famous N-Queen puzzle is to put N
queens on a N X N chess board without attacking each
other.</p>
<p>This program solves it with a simple backtracking
technique.</p>
<p><span class="emphasis"><i class="EMPHASIS">File Path:
JustForFun/queens.c</i></span></p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="SHUFFLE" id="SHUFFLE">20.5.
Shuffle</a></h3>
<p>A fun game, if you have time to kill.</p>
<p><span class="emphasis"><i class="EMPHASIS">File Path:
JustForFun/shuffle.c</i></span></p>
</div>
<div class="SECT2">
<hr>
<h3 class="SECT2"><a name="TT" id="TT">20.6. Typing
Tutor</a></h3>
<p>A simple typing tutor, I created more out of need than
for ease of use. If you know how to put your fingers
correctly on the keyboard, but lack practice, this can be
helpful.</p>
<p><span class="emphasis"><i class="EMPHASIS">File Path:
JustForFun/tt.c</i></span></p>
</div>
</div>
<div class="SECT1">
<hr>
<h2 class="SECT1"><a name="REF" id="REF">21.
References</a></h2>
<ul>
<li>
<p>NCURSES man pages</p>
</li>
<li>
<p>NCURSES FAQ at <a href=
"https://invisible-island.net/ncurses/ncurses.faq.html"
target=
"_top">https://invisible-island.net/ncurses/ncurses.faq.html</a></p>
</li>
<li>
<p>Writing programs with NCURSES by Eric Raymond and Zeyd
M. Ben-Halim at <a href=
"https://invisible-island.net/ncurses/ncurses-intro.html"
target=
"_top">https://invisible-island.net/ncurses/ncurses-intro.html</a>
- somewhat obsolete. I was inspired by this document and
the structure of this HOWTO follows from the original
document</p>
</li>
</ul>
</div>
</div>
</body>
</html>
|
