約 2,724,527 件
https://w.atwiki.jp/utauuuta/pages/3994.html
【登録タグ A collt（ですか） 曲 楓歌コト】 作詞：collt（ですか） 作曲：collt（ですか） 唄：楓歌コト 曲紹介 ハイヨー ハイヨー 愛鳥週間2014参加楽曲 日々日々歴史を駆け抜ける 歌詞 （動画歌詞より転載） ハイヨー ハイヨー 空論の街で 見据えた明日は とうに過ぎた ハイヨー ハイヨー 空想の城で 栄えた国は とうに消えた 回る回る時に空回る空の 雲の無常だけがキミを知る ハイヨー ハイヨー 空欄の履歴 希望の未来 とうに過ぎた ハイヨー ハイヨー「空虚の日々へ」と 迎えた夜は とうに超えた 回る回る命 空回る夢の 欠片無情に湧きキミを連れ Allegroで走る様に 過ぎて行く時に挟まれて Allegroで縺れる様に 諸共に 諸共に 果てへ ハイヨー ハイヨー 空走のlagに 集うあの日は とうに過ぎた ハイヨー ハイヨー 空説のlogを 辿るあの日は とうに消えた 回る回る日々に空回る針の 今日は霧状に散りキミは消え Allegroで走る様に 過ぎて行く時に挟まれて Allegroで縺れる様に 諸共に 諸共に Allegroで走る様に 過ぎて行く時に挟まれて Allegroで縺れる様に 諸共に 諸共に 果てへ コメント 名前 コメント
https://w.atwiki.jp/nenyaffle/pages/31.html
クラブ設立：07/07/13 エンブレム：07/08/05 2010.秋 ついに事実上の崩壊をむかえた 以下、過去の栄光（笑 猫鯖を代表する要塞クラブとして07年後半から長期に渡り要塞戦を続けてきた。 レベル・装備・人数どれも高水準で、侵攻・防衛ともに安定していた。現在は過疎化が進み戦力は未知数。 晒しにおけるアレグロテンプレのキャッチコピーは、不正、キモオタ、廃人、引き抜き、2ch張り付き、妖怪、直結厨、などなど実に多様であった。 友好クラブはLicenza ～最近の要塞戦績～ 09/04/19 カルデア要塞に侵攻。ODYSSEYを攻め落とす。以降連続防衛2回。 09/04/30 ODYSSEYに敗北。 09/06/02 アミティス要塞に侵攻。Skyscraperを3分で攻め落とす。以降連続防衛6回。 09/06/27 要塞クラブの連合軍と化していた松本人志を相手に敗北。 09/07/23 カルデア要塞に侵攻。Devilockを5分で攻め落とす。以降長期防衛。 09/09/06 傭兵多数で攻め込んだ乱ーRUNーに敗北。 その後は要塞戦を行う様子が見られない。 クラブ会議（笑）で要塞が話題になっているが、どうやら過疎が原因で侵攻できる状況にないらしい。 ☆AlleGroメンバー規約☆ 掟１、挨拶は元気よく！ 掟２、横・詐欺などの迷惑行為禁止 掟３、Pkは自己責任で 掟４、敬語はなるべく使わない 掟５、敬語を使ったら呼称覚悟 掟６、サブの育成はご自由に 掟７、キャラの入れ替えもご相談してください 掟８、ただしそのキャラで他クラブの要塞には出ない 掟９、傭兵もだぁめ 掟10、キャラ要塞は参加おｋ 掟11、ただしAlleGro要塞占拠時・申請時は他要塞にでること禁止 掟12、イベント要塞も禁止 掟13、無言で1ヶ月以上ログインしない人は蹴ります （クラブHPより） クラブHPでは、メンバー表や要塞戦績も掲載されている。
https://w.atwiki.jp/sdvx/pages/11191.html
Allegro Saetta/ 天束 vs. siromaru 「BEMANI PRO LEAGUE -SEASON 3-」チーム「GAME PANIC」のイメージミュージック Lv CHAIN 譜面属性 BPM TIME Version Genre Illustrator Effect NOVICE 07 182 EG95 FLOOR minoru 脈力木魚 ADVANCED 14 EXHAUST 17 1600 MAXIMUM 19 1995 + 難易度投票 NOVICE 選択肢 投票数 投票 詐称 0 強 0 中 0 弱 0 逆詐称 0 ADVANCED 選択肢 投票数 投票 詐称 0 強 0 中 0 弱 0 逆詐称 0 EXHAUST 選択肢 投票数 投票 詐称 0 強 0 中 0 弱 0 逆詐称 0 MAXIMUM 選択肢 投票数 投票 詐称 0 強 0 中 0 弱 0 逆詐称 0 攻略・解説 譜面・楽曲の攻略についてはこちらへどうぞ 見辛さ解消の為に改行や文頭の編集、不適切なコメントを削除することがあります 名前 コメント ※文頭に[ bgcolor(#aaf){NOV}]、[ bgcolor(#ffa){ADV}]、[ bgcolor(#faa){EXH}]、[ bgcolor(#888){MXM}]をコピー ペーストすると見やすくなります コメント 楽曲やイラストなどのコメントについてはこちらへどうぞ 名前 コメント すべてのコメントを見る
https://w.atwiki.jp/chikugogawa/pages/99.html
まず楽譜を確認してみると、同じAllegro leggieroで始まっていて、ピアノパートに関しては冒頭の３小節目からの譜面と、ここからの動きは16小節間にわたって「しぜんにそだてられた」まで完全に一致。調もスタッカートもテヌートもクレシェンド、デクレシェンドも。ただ違うのは音量が冒頭はｐで始まるのにここではｆ。そして冒頭はベースが歌に参加するところで音量をｍｆに２ランクアップさせるのにここでは変化の指示なし。 合唱の音型は、冒頭で合いの手だった「ラララ」。だけどよくよく見てみると、冒頭でラララを歌うタイミングをピアノパートとの関係で見てみると２小節ずれている。完全に一致しているのは冒頭からではなくて冒頭の３小節目からだから。とはいえ収まりよく作曲されているので、ずれていることをことさらに意識する必要はないでしょう。 とりあえずピアニストさまにはぼーっと歌っている合唱団員にも明らかに違いが分からせるような冒頭のｐとここのｆの差を演じ分けてもらいたいなぁって思います。右手しかない楽譜でしかもこのテンポ。つぶが揃ったスタッカートを、躍動感や昂揚感のあるｐと、さらなる期待感を孕みつつも問題解決と若い愛に満ちたｆとに演じ分けることって、そう簡単なことではないと思いますが。 全く個人的な嗜好ですが、こういうもとの音楽が発展して戻ってくる形式って大好きです。かつて主旋律だった音楽を合唱以外が奏でていて、そこに全く新しい音楽を後ろから重ねていく様なところ。ブラームスのドイツレクイエムにあるバイオリンにwie lieblich sind の旋律を任せて合唱が低くwohl denenと入ってくるところとか。
https://w.atwiki.jp/niconamadqrta/pages/183.html
【コミュニティ】 Allegroの気ままに放送 http //com.nicovideo.jp/community/co1235709 【記録】 【大会実績】 【関連】
https://w.atwiki.jp/allegro_jp/pages/14.html
Event system and events * ALLEGRO_EVENT o ALLEGRO_EVENT_JOYSTICK_AXIS o ALLEGRO_EVENT_JOYSTICK_BUTTON_DOWN o ALLEGRO_EVENT_JOYSTICK_BUTTON_UP o ALLEGRO_EVENT_JOYSTICK_CONFIGURATION o ALLEGRO_EVENT_KEY_DOWN o ALLEGRO_EVENT_KEY_UP o ALLEGRO_EVENT_KEY_CHAR o ALLEGRO_EVENT_MOUSE_AXES o ALLEGRO_EVENT_MOUSE_BUTTON_DOWN o ALLEGRO_EVENT_MOUSE_BUTTON_UP o ALLEGRO_EVENT_MOUSE_WARPED o ALLEGRO_EVENT_MOUSE_ENTER_DISPLAY o ALLEGRO_EVENT_MOUSE_LEAVE_DISPLAY o ALLEGRO_EVENT_TIMER o ALLEGRO_EVENT_DISPLAY_EXPOSE o ALLEGRO_EVENT_DISPLAY_RESIZE o ALLEGRO_EVENT_DISPLAY_CLOSE o ALLEGRO_EVENT_DISPLAY_LOST o ALLEGRO_EVENT_DISPLAY_FOUND o ALLEGRO_EVENT_DISPLAY_SWITCH_OUT o ALLEGRO_EVENT_DISPLAY_SWITCH_IN o ALLEGRO_EVENT_DISPLAY_ORIENTATION * ALLEGRO_USER_EVENT * ALLEGRO_EVENT_QUEUE * ALLEGRO_EVENT_SOURCE * ALLEGRO_EVENT_TYPE * ALLEGRO_GET_EVENT_TYPE * ALLEGRO_EVENT_TYPE_IS_USER * al_create_event_queue * al_destroy_event_queue * al_register_event_source * al_unregister_event_source * al_is_event_queue_empty * al_get_next_event * al_peek_next_event * al_drop_next_event * al_flush_event_queue * al_wait_for_event * al_wait_for_event_timed * al_wait_for_event_until * al_init_user_event_source * al_destroy_user_event_source * al_emit_user_event * al_unref_user_event * al_get_event_source_data * al_set_event_source_data These functions are declared in the main Allegro header file allegro5/allegro.h ALLEGRO_EVENT typedef union ALLEGRO_EVENT ALLEGRO_EVENT; An ALLEGRO_EVENT is a union of all builtin event structures, i.e. it is an object large enough to hold the data of any event type. All events have the following fields in common type (ALLEGRO_EVENT_TYPE) Indicates the type of event. any.source (ALLEGRO_EVENT_SOURCE *) The event source which generated the event. any.timestamp (double) When the event was generated. By examining the type field you can then access type-specific fields. The any.source field tells you which event source generated that particular event. The any.timestamp field tells you when the event was generated. The time is referenced to the same starting point as al_get_time. Each event is of one of the following types, with the usable fields given. ALLEGRO_EVENT_JOYSTICK_AXIS A joystick axis value changed. joystick.id (ALLEGRO_JOYSTICK *) The joystick which generated the event. This is not the same as the event source joystick.source. joystick.stick (int) The stick number, counting from zero. Axes on a joystick are grouped into "sticks". joystick.axis (int) The axis number on the stick, counting from zero. joystick.pos (float) The axis position, from -1.0 to +1.0. ALLEGRO_EVENT_JOYSTICK_BUTTON_DOWN A joystick button was pressed. joystick.id (ALLEGRO_JOYSTICK *) The joystick which generated the event. joystick.button (int) The button which was pressed, counting from zero. ALLEGRO_EVENT_JOYSTICK_BUTTON_UP A joystick button was released. joystick.id (ALLEGRO_JOYSTICK *) The joystick which generated the event. joystick.button (int) The button which was released, counting from zero. ALLEGRO_EVENT_JOYSTICK_CONFIGURATION A joystick was plugged in or unplugged. See al_reconfigure_joysticks for details. ALLEGRO_EVENT_KEY_DOWN A keyboard key was pressed. keyboard.keycode (int) The code corresponding to the physical key which was pressed. See the "Key codes" section for the list of ALLEGRO_KEY_* constants. keyboard.display (ALLEGRO_DISPLAY *) The display which had keyboard focus when the event occurred. Note this event is about the physical keys being press on the keyboard. Look for ALLEGRO_EVENT_KEY_CHAR events for character input. ALLEGRO_EVENT_KEY_UP A keyboard key was released. keyboard.keycode (int) The code corresponding to the physical key which was released. See the "Key codes" section for the list of ALLEGRO_KEY_* constants. keyboard.display (ALLEGRO_DISPLAY *) The display which had keyboard focus when the event occurred. ALLEGRO_EVENT_KEY_CHAR A character was typed on the keyboard, or a character was auto-repeated. keyboard.keycode (int) The code corresponding to the physical key which was last pressed. See the "Key codes" section for the list of ALLEGRO_KEY_* constants. keyboard.unichar (int) A Unicode code point (character). This may be zero or negative if the event was generated for a non-visible "character", such as an arrow or Function key. In that case you can act upon the keycode field. Some special keys will set the unichar field to their standard ASCII values Tab=9, Return=13, Escape=27. In addition if you press the Control key together with A to Z the unichar field will have the values 1 to 26. For example Ctrl-A will set unichar to 1 and Ctrl-H will set it to 8. As of Allegro 5.0.2 there are some inconsistencies in the treatment of Backspace (8 or 127) and Delete (127 or 0) keys on different platforms. These can be worked around by checking the keycode field. keyboard.modifiers (unsigned) This is a bitfield of the modifier keys which were pressed when the event occurred. See "Keyboard modifier flags" for the constants. keyboard.repeat (bool) Indicates if this is a repeated character. keyboard.display (ALLEGRO_DISPLAY *) The display which had keyboard focus when the event occurred. Note in many input methods, characters are not entered one-for-one with physical key presses. Multiple key presses can combine to generate a single character, e.g. apostrophe + e may produce é . Fewer key presses can also generate more characters, e.g. macro sequences expanding to common phrases. ALLEGRO_EVENT_MOUSE_AXES One or more mouse axis values changed. mouse.x (int) x-coordinate mouse.y (int) y-coordinate mouse.z (int) z-coordinate. This usually means the vertical axis of a mouse wheel, where up is positive and down is negative. mouse.w (int) w-coordinate. This usually means the horizontal axis of a mouse wheel. mouse.dx (int) Change in the x-coordinate value since the previous ALLEGRO_EVENT_MOUSE_AXES event. mouse.dy (int) Change in the y-coordinate value since the previous ALLEGRO_EVENT_MOUSE_AXES event. mouse.dz (int) Change in the z-coordinate value since the previous ALLEGRO_EVENT_MOUSE_AXES event. mouse.dw (int) Change in the w-coordinate value since the previous ALLEGRO_EVENT_MOUSE_AXES event. mouse.display (ALLEGRO_DISPLAY *) The display which had mouse focus. Note Calling al_set_mouse_xy also will result in a change of axis values, but such a change is reported with ALLEGRO_EVENT_MOUSE_WARPED events instead. Note currently mouse.display may be NULL if an event is generated in response to al_set_mouse_axis. ALLEGRO_EVENT_MOUSE_BUTTON_DOWN A mouse button was pressed. mouse.x (int) x-coordinate mouse.y (int) y-coordinate mouse.z (int) z-coordinate mouse.w (int) w-coordinate mouse.button (unsigned) The mouse button which was pressed, numbering from 1. mouse.display (ALLEGRO_DISPLAY *) The display which had mouse focus. ALLEGRO_EVENT_MOUSE_BUTTON_UP A mouse button was released. mouse.x (int) x-coordinate mouse.y (int) y-coordinate mouse.z (int) z-coordinate mouse.w (int) w-coordinate mouse.button (unsigned) The mouse button which was released, numbering from 1. mouse.display (ALLEGRO_DISPLAY *) The display which had mouse focus. ALLEGRO_EVENT_MOUSE_WARPED al_set_mouse_xy was called to move the mouse. This event is identical to ALLEGRO_EVENT_MOUSE_AXES otherwise. ALLEGRO_EVENT_MOUSE_ENTER_DISPLAY The mouse cursor entered a window opened by the program. mouse.x (int) x-coordinate mouse.y (int) y-coordinate mouse.z (int) z-coordinate mouse.w (int) w-coordinate mouse.display (ALLEGRO_DISPLAY *) The display which had mouse focus. ALLEGRO_EVENT_MOUSE_LEAVE_DISPLAY The mouse cursor leave the boundaries of a window opened by the program. mouse.x (int) x-coordinate mouse.y (int) y-coordinate mouse.z (int) z-coordinate mouse.w (int) w-coordinate mouse.display (ALLEGRO_DISPLAY *) The display which had mouse focus. ALLEGRO_EVENT_TIMER A timer counter incremented. timer.source (ALLEGRO_TIMER *) The timer which generated the event. timer.count (int64_t) The timer count value. ALLEGRO_EVENT_DISPLAY_EXPOSE The display (or a portion thereof) has become visible. display.source (ALLEGRO_DISPLAY *) The display which was exposed. display.x (int) display.y (int) The top-left corner of the display which was exposed. display.width (int) display.height (int) The width and height of the rectangle which was exposed. Note The display needs to be created with ALLEGRO_GENERATE_EXPOSE_EVENTS flag for these events to be generated. ALLEGRO_EVENT_DISPLAY_RESIZE The window has been resized. display.source (ALLEGRO_DISPLAY *) The display which was resized. display.x (int) display.y (int) The position of the top-level corner of the display. display.width (int) The new width of the display. display.height (int) The new height of the display. Note that further resize events may be generated by the time you process the event, so these fields may hold outdated information. ALLEGRO_EVENT_DISPLAY_CLOSE The close button of the window has been pressed. display.source (ALLEGRO_DISPLAY *) The display which was closed. ALLEGRO_EVENT_DISPLAY_LOST When using Direct3D, displays can enter a "lost" state. In that state, drawing calls are ignored, and upon entering the state, bitmap s pixel data can become undefined. Allegro does its best to preserve the correct contents of bitmaps (see ALLEGRO_NO_PRESERVE_TEXTURE) and restore them when the device is "found" (see ALLEGRO_EVENT_DISPLAY_FOUND). However, this is not 100% fool proof. To ensure that all bitmap contents are restored accurately, one must take additional steps. The best procedure to follow if bitmap constancy is important to you is as follows first, always have the ALLEGRO_NO_PRESERVE_TEXTURE flag set to true when creating bitmaps, as it incurs pointless overhead when using this method. Second, create a mechanism in your game for easily reloading all of your bitmaps -- for example, wrap them in a class or data structure and have a "bitmap manager" that can reload them back to the desired state. Then, when you receive an ALLEGRO_EVENT_DISPLAY_FOUND event, tell the bitmap manager (or whatever your mechanism is) to restore your bitmaps. display.source (ALLEGRO_DISPLAY *) The display which was lost. ALLEGRO_EVENT_DISPLAY_FOUND Generated when a lost device is restored to operating state. See ALLEGRO_EVENT_DISPLAY_LOST. display.source (ALLEGRO_DISPLAY *) The display which was found. ALLEGRO_EVENT_DISPLAY_SWITCH_OUT The window is no longer active, that is the user might have clicked into another window or "tabbed" away. display.source (ALLEGRO_DISPLAY *) The display which was switched out of. ALLEGRO_EVENT_DISPLAY_SWITCH_IN The window is the active one again. display.source (ALLEGRO_DISPLAY *) The display which was switched into. ALLEGRO_EVENT_DISPLAY_ORIENTATION Generated when the rotation or orientation of a display changes. display.source (ALLEGRO_DISPLAY *) The display which generated the event. event.display.orientation Contains one of the following values * ALLEGRO_DISPLAY_ORIENTATION_0_DEGREES * ALLEGRO_DISPLAY_ORIENTATION_90_DEGREES * ALLEGRO_DISPLAY_ORIENTATION_180_DEGREES * ALLEGRO_DISPLAY_ORIENTATION_270_DEGREES * ALLEGRO_DISPLAY_ORIENTATION_FACE_UP * ALLEGRO_DISPLAY_ORIENTATION_FACE_DOWN See also ALLEGRO_EVENT_SOURCE, ALLEGRO_EVENT_TYPE, ALLEGRO_USER_EVENT ALLEGRO_USER_EVENT typedef struct ALLEGRO_USER_EVENT ALLEGRO_USER_EVENT; An event structure that can be emitted by user event sources. These are the public fields * ALLEGRO_EVENT_SOURCE *source; * intptr_t data1; * intptr_t data2; * intptr_t data3; * intptr_t data4; See also al_emit_user_event ALLEGRO_EVENT_QUEUE typedef struct ALLEGRO_EVENT_QUEUE ALLEGRO_EVENT_QUEUE; An event queue holds events that have been generated by event sources that are registered with the queue. Events are stored in the order they are generated. Access is in a strictly FIFO (first-in-first-out) order. See also al_create_event_queue, al_destroy_event_queue ALLEGRO_EVENT_SOURCE typedef struct ALLEGRO_EVENT_SOURCE ALLEGRO_EVENT_SOURCE; An event source is any object which can generate events. For example, an ALLEGRO_DISPLAY can generate events, and you can get the ALLEGRO_EVENT_SOURCE pointer from an ALLEGRO_DISPLAY with al_get_display_event_source. You may create your own "user" event sources that emit custom events. See also ALLEGRO_EVENT, al_init_user_event_source, al_emit_user_event ALLEGRO_EVENT_TYPE typedef unsigned int ALLEGRO_EVENT_TYPE; An integer used to distinguish between different types of events. See also ALLEGRO_EVENT, ALLEGRO_GET_EVENT_TYPE, ALLEGRO_EVENT_TYPE_IS_USER ALLEGRO_GET_EVENT_TYPE #define ALLEGRO_GET_EVENT_TYPE(a, b, c, d) AL_ID(a, b, c, d) Make an event type identifier, which is a 32-bit integer. Usually, but not necessarily, this will be made from four 8-bit character codes, for example #define MY_EVENT_TYPE ALLEGRO_GET_EVENT_TYPE( M , I , N , E ) IDs less than 1024 are reserved for Allegro or its addons. Don t use anything lower than ALLEGRO_GET_EVENT_TYPE(0, 0, 4, 0). You should try to make your IDs unique so they don t clash with any 3rd party code you may be using. Be creative. Numbering from 1024 is not creative. If you need multiple identifiers, you could define them like this #define BASE_EVENT ALLEGRO_GET_EVENT_TYPE( M , I , N , E ) #define BARK_EVENT (BASE_EVENT + 0) #define MEOW_EVENT (BASE_EVENT + 1) #define SQUAWK_EVENT (BASE_EVENT + 2) /* Alternatively */ enum { BARK_EVENT = ALLEGRO_GET_EVENT_TYPE( M , I , N , E ), MEOW_EVENT, SQUAWK_EVENT }; See also ALLEGRO_EVENT, ALLEGRO_EVENT_TYPE_IS_USER ALLEGRO_EVENT_TYPE_IS_USER #define ALLEGRO_EVENT_TYPE_IS_USER(t) ((t) = 512) A macro which evaluates to true if the event type is not a builtin event type, i.e. one of those described in ALLEGRO_EVENT_TYPE. al_create_event_queue ALLEGRO_EVENT_QUEUE *al_create_event_queue(void) Create a new, empty event queue, returning a pointer to object if successful. Returns NULL on error. See also al_register_event_source, al_destroy_event_queue, ALLEGRO_EVENT_QUEUE al_destroy_event_queue void al_destroy_event_queue(ALLEGRO_EVENT_QUEUE *queue) Destroy the event queue specified. All event sources currently registered with the queue will be automatically unregistered before the queue is destroyed. See also al_create_event_queue, ALLEGRO_EVENT_QUEUE al_register_event_source void al_register_event_source(ALLEGRO_EVENT_QUEUE *queue, ALLEGRO_EVENT_SOURCE *source) Register the event source with the event queue specified. An event source may be registered with any number of event queues simultaneously, or none. Trying to register an event source with the same event queue more than once does nothing. See also al_unregister_event_source, ALLEGRO_EVENT_SOURCE al_unregister_event_source void al_unregister_event_source(ALLEGRO_EVENT_QUEUE *queue, ALLEGRO_EVENT_SOURCE *source) Unregister an event source with an event queue. If the event source is not actually registered with the event queue, nothing happens. If the queue had any events in it which originated from the event source, they will no longer be in the queue after this call. See also al_register_event_source al_is_event_queue_empty bool al_is_event_queue_empty(ALLEGRO_EVENT_QUEUE *queue) Return true if the event queue specified is currently empty. See also al_get_next_event, al_peek_next_event al_get_next_event bool al_get_next_event(ALLEGRO_EVENT_QUEUE *queue, ALLEGRO_EVENT *ret_event) Take the next event out of the event queue specified, and copy the contents into ret_event, returning true. The original event will be removed from the queue. If the event queue is empty, return false and the contents of ret_event are unspecified. See also ALLEGRO_EVENT, al_peek_next_event, al_wait_for_event al_peek_next_event bool al_peek_next_event(ALLEGRO_EVENT_QUEUE *queue, ALLEGRO_EVENT *ret_event) Copy the contents of the next event in the event queue specified into ret_event and return true. The original event packet will remain at the head of the queue. If the event queue is actually empty, this function returns false and the contents of ret_event are unspecified. See also ALLEGRO_EVENT, al_get_next_event, al_drop_next_event al_drop_next_event bool al_drop_next_event(ALLEGRO_EVENT_QUEUE *queue) Drop (remove) the next event from the queue. If the queue is empty, nothing happens. Returns true if an event was dropped. See also al_flush_event_queue, al_is_event_queue_empty al_flush_event_queue void al_flush_event_queue(ALLEGRO_EVENT_QUEUE *queue) Drops all events, if any, from the queue. See also al_drop_next_event, al_is_event_queue_empty al_wait_for_event void al_wait_for_event(ALLEGRO_EVENT_QUEUE *queue, ALLEGRO_EVENT *ret_event) Wait until the event queue specified is non-empty. If ret_event is not NULL, the first event in the queue will be copied into ret_event and removed from the queue. If ret_event is NULL the first event is left at the head of the queue. See also ALLEGRO_EVENT, al_wait_for_event_timed, al_wait_for_event_until, al_get_next_event al_wait_for_event_timed bool al_wait_for_event_timed(ALLEGRO_EVENT_QUEUE *queue, ALLEGRO_EVENT *ret_event, float secs) Wait until the event queue specified is non-empty. If ret_event is not NULL, the first event in the queue will be copied into ret_event and removed from the queue. If ret_event is NULL the first event is left at the head of the queue. timeout_msecs determines approximately how many seconds to wait. If the call times out, false is returned. Otherwise true is returned. See also ALLEGRO_EVENT, al_wait_for_event, al_wait_for_event_until al_wait_for_event_until bool al_wait_for_event_until(ALLEGRO_EVENT_QUEUE *queue, ALLEGRO_EVENT *ret_event, ALLEGRO_TIMEOUT *timeout) Wait until the event queue specified is non-empty. If ret_event is not NULL, the first event in the queue will be copied into ret_event and removed from the queue. If ret_event is NULL the first event is left at the head of the queue. timeout determines how long to wait. If the call times out, false is returned. Otherwise true is returned. See also ALLEGRO_EVENT, ALLEGRO_TIMEOUT, al_init_timeout, al_wait_for_event, al_wait_for_event_timed al_init_user_event_source void al_init_user_event_source(ALLEGRO_EVENT_SOURCE *src) Initialise an event source for emitting user events. The space for the event source must already have been allocated. One possible way of creating custom event sources is to derive other structures with ALLEGRO_EVENT_SOURCE at the head, e.g. typedef struct THING THING; struct THING { ALLEGRO_EVENT_SOURCE event_source; int field1; int field2; /* etc. */ }; THING *create_thing(void) { THING *thing = malloc(sizeof(THING)); if (thing) { al_init_user_event_source( thing- event_source); thing- field1 = 0; thing- field2 = 0; } return thing; } The advantage here is that the THING pointer will be the same as the ALLEGRO_EVENT_SOURCE pointer. Events emitted by the event source will have the event source pointer as the source field, from which you can get a pointer to a THING by a simple cast (after ensuring checking the event is of the correct type). However, it is only one technique and you are not obliged to use it. The user event source will never be destroyed automatically. You must destroy it manually with al_destroy_user_event_source. See also ALLEGRO_EVENT_SOURCE, al_emit_user_event, al_destroy_user_event_source al_destroy_user_event_source void al_destroy_user_event_source(ALLEGRO_EVENT_SOURCE *src) Destroy an event source initialised with al_init_user_event_source. This does not free the memory, as that was user allocated to begin with. See also ALLEGRO_EVENT_SOURCE al_emit_user_event bool al_emit_user_event(ALLEGRO_EVENT_SOURCE *src, ALLEGRO_EVENT *event, void (*dtor)(ALLEGRO_USER_EVENT *)) Emit a user event. The event source must have been initialised with al_init_user_event_source. Returns false if the event source isn t registered with any queues, hence the event wouldn t have been delivered into any queues. Events are copied in and out of event queues, so after this function returns the memory pointed to by event may be freed or reused. Some fields of the event being passed in may be modified by the function. Reference counting will be performed if dtor is not NULL. Whenever a copy of the event is made, the reference count increases. You need to call al_unref_user_event to decrease the reference count once you are done a user event that you have received from al_get_next_event, al_peek_next_event, al_wait_for_event, etc. Once the reference count drops to zero dtor will be called with a copy of the event as an argument. It should free the resources associated with the event, but not the event itself (since it is just a copy). If dtor is NULL then reference counting will not be performed. It is safe, but unnecessary, to call al_unref_user_event on non-reference counted user events. See also ALLEGRO_USER_EVENT, al_unref_user_event al_unref_user_event void al_unref_user_event(ALLEGRO_USER_EVENT *event) Decrease the reference count of a user-defined event. This must be called on any user event that you get from al_get_next_event, al_peek_next_event, al_wait_for_event, etc. which is reference counted. This function does nothing if the event is not reference counted. See also al_emit_user_event al_get_event_source_data intptr_t al_get_event_source_data(const ALLEGRO_EVENT_SOURCE *source) Returns the abstract user data associated with the event source. If no data was previously set, returns NULL. See also al_set_event_source_data al_set_event_source_data void al_set_event_source_data(ALLEGRO_EVENT_SOURCE *source, intptr_t data) Assign the abstract user data to the event source. Allegro does not use the data internally for anything; it is simply meant as a convenient way to associate your own data or objects with events. See also al_get_event_source_data
https://w.atwiki.jp/allegro_jp/pages/13.html
Timer routines ALLEGRO_TIMER ALLEGRO_USECS_TO_SECS ALLEGRO_MSECS_TO_SECS ALLEGRO_BPS_TO_SECS ALLEGRO_BPM_TO_SECS al_create_timer al_start_timer al_stop_timer al_get_timer_started al_destroy_timer al_get_timer_count al_set_timer_count al_add_timer_count al_get_timer_speed al_set_timer_speed al_get_timer_event_source これらの関数はAllegroメインヘッダファイルで宣言されています。 #include allegro5/allegro.h ALLEGRO_TIMER タイマーオブジェクトを表す抽象型です。 typedef struct ALLEGRO_TIMER ALLEGRO_TIMER; ALLEGRO_USECS_TO_SECS マイクロ秒から秒に変換します。 #define ALLEGRO_USECS_TO_SECS(x) ((x) / 1000000.0) ALLEGRO_MSECS_TO_SECS ミリ秒から秒に変換します。 #define ALLEGRO_MSECS_TO_SECS(x) ((x) / 1000.0) ALLEGRO_BPS_TO_SECS BPSから秒に変換します。 #define ALLEGRO_BPS_TO_SECS(x) (1.0 / (x)) ALLEGRO_BPM_TO_SECS BPMから秒に変換します。 #define ALLEGRO_BPM_TO_SECS(x) (60.0 / (x)) al_create_timer 新しいタイマーをインストールします。成功した場合、新しいタイマーオブジェクトを返し、失敗した場合はNULLを返します。speed_secsは"tick"の発生間隔(秒)で、正の値でなければいけません。新しいタイマーは停止しています。この関数が呼び出される前に、システムのドライバがインストールされている必要があります。 ALLEGRO_TIMER* al_create_timer(double speed_secs) 使用上の注意：一般的な精度はマイクロ秒オーダーですが、いくつかのドライバの場合はミリ秒かもしれません。 関連項目 al_start_timer, al_destroy_timer al_start_timer 指定されたタイマーを開始します。タイマーのカウンターが一定速度でインクリメントされ、イベントの生成を開始します。既にタイマーが開始している場合、何も処理を行いません。 void al_start_timer(ALLEGRO_TIMER *timer) 関連項目 al_stop_timer, al_get_timer_started al_stop_timer 指定されたタイマーを停止します。タイマーのカウンターのインクリメントを停止し、イベントを生成を停止します。既にタイマーが停止している場合、何も処理を行いません。 void al_stop_timer(ALLEGRO_TIMER *timer) 関連項目 al_start_timer, al_get_timer_started al_get_timer_started 指定されたタイマーが開始された状態の場合、trueを返します。 bool al_get_timer_started(const ALLEGRO_TIMER *timer) al_destroy_timer 指定されたタイマーをアンインストールします。タイマーが開始されている場合は、アンインストール前に自動的に停止します。また、任意のイベントキューとタイマーを解除します。 NULLポインタが渡された場合は何も処理を行いません。 void al_destroy_timer(ALLEGRO_TIMER *timer) 関連項目 al_create_timer al_get_timer_count 指定されたタイマーのカウンター値を返します。指定するタイマーは開始済み、停止中のどちらでも利用可能です。 int64_t al_get_timer_count(const ALLEGRO_TIMER *timer) 関連項目 al_set_timer_count al_set_timer_count タイマーのカウンタの値を設定します。指定するタイマーは開始済み、停止中のどちらでも利用可能です。カウント値は、正または負の値が設定されますが、常に各刻みで1ずつインクリメントされます。 void al_set_timer_count(ALLEGRO_TIMER *timer, int64_t new_count) 関連項目 al_get_timer_count, al_add_timer_count al_add_timer_count void al_add_timer_count(ALLEGRO_TIMER *timer, int64_t diff) Add diff to the timer s counter value. This is similar to writing al_set_timer_count(timer, al_get_timer_count(timer) + diff); except that the addition is performed atomically, so no ticks will be lost. See also al_set_timer_count al_get_timer_speed double al_get_timer_speed(const ALLEGRO_TIMER *timer) Return the timer s speed, in seconds. See also al_set_timer_speed al_set_timer_speed void al_set_timer_speed(ALLEGRO_TIMER *timer, double new_speed_secs) Set the timer s speed, i.e. the rate at which its counter will be incremented when it is started. This can be done when the timer is started or stopped. If the timer is currently running, it is made to look as though the speed change occured precisely at the last tick. speed_secs has exactly the same meaning as with al_create_timer. See also al_get_timer_speed al_get_timer_event_source ALLEGRO_EVENT_SOURCE *al_get_timer_event_source(ALLEGRO_TIMER *timer) Retrieve the associated event source.
https://w.atwiki.jp/1007k/pages/676.html
Allegro Cantabile 攻略・詳細 AC10に収録 ★×5で、378コンボ。BPMは168 アーティストは SUEMITSU THE SUEMITH アニメ「のだめカンタービレ」のOP曲。 小節線に重なる音符が少ない。（この曲と同じ。） 「Allegro」という名の通りBPMが171と速めで16分混じりのフレーズが当たり前のように出て来ることから★×6で良いという声も多く初期からずっと★×5と★×6の差が希薄であることを感じさせる譜面の一つ。 読み方は、 アレグロ カンタービレ かんたん ふつう むずかしい コメント 譜面 風船の連打数、長さは適当です 10/3/22 BPMを167.9886
https://w.atwiki.jp/allegro_jp/pages/2.html
メニュー トップページ Allegro55.0timer events ここを編集
https://w.atwiki.jp/marukooz/pages/22.html
アレグロ・ダ・カーポ Allegro da Capo 別名ミュージッカー。ロバマチの近くの美しい丘の谷間に一人で住んでいる、小柄でぽっちゃりした男性。 胸の中にたくさんのリードが入っていて、呼吸をするたびに音楽を奏でる。ただしその音楽はあまり心地よいものではないらしい。しかし呼吸を止めることも出来ないので、彼に近よった人はその音楽に耐えなければならない。 アレグロ・ダ・カーポは、もちろん音楽用語の「アレグロ（快速に）」とダカーポ（曲頭から）」」を繋げたものだが、ずっと音楽を鳴らし続けている彼には、ふさわしい名前だろう。 初出作品：「オズへつづく道」