Searched refs:AA_RESIZE (Results 1 – 13 of 13) sorted by relevance
88 return (AA_RESIZE); in slang_getchar()143 return (AA_RESIZE); in slang_getchar()
58 if (ch == AA_RESIZE && c->resizehandler != NULL) in aa_getevent()80 } while (c == AA_MOUSE || c == AA_RESIZE || c>=AA_RELEASE); in aa_getkey()
56 return (AA_RESIZE); in stdin_getchar()
92 return (AA_RESIZE); in curses_getchar()
87 return (AA_RESIZE); in X_getchar()
145 while (!(event = aa_getevent (context, 0)) || event == AA_RESIZE) in game()
57 #define AA_RESIZE 258 /*special keycodes */ macro
106 if ( (evt > AA_NONE) && (evt < AA_RELEASE) && (evt != AA_MOUSE) && (evt != AA_RESIZE) ) { in AA_PumpEvents()
194 case AA_RESIZE: in gp_cmd_capture_preview()
265 while (!(event = aa_getevent (context, 0)) || event == AA_RESIZE) in game()
297 case AA_RESIZE: in Manage()
1165 two special events AA_MOUSE and AA_RESIZE (will be explained later)1225 @findex AA_RESIZE1229 This event is reported by AA_RESIZE. Then application is expected to call the function1239 the catch of AA_RESIZE is more complicated and you should use the resize handler.1246 functions when AA_RESIZE event appears. Some simple apps that don't rely on
1736 takes into account the AA_RESIZE event. The context is reinitialized