@@ -391,14 +391,14 @@ fn make_notify_method(class_name: &TyName, ctx: &mut Context) -> TokenStream {
391
391
/// If you call this method on a user-defined object while holding a `GdRef` or `GdMut` guard on the instance, you will encounter
392
392
/// a panic. The reason is that the receiving virtual method `on_notification()` acquires a `GdMut` lock dynamically, which must
393
393
/// be exclusive.
394
- pub fn issue_notification ( & mut self , what: #enum_name) {
394
+ pub fn notify ( & mut self , what: #enum_name) {
395
395
self . notification( i32 :: from( what) as i64 , false ) ;
396
396
}
397
397
398
- /// ⚠️ Like [`Self::issue_notification ()`], but starts at the most-derived class and goes up the hierarchy.
398
+ /// ⚠️ Like [`Self::notify ()`], but starts at the most-derived class and goes up the hierarchy.
399
399
///
400
400
/// See docs of that method, including the panics.
401
- pub fn issue_notification_reversed ( & mut self , what: #enum_name) {
401
+ pub fn notify_reversed ( & mut self , what: #enum_name) {
402
402
self . notification( i32 :: from( what) as i64 , true ) ;
403
403
}
404
404
}
@@ -1299,7 +1299,7 @@ fn special_virtual_methods(notification_enum_name: &Ident) -> TokenStream {
1299
1299
/// to represent integers out of known constants (mistakes or future additions).
1300
1300
///
1301
1301
/// This method is named `_notification` in Godot, but `on_notification` in Rust. To _send_ notifications, use the
1302
- /// [`Object::issue_notification `][crate::engine::Object::issue_notification ] method.
1302
+ /// [`Object::notify `][crate::engine::Object::notify ] method.
1303
1303
///
1304
1304
/// See also in Godot docs:
1305
1305
/// * [`Object::_notification`](https://docs.godotengine.org/en/stable/classes/class_object.html#class-object-method-notification).
0 commit comments