notes:fall2024:projects:cgfx
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| notes:fall2024:projects:cgfx [2024/10/09 22:30] – [POP] gsalce | notes:fall2024:projects:cgfx [2024/10/23 15:56] (current) – [Cursor] gsalce | ||
|---|---|---|---|
| Line 34: | Line 34: | ||
| The reason behind handling your list is that you have a stack built upon a list, if you don't want a stack why do you want a list? | The reason behind handling your list is that you have a stack built upon a list, if you don't want a stack why do you want a list? | ||
| + | The purpose of a rmstack() function is to clear up and deallocate a stack. If you do not remove your stack at the end of the game, the stack elements (card nodes) will not be freed. Over time, the program will allocate more memory without freeing the previously allocated memory, which will lead to memory leak. | ||
| + | |||
| + | Remember too that you are returning a stack pointer when you call your function so you will want to set < | ||
| ====POP==== | ====POP==== | ||
| < | < | ||
| Line 42: | Line 45: | ||
| - | If you are using a quantity counter in your List, it would not be a bad idea to have it decrease | + | If you are using a quantity counter in your List, it would not be a bad idea to have it decrease |
| ====PUSH==== | ====PUSH==== | ||
| < | < | ||
| Line 48: | Line 51: | ||
| Whether you need to use insert() or append() as long as it is appropriately adding to the top of your stack you'll be fine\\ | Whether you need to use insert() or append() as long as it is appropriately adding to the top of your stack you'll be fine\\ | ||
| Of course reassign myStack-> | Of course reassign myStack-> | ||
| + | |||
| + | If you are using a quantity counter in your List, it would not be a bad idea to have it increase as part of append / insert as well. | ||
| + | |||
| ====Stacklist==== | ====Stacklist==== | ||
| Line 84: | Line 90: | ||
| Keep in mind that when you " | Keep in mind that when you " | ||
| + | |||
| + | ====Cursor==== | ||
| + | |||
| + | FreeCell is a game that requires fluent movement for the cards between the original free cells, and the cells that will become available as the game progresses. | ||
| + | |||
| + | Traditionally, | ||
| + | |||
| + | There are a couple schools of thought on how to implement this movement into your game: | ||
| + | |||
| + | 1) You could implement a pointer arrow (or a couple) to represent which stack the player is currently looking at. Then, assign keybinds to have the cards go to a certain cell / stack. Vircon32 has more than enough buttons to accomplish this goal. | ||
| + | |||
| + | 2) You could introduce new movement patterns to the link list, so that the player may move up / down / left / right to move particular sets of cards at a time. | ||
notes/fall2024/projects/cgfx.1728513050.txt.gz · Last modified: 2024/10/09 22:30 by gsalce
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
