ID:161963
Mar 10 2008, 3:09 am
|
|
anyone know a quick,simple but efficient tutorial for skins other than the one provided by BYOND.that one is hard to understand...
|
Mar 10 2008, 9:36 am
|
|
Where are you getting stuck in the tutorial?
|
In response to Traztx
|
|
usually the part about panes... dont get what they do. after that i just quit. i dont understand what they ,or anything, does. the tutorial tells us what to do, but doesnt say why. HELPP!
|
In response to Iraqii
|
|
Iraqii wrote:
usually the part about panes... dont get what they do. after that i just quit. i dont understand what they ,or anything, does. the tutorial tells us what to do, but doesnt say why. HELPP! panes hold children |
In response to Obs
|
|
no children are a pane.hahahah funny joke!
|
In response to Iraqii
|
|
Well you made it through lessons 1 and 2. =)
The tutorial is set up for those who actually perform the steps as they are explained. Don't worry about "why", because that will be explained later on. Just focus on "how". So in lesson 3 about panes, just follow the steps and later on in the lesson you will be treated to this: So let's look back. We've created some panes and learned how to use them in the child control, which lets us use splitters. We now have an interface that has six panes (mappane, outputpane, gridpane, leftpane, inventorypane, and equipmentpane) and three splitters. The most important thing you can take away from this lesson is that for a flexible interface, many controls should be put in their very own pane. In fact so far the only place where two controls appear in a window or a pane is that the map and input controls are grouped together. Everything else can be moved separately. Later on we'll encounter some more exceptions to this, like if we create a rack of buttons, but we're still going to end up with a lot of panes. What does this mean? Well before lesson 3 you learned how to make a nice interface with all the controls fixed to the places you want them. After lesson 3, you can make a window that allows the user to adjust the boundaries between controls to how they want them. |