Searched refs:alert (Results 1 – 17 of 17) sorted by relevance
46 /* Retain the NSWindow because we'll show the alert later on the main thread */57 - (void)showAlert:(NSAlert*)alert80 clicked = [alert runModal];99 NSAlert* alert = [[[NSAlert alloc] init] autorelease];102 [alert setAlertStyle:NSAlertStyleCritical];104 [alert setAlertStyle:NSAlertStyleWarning];106 [alert setAlertStyle:NSAlertStyleInformational];109 [alert setMessageText:[NSString stringWithUTF8String:messageboxdata->title]];110 [alert setInformativeText:[NSString stringWithUTF8String:messageboxdata->message]];124 button = [alert addButtonWithTitle:[NSString stringWithUTF8String:sdlButton->text]];[all …]
45 /* Run the main event loop until the alert has finished */67 UIAlertController *alert;92 [alert addAction:action];95 alert.preferredAction = action;154 UIAlertView *alert = [[UIAlertView alloc] init];157 alert.delegate = delegate;158 alert.title = @(messageboxdata->title);159 alert.message = @(messageboxdata->message);168 [alert addButtonWithTitle:@(sdlButton->text)];173 [alert show];[all …]
50 my.alert({ content: res.content })63 my.alert({ content: "请选择目标设备" })137 my.alert({ content: "配网失败，设备无回复" })157 my.alert({ content: '请输入正确的SSID' })161 my.alert({ content: '请输入正确的密码' })214 my.alert({ content: "配网失败，设备无回复" })
60 my.alert({ content: "二维码格式错误" });87 my.alert({ content: res.content })99 my.alert({ content: '请输入正确的三元组信息' })151 my.alert({ content: "下发三元组失败：设备无回复" })
1 {"Illegal invocation": alert()}
10 my.alert({ contant: "请扫描正确的预览二维码" });
103 } alert; member
135 event.data.alert.module_name = node->module_name; in _diag_desc_list_send()136 event.data.alert.level = node->level; in _diag_desc_list_send()137 event.data.alert.desc = node->desc; in _diag_desc_list_send()
72 } alert; member
360 function alert() { function758 "\x12": alert, /* ^R - reverse-search */759 "\x13": alert, /* ^S - search */904 alert(); /* beep! */
352 function alert() { function750 "\x12": alert, /* ^R - reverse-search */751 "\x13": alert, /* ^S - search */896 alert(); /* beep! */
5448 uint8_t alert; in ssl_parse_certificate_chain() local5590 alert = MBEDTLS_SSL_ALERT_MSG_INTERNAL_ERROR; in ssl_parse_certificate_chain()5594 alert = MBEDTLS_SSL_ALERT_MSG_UNSUPPORTED_CERT; in ssl_parse_certificate_chain()5598 alert = MBEDTLS_SSL_ALERT_MSG_BAD_CERT; in ssl_parse_certificate_chain()5880 uint8_t alert; in mbedtls_ssl_parse_certificate() local5888 alert = MBEDTLS_SSL_ALERT_MSG_BAD_CERT; in mbedtls_ssl_parse_certificate()5900 alert = MBEDTLS_SSL_ALERT_MSG_CERT_EXPIRED; in mbedtls_ssl_parse_certificate()5902 alert = MBEDTLS_SSL_ALERT_MSG_CERT_REVOKED; in mbedtls_ssl_parse_certificate()5904 alert = MBEDTLS_SSL_ALERT_MSG_UNKNOWN_CA; in mbedtls_ssl_parse_certificate()5906 alert = MBEDTLS_SSL_ALERT_MSG_CERT_UNKNOWN; in mbedtls_ssl_parse_certificate()[all …]
302 'alert': alert, property in common.defaultMessageTypes
380 * Fail when receiving a TLS alert message with an invalid length, or invalid954 when sending the alert failed. The fix makes sure not to hide the error955 that triggered the alert.957 peer after sending a fatal alert to refuse a renegotiation attempt.958 Previous behaviour was to keep processing data even after the alert has975 sending the fatal alert and just drop the connection.1951 * Some example server programs were not sending the close_notify alert.2337 * Some example server programs were not sending the close_notify alert.2460 * Sending of security-relevant alert messages that do not break
1241 * Enable sending of alert messages in case of encountered errors as per RFC.1242 * If you choose not to send the alert messages, mbed TLS can still communicate1245 * The advantage of not sending alert messages, is that no information is given1248 * Enable sending of all alert messages
960 /* init was successful, alert parent thread and start running... */
4045 alert(UTF8ToString($0) + "\n\n" + UTF8ToString($1)); in SDL_ShowSimpleMessageBox()
Completed in 47 milliseconds