49
edits
Changes
Jump to navigation
Jump to search
Line 19:
Line 19: − + Line 25:
Line 25: +
→Possible issues
*<del>Use wiimote IR input with a default cursor</del> Will just need to use functions that check against info obtained from IR.
*<del>Use wiimote IR input with a default cursor</del> Will just need to use functions that check against info obtained from IR.
===Possible issues===
===Possible issues===
*I can't think of an easy way to allow a mix of text AND images over buttons on the menu. Unless maybe an "icon" class with an overloaded constructor?
*I can't think of an easy way to allow a mix of text AND images over buttons on the menu. <del>Unless maybe an "icon" class with an overloaded constructor?</del> Roll that all into Button that can have text and icon at the same time, and if it's missing one, assign a null image or something.
*The menu, buttons and all will have to sit in a LayerManager, but LayerManager has no visible option, so where do we put the Menu when not in use? Or is it better to discard the menu from memory and rebuild later? Will look into how this is done on other software. Each menu/function can sit in its own LayerManager and be shoved offscreen when needed.
*The menu, buttons and all will have to sit in a LayerManager, but LayerManager has no visible option, so where do we put the Menu when not in use? Or is it better to discard the menu from memory and rebuild later? Will look into how this is done on other software. Each menu/function can sit in its own LayerManager and be shoved offscreen when needed.
*When allowing some other function to access video that does not use libwiisprite (say an emulator) then how do we make sure the path is clear, so to speak?
*When allowing some other function to access video that does not use libwiisprite (say an emulator) then how do we make sure the path is clear, so to speak?
*I've forgotten how to deal with passing arrays and dealing with their sizes. That's why I have reference books though.
*I've forgotten how to deal with passing arrays and dealing with their sizes. That's why I have reference books though.
*I'm starting to think I might want to use vectors or another data structure if it's going to allow adding and removing buttons.
*I'm starting to think I might want to use vectors or another data structure if it's going to allow adding and removing buttons.
==Class Member Function Outline==
==Class Member Function Outline==
===Menu===
===Menu===