Ignore the event id that was something he/she requested. In your case it would be a filename of the image you want to show. So what does load_picture mean. Nothing, perhaps at the time I was just being dumb or writing nearly complete psuedocode. Probably the prior. What I probably meant was:
RPG::Cache.picture(filename)
Cache has a lot of loading methods.
battler
icon
panorama
tileset
title
picture
What they basically do are shortening this method:
RPG::Cache.load_bitmap(dir, filename, hue)
RPG::Cache.title will automatically throw in '/Graphics/Title/' as the dir and you only need the filename of the title screen image.
RPG::Cache.picture will load an image from the '/Graphics/Pictures/' directory.
If you want to show your own picture. First you should place the image in the directory you feel is most appropriate. You might even consider separating the images further within that folder. Anyway let's say you wanted to load an a file within the '/Graphics/Pictures/' directory and its named 'test.png'.
First we need to create a sprite object.
$test = Sprite.new
$test.bitmap = RPG::Cache.picture('test.png')
# Alternatively you can also initialize a bitmap like this:
# $test.bitmap = Bitmap.new('/Graphics/Pictures/test.png')
Then when you are done with the bitmap and the sprite:
$test.bitmap.dispose unless $test.bitmap.disposed?
$test.dispose unless $test.disposed?
I gave it global scope($) but it really depends on the application what scope the sprite should be. If we wanted to relegate this to a particular scene and the sprite would need to be accessed across several methods I would give it instance scope(@). Or if I could get away with it only needing to be accessed through main I would give it local scope. Which means it has no prefix.
I recall you asking what
alias_method does.
alias_method is used to save a reference to older code without overriding it. Whenever I code out a method and create a method by the same name within the same class I will overwrite the old method and the new one will run. Sometimes we want to avoid this situation so we use
alias_method.
Like for example with the default scripts. Let's say I want to add a HUD to Scene_Map's main and have it update within Scene_Map's update. I don't want to overwrite the old code. I'd rather preserve it so I don't have to recode the whole thing.
class Scene_Map
alias_method :old_main, :main
alias_method :old_update, :update
def main
@test = HUD.new
old_main
@test.dispose
end
def update
@test.update
old_update
end
end
Good luck with it DelSolu! :thumb:
[edit]
Doh, sorry xBrokenSin. I had most of it typed up but got sidetracked.
