Congratulations, if you have gotten this far in the tutorial, you know enough to make simple modifications of how a skin looks. However, skins offer more than just the ability to switch out images; they also give you full control over exactly where the buttons should go, how big they should be, and also where the game screen itself should be placed.
Combining all of these, you can create very unique read: strange layouts for your skins, or maybe just make the game screen a bit smaller when in landscape mode. The point is, skins were designed to be flexible, and this section will show you just how to take advantage of everything! Open up the orientation of your choice in your skin template, then open up layouts. If you open up landscape, you should see the following options:. If you were to open up the portrait orientation, you would notice that there isn't an iPhone Landscape item.
If GBA4iOS can't find button mappings for the current device's screen, then it will fallback to another button mapping. Unlike images, if it can't find any button mappings, GBA4iOS does not revert to using the default skin; it just won't respond to button presses! This fallback mechanism is the same reason why there isn't an iPad Retina item for either orientation. Very rarely will the iPad and iPad Retina button mappings differ, so it's better to just map all the buttons for the non-retina version, and have all retina iPads fallback to using the non-retina mappings.
If the button mappings should differ between iPad and iPad Retina , or between iPhone and iPhone Widescreen in portrait, feel free to add either an iPad Retina or iPhone Widescreen item. Now, let's take a look at the format of how each button is mapped. Open any button up, and you should see four or five items:.
The first four items define the exact location of the button in the image in pixels, with no padding around it. The extendedEdges item is something special that we use to add padding around the buttons to increase the touch area, but we'll look at that later. Now, you may be wondering, how can the iPad and iPad Retina items use the same mappings, even though the iPad Retina image has twice the number of pixels both vertically and horizontally as the iPad image?
Well, this is because everything is actually mapped in points. On a non-retina display, one point is equal to one pixel. However, on a retina display, one point is actually four pixels; two pixels wide and two pixels tall. So even though the iPhone image is x pixels, everything should be mapped as if it were x So, if you're mapping anything other than an iPad image, it's recommended that you copy the image, downsize it to half its original width and height, and then map it.
Exactly how you find the location and size of the skin buttons may vary, but all GBA4iOS skins were mapped by downsizing images to non-retina sizes, opening them in Photoshop , and using a combination of masks and the Info window to find the exact pixel locations of each button.
Once you find the required information, you can fill in the button mappings for each button x and y refer to the x and y co-ordinates of the top left of the button location. Just so you know what each button does, they're each listed individally below. Some have slightly different mapping requirements than others, so make sure to read them all! Typically, it controls movement in games. Unlike other controls, this control is actually divided up into nine sections: eight control directions, and a center neutral section.
However, there aren't nine separate mappings for each section; there's only one for the entire D-Pad. Simple, it just divides the button mapping you give it into three equal sections horizontally and three equal sections vertically. Because of this, it is very important that you map the D-Pad exactly as it appears on the skin, and with no extra padding, or else the directions will not exactly match what the user sees.
To properly add padding without messing up the mapping, you can take advantage of the extendedEdges property, which will be explained in more detail below. Typically, this is used to select or confirm options in the game. Typically, this is used to cancel or perform secondary functions in the game. When pressed, this button actually presses both the A and B buttons at once, which can be useful for certain games.
Typically, this performs a secondary function in the game. As always, make sure to map it exactly without padding, since the pause menu that appears relies on the mapping to position itself next to the button on an iPad. Each extendedEdges item consists of four sub-items: top, bottom, left, and right. These four items "extend" the edge of a button in that direction by whatever value it has been set to.
For example, the A button may have a mapping of:. However, maybe the orientation-specific extendedEdges has a value of 10 in all directions. Berry 3. Flash 4. Green Lantern 5. Jolteon 6. Lightning 7.
Marvel 8. Naruto 9. Spiderman Arceus 2. Charizard 3. Charizard-X 4. Delta-Emerald 5. However, with thousands of games available to play, we wanted to give users just as many options for the skins they use to play the games with.
Want to have a Mario skin when you rescue the princess, or a Pokemon skin while you catch them all? With customizable controller skins, the possibilities are endless. To make the process easier, you can download the controller skins in-app, or alternatively download them from a 3rd party skin site such as GBA4iOSkins.
Out with the Old, In with the New. Take Classic Gaming one step further.
0コメント