aboutsummaryrefslogtreecommitdiff
path: root/engines/director
AgeCommit message (Collapse)Author
2017-08-11DIRECTOR: Lingo: Add missing break statementEugene Sandulenko
2017-08-02DIRECTOR: Fix GCC Compiler Warnings.D G Turner
2017-08-01DIRECTOR: Clarified STXT field namesEugene Sandulenko
2017-07-05DIRECTOR: Make 3-ary processEvent privateTobia Tesan
2017-07-05DIRECTOR: Handle kEventPrepareMovie with 1-ary processEventTobia Tesan
2017-07-05DIRECTOR: Handle kEventExitFrame with 1-ary processEventTobia Tesan
2017-07-05DIRECTOR: Handle kEventNone with 1-ary processEventTobia Tesan
2017-07-05DIRECTOR: Handle kEventIdle with 1-ary processEventTobia Tesan
2017-07-05DIRECTOR: Add processSpriteEventTobia Tesan
2017-07-05DIRECTOR: Move executeImmediateScripts to lingo.cppTobia Tesan
2017-07-05DIRECTOR: Include director/frame.h and sprite.h in lingo.cppTobia Tesan
2017-07-05DIRECTOR: Move #define CHANNEL_COUNT to director.hTobia Tesan
2017-07-05DIRECTOR: Use 1-ary processEvent call to start movieTobia Tesan
Perahsp a specialized Lingo::start() would be better for clarity for this single one?
2017-07-05DIRECTOR: Add kEventStart case for processGenericEventTobia Tesan
2017-07-05DIRECTOR: Remove "primary event handler" commentTobia Tesan
According to D4 manual only mouse/key/timeout event can have primary handler
2017-07-05DIRECTOR: Handle keyDown in 1-ary processEventTobia Tesan
Might change semantics by calling the standard chain for input events. That is what the D4 docs suggest anyway.
2017-07-05DIRECTOR: Add kFrameScript callTobia Tesan
This follows from D4 docs. Changes semantics, *might* break stuff.
2017-07-05DIRECTOR: Reorder processInputEventTobia Tesan
2017-07-05DIRECTOR: Swap order of processEvent callsTobia Tesan
This appears to be the correct order from docs and makes code easier to reorder. *Might* break stuff though.
2017-07-05DIRECTOR: Call primaryEventHandler in processInputEventTobia Tesan
2017-07-05DIRECTOR: Handle kEventPrepareFrame in processFrameEventTobia Tesan
2017-07-05DIRECTOR: Move kEventMouseUp/Down handling to processInputEventTobia Tesan
2017-07-05DIRECTOR: Include sprite.h in lingo-events.cppTobia Tesan
2017-07-05DIRECTOR: Handle frame enter/exit with 1-ary processEvent callTobia Tesan
2017-07-05DIRECTOR: Implement processFrameEventTobia Tesan
2017-07-05DIRECTOR: Add runMovieScriptTobia Tesan
2017-07-05DIRECTOR: Add Lingo::PrimaryEventHandlerTobia Tesan
2017-07-05DIRECTOR: Include frame.h in lingo-events.cppTobia Tesan
2017-07-05DIRECTOR: Add Lingo::_dontPassEventTobia Tesan
I'm not sure whether this should go here or in Director. I'm leaving it here because _dontPassEvent changes the semantics of event handling.
2017-05-02DIRECTOR: Fix code formattingEugene Sandulenko
2017-05-02DIRECTOR: Reduce header dependencyEugene Sandulenko
2017-05-02DIRECTOR: Fix #include pathsEugene Sandulenko
2017-05-02DIRECTOR: Use CachedMacText for renderingTobia Tesan
2017-05-02DIRECTOR: Add CachedMacText to TextCastTobia Tesan
2017-05-02DIRECTOR: Add CachedMacTextTobia Tesan
2017-05-02DIRECTOR: Add TextCast::importStxtTobia Tesan
2017-05-02DIRECTOR: Remove now-useless textId parameter from renderButtonTobia Tesan
2017-05-02DIRECTOR: Use text from textCastsTobia Tesan
2017-05-02DIRECTOR: Init textCasts with Stxts in ScoreTobia Tesan
2017-05-02DIRECTOR: Equip textCast with _ftextTobia Tesan
2017-05-02GRAPHICS: Pass interlinear as constructor argument to MacTextTobia Tesan
2017-05-02DIRECTOR: Add stxt.cppTobia Tesan
2017-05-02DIRECTOR: Delete Stxts in ~ScoreTobia Tesan
2017-05-02DIRECTOR: Use preloaded Stxt for renderingTobia Tesan
2017-05-02DIRECTOR: Preload Stxts in ScoreTobia Tesan
2017-05-02DIRECTOR: Add _loadedStxts member to ScoreTobia Tesan
2017-05-02DIRECTOR: Add Stxt.hTobia Tesan
2017-04-30DIRECTOR: clean up renderText: separate reading & actual renderingTobia Tesan
2017-04-30DIRECTOR: remove redundant/ineffective assignments to widthTobia Tesan
2017-04-30DIRECTOR: clean up renderText: move warning block downTobia Tesan
This changes slightly the semantics of the method; however, I assume we want to print (or not) the warning based on the width/height values that will in fact be used *in* the method.