Differences

This shows you the differences between two versions of the page.

--- notes:fall2024:projects:cgfx [2024/10/09 23:50] – [RMSTACK] jmerri10
+++ notes:fall2024:projects:cgfx [2024/10/23 15:56] (current) – [Cursor] gsalce
@@ Line 36: / Line 36: @@
 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 <code>myStack = rmstack(myStack)</code> when the time comes.
 ====POP====
 <code>Stack *pop (Stack *, Node **);</code>
@@ Line 89: / Line 90: @@
 Keep in mind that when you "make" a Stacklist, you will want to have the ability to rm / clear a stacklist later on down the line.
+====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, a mouse is required for the simplest form of transitioning the cards. However, Vircon32 does not currently have mouse functionality, so one must get creative.
+There are a couple schools of thought on how to implement this movement into your game:
+) 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.
+) 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.

Lab46 Wiki

User Tools

Site Tools

Differences

Page Tools