Well, if you know you need a specific number of Polaroids photos beforehand,
you can use the simplest native Java array type.
Otherwise, you'll need an ArrayList<PImage> type.

...

final static int picNum = 9;    // max number of Polaroid pictures to store
PImage [] picture;                 // array of Polaroid pictures

...

picture [0] = loadImage("picture.jpg");
picture [1] = loadImage("xxxxx1.jpg");

...

picture [8] = loadImage("xxxxx8.jpg");

And so on!

Perhaps you may need a boolean array to indicate if a particular picture index is authorized to be displayed:

final static boolean[] showPic = new boolean[picNum];

Or instead, something simpler like a counter:

If counter == 0, display no Polaroid picture
if counter == 1, show only the 1st Polaroid picture -> picture[0], that is picture[counter - 1]
if counter == 5, display first 5 Polaroid pictures, that is -> from picture[0] up to picture[counter - 1].
if counter == picNum, show all available pictures -> from picture[0] up to picture[picNum - 1]

To display all images inside draw() callback function, you're gonna need as many image() statements as the number of photos.
Of course, to avoid redundancy, we're gonna rely on a for loop block:

• Instead of     -> image(picture[picNum], bx, by);
• Try this loop -> for ( int pic = counter; pic != 0; image( picture[--pic], bx + 75*pic, by ) );

so my code looks like this now but it says there's a syntax error.  I don't get what it means by it

You're declaring picture 2 times. You have to remove 1st one!

And I had made some edits in previous post to fix some details too! 

Mostly, I forgot to declare iterator pic w/ int! 

I was not expecting you to read it so early! HEHEHE

I was able to figure out my problem phew! only thing now is seeing if I can make each Polaroid separate.  Each time I add one, it attaches to the previous one and can only be dragged around by the parameters of the first picture

Perhaps you should try the OOP approach; that is, have a class to represent the object Polaroid picture!
That way, you can make instances (copies) of that, each 1 having their own separate characteristics like:

• which picture file to display;
• which (x,y) coordinates to place it;
• a flag to indicate show/hide states, etc.

You would have to move things around a bit.

The idea of a class object is that variables which are pertinent to the object, should be declared and stay inside the class.
In the same vein, the functions which manipulate the object stays inside the class as well.

It's some kind of encapsulation and blueprint, to be separated from the rest of the sketch.

Once you have a complete class object, variables (also called fields) & functions (also called methods), you can make as many copies of it (also called instances), and each one can have their own values for each of their variables.

For example, imagine the object has variables which store coordinate positions x & y.
Each instance of the object will have their own separate values for the same variable.
Instance #0 can have its x = 100 & y = 50, and instance #3, in turn, have its x = 430 & y = 70.

It needs some planning. But once done, it's very easy to control and modify!
However, since you dunno classes yet, better keep doing the next best thing, arrays!

You already have an array to store each of the 9 Polaroids.
What about making more arrays which define w/ more details those Polaroid photos?

Following the same model how classes are made, you can make an array to store its scalar x and another for y.
So you'll always know where to place each photo at the screen canvas.

And of course, a 4th one to store a boolean flag to define show/hide states for each photo!

Once you have those characteristics stored in arrays, you'll have full control where to place and when to show each photo!!!
By full control I mean, able to write more efficient functions which use the data stored in those arrays.