Board implementation in visual programming

Yikes, no. Do one big picture. Determine, using math, which square was actually clicked in based on the location of the click.

---

How appropriate. You fight like a cow.

either way really would be fine. As long as you code it well enough, having 361 "tiles" for the board shouldn''t be much slower (do your best to keep each tile object as trim as possible). Plus having seperate tiles will make it a touch more robust and allow you to do some cool things with the board more easily (e.g. Raise the tile that the player''s mouse cursor is currently over a bit).

quote:

---

Original post by MelvinElvin
either way really would be fine. As long as you code it well enough, having 361 "tiles" for the board shouldn''t be much slower (do your best to keep each tile object as trim as possible). Plus having seperate tiles will make it a touch more robust and allow you to do some cool things with the board more easily (e.g. Raise the tile that the player''s mouse cursor is currently over a bit).

---

and, can I just make one function to control all that "tiles"? (how?) or still I have to do a single manual coding for each tile?

well is this in visual basic, basic.NET, c++? there are alot of IDE''s out there for every language. if it''s an object oriented language then make a button object!

if it''s VB, just create a Buttwhenclickedoned function and whenever a button is clicked, forward any relevent data like mouse position, tile state (occupied? active?), etc to Buttwhenclickedoned. Then just use a for loop to create your buttons where you need them when you start up your game.

quote:

---

Original post by Penance
well is this in visual basic, basic.NET, c++? there are alot of IDE''s out there for every language. if it''s an object oriented language then make a button object!

if it''s VB, just create a Buttwhenclickedoned function and whenever a button is clicked, forward any relevent data like mouse position, tile state (occupied? active?), etc to Buttwhenclickedoned. Then just use a for loop to create your buttons where you need them when you start up your game.

---

i use borland c++ builder..

can you tell me a more detail how to do that things?

So you are writing a Chinese Go game?I guess.

Just use image is ok.

quote:

---

Original post by reean

quote:

---

Original post by MelvinElvin
either way really would be fine. As long as you code it well enough, having 361 "tiles" for the board shouldn''t be much slower (do your best to keep each tile object as trim as possible). Plus having seperate tiles will make it a touch more robust and allow you to do some cool things with the board more easily (e.g. Raise the tile that the player''s mouse cursor is currently over a bit).

---

and, can I just make one function to control all that "tiles"? (how?) or still I have to do a single manual coding for each tile?

---

ummm, lost me a bit on what you''re asking for there. control the tiles how?

I''d really just have the tiles largely as data structures, pointer to the "piece" (or whatever is in your game), a position, that sort of stuff. Any actual manipulation (like picking or say raising a tile when the cursor is over it) should be done by an external piece of code. Maybe have a board object while holds a linked list of all the tile objects, and have the board do all the manipulation of the tiles and so on and so forth. This is just basic code structuring though and you should really do it however you want. I would keep as much code seperate from the Tile object as possible though, since you''ll have heaps of them you won''t want them taking up too much room in memory.

I make a game named Pente. It''s like a combination between othello and tic-tac-toe.

thx 4 everything