Putting a image memblock on a grid

Author

Message

Donald Smith

21

Years of Service

User Offline

Joined: 15th Nov 2002

Location:

Posted: 23rd Jan 2019 06:34 Edited at: 23rd Jan 2019 06:38

Link

So, here's my issue, then a question.

I'm running DBC 1.12 Enhanced and I came across Wipes and memblocks for images (first time using these) which would handy in a game I'm making, but the question is if my game uses a 3 x 3 grid (think tic-tac-toe) or:

1 | 2 | 3
---|---|---
4 | 5 | 6
---|---|---
7 | 8 | 9

and if I choose 9, for example, how can I get the 9 memblock image, execute the downward wipe, execute the upward wipe then restore the 9 memblock image?

Thanks, dsmith

Back to top

Profile PM

Donald Smith

21

Years of Service

User Offline

Joined: 15th Nov 2002

Location:

Posted: 25th Jan 2019 15:25

Link

So, can the memblock idea work? If not, 1) what about using sprites and the wipes dll or 2) can a sprite be programmed to start at the top line by line to "disappear" ?

Thanks, dsmith

Back to top

Profile PM

Latch

17

Years of Service

User Offline

Joined: 23rd Jul 2006

Location:

Posted: 28th Jan 2019 18:46

Link

Hi,

not at a DBC computer right now, but i might have some time to take a look a little later

Enjoy your day.

Back to top

Profile PM

Donald Smith

21

Years of Service

User Offline

Joined: 15th Nov 2002

Location:

Posted: 29th Jan 2019 00:15

Link

Thanks Latch. By the way, the images are the exact size.

Back to top

Profile PM

Latch

17

Years of Service

User Offline

Joined: 23rd Jul 2006

Location:

Posted: 29th Jan 2019 05:19 Edited at: 29th Jan 2019 15:43

Link

Hi Donald,

I couldn't find the wipe program, I'll have to dig around a little bit more on that. However, I can tell you the concept of how to do a wipe and supply you with some example code.

Basically, you page flip through different bitmaps. You might store a few different images on background bitmaps, and then swap in portions of those screens to the main viewable screen in locations that you choose.

In the example code, I create a colored grid on screen 0 (the main viewable screen). I copy that to bitmap 1 so I have a backup of it when I want to redraw the main screen in it's original state. next I create a background image on bitmap 2. I then slowly copy the pixels in the location of square 9 from bitmap 2 to bitmap 0. Once that's done, I copy bitmap 1 to bitmap 0 in the same location to restore square 9.

Then just for fun, I do a full wipe of bitmap 2 to 0 and then restore 0

rem a simple wipe example
   rem by latch
   rem 1/28/2019
      
   autocam off
   set display mode 1024,768,32
   sync on
   sync rate 0
   hide mouse
   randomize timer()
   
   rem first make some squares in a grid pattern
   sw=screen width()
   sh=screen height()
   
   rem if we divide our screen by 3, we can figure out the positions of each
   rem square
   xacross = (sw/3)-1
   ydown = (sh/3)-1
   
   rem for the demo, we're only interested in square 9
   rem but we'll store all of the screen coordinates for the whole
   rem grid
   
   dim sq(9,4) : rem store x and y coordinates in sq(n,n)
   
   x=0
   y=0
   for n=1 to 9
      sq(n,1)=x * xacross
      sq(n,2)=y * ydown
      sq(n,3)=sq(n,1) + xacross
      sq(n,4)=sq(n,2) + ydown
      
      ink rgb(rnd(255),rnd(255),rnd(255)),0
      box sq(n,1),sq(n,2),sq(n,3),sq(n,4)
      
      inc x
      if x=3
         inc y
         x=0
      endif   
         
   next n
   sync
   
   rem Ok, we've made our screen, copy it to another bitmap in the background
   create bitmap 1,sw,sh
   copy bitmap 0,1
   
   rem we're gonna create another bitmap in the background maybe to use some transitional effects
   create bitmap 2,sw,sh
   set current bitmap 2
   
   rem draw some bluish spheres on bitmap 2
   cls 0
   cinc#=255/63
   for r=0 to 63
      ink rgb(0,255-(r*cinc#),255-(r*cinc#)),0
      circle 64,64,r
      circle 64,63,r
   next r
   get image 2,0,0,128,128
   sync
   
   for x=0 to sw step 128
      for y=0 to sh step 128
         paste image 2,x,y,1
      next y
   next x

sync
   
   rem ask for keypress
   set current bitmap 0
   ink rgb(255,255,255),0
   text 0,0,"press enter to do wipe"
   sync
   wait key
   
   
   rem now here's a simple wipe on square 9.  We copy just those pieces of the hidden screen
   rem in the background to the area of our main screen we want to wipe
   for x=sq(9,1) to sq(9,3)
      for y=sq(9,2) to sq(9,4)
         copy bitmap 2,x,y,x+1,y+1,0,x,y,x+1,y+1
      next y
      sync
   next x
  
   
   rem and since we stored the original screen on bitmap 1 we can restore the main drawing screen
   for x=sq(9,1) to sq(9,3) 
      for y=sq(9,2) to sq(9,4)
         copy bitmap 1,x,y,x+1,y+1,0,x,y,x+1,y+1
      next y
      sync
   next x

rem copy all of screen 2 to 0 in a fast wipe
for y=0 to sh step 16
   for x=0 to sw step 16
      if x >= (sw-17) then x=sw-17
      if y >= (sh-17) then y=sh-17
      x2=x+16
      if x2>sw then x2=sw-1
      y2=y+16
      if y2>sh then y2=sh-1
      copy bitmap 2,x,y,x2,y2,0,x,y,x2,y2
      if x=sw-17 then x=sw
   next x
   sync
   if y=sh-17 then y=sh
next y
sync            
 
for y=0 to sh step 16
   for x=0 to sw step 16
      if x >= (sw-17) then x=sw-17
      if y >= (sh-17) then y=sh-17
      x2=x+16
      if x2>sw then x2=sw-1
      y2=y+16
      if y2>sh then y2=sh-1
      copy bitmap 1,x,y,x2,y2,0,x,y,x2,y2
      if x=sw-17 then x=sw
   next x
   sync
   if y=sh-17 then y=sh
next y
sync

wait key

+ Code Snippet

   rem a simple wipe example
   rem by latch
   rem 1/28/2019
      
   autocam off
   set display mode 1024,768,32
   sync on
   sync rate 0
   hide mouse
   randomize timer()
   
   rem first make some squares in a grid pattern
   sw=screen width()
   sh=screen height()
   
   rem if we divide our screen by 3, we can figure out the positions of each
   rem square
   xacross = (sw/3)-1
   ydown = (sh/3)-1
   
   rem for the demo, we're only interested in square 9
   rem but we'll store all of the screen coordinates for the whole
   rem grid
   
   dim sq(9,4) : rem store x and y coordinates in sq(n,n)
   
   x=0
   y=0
   for n=1 to 9
      sq(n,1)=x * xacross
      sq(n,2)=y * ydown
      sq(n,3)=sq(n,1) + xacross
      sq(n,4)=sq(n,2) + ydown
      
      ink rgb(rnd(255),rnd(255),rnd(255)),0
      box sq(n,1),sq(n,2),sq(n,3),sq(n,4)
      
      inc x
      if x=3
         inc y
         x=0
      endif   
         
   next n
   sync
   
   rem Ok, we've made our screen, copy it to another bitmap in the background
   create bitmap 1,sw,sh
   copy bitmap 0,1
   
   rem we're gonna create another bitmap in the background maybe to use some transitional effects
   create bitmap 2,sw,sh
   set current bitmap 2
   
   rem draw some bluish spheres on bitmap 2
   cls 0
   cinc#=255/63
   for r=0 to 63
      ink rgb(0,255-(r*cinc#),255-(r*cinc#)),0
      circle 64,64,r
      circle 64,63,r
   next r
   get image 2,0,0,128,128
   sync
   
   for x=0 to sw step 128
      for y=0 to sh step 128
         paste image 2,x,y,1
      next y
   next x      

   sync
   
   rem ask for keypress
   set current bitmap 0
   ink rgb(255,255,255),0
   text 0,0,"press enter to do wipe"
   sync
   wait key
   
   
   rem now here's a simple wipe on square 9.  We copy just those pieces of the hidden screen
   rem in the background to the area of our main screen we want to wipe
   for x=sq(9,1) to sq(9,3)
      for y=sq(9,2) to sq(9,4)
         copy bitmap 2,x,y,x+1,y+1,0,x,y,x+1,y+1
      next y
      sync
   next x
  
   
   rem and since we stored the original screen on bitmap 1 we can restore the main drawing screen
   for x=sq(9,1) to sq(9,3) 
      for y=sq(9,2) to sq(9,4)
         copy bitmap 1,x,y,x+1,y+1,0,x,y,x+1,y+1
      next y
      sync
   next x    

 
   
rem copy all of screen 2 to 0 in a fast wipe
for y=0 to sh step 16
   for x=0 to sw step 16
      if x >= (sw-17) then x=sw-17
      if y >= (sh-17) then y=sh-17
      x2=x+16
      if x2>sw then x2=sw-1
      y2=y+16
      if y2>sh then y2=sh-1
      copy bitmap 2,x,y,x2,y2,0,x,y,x2,y2
      if x=sw-17 then x=sw
   next x
   sync
   if y=sh-17 then y=sh
next y
sync            
 
for y=0 to sh step 16
   for x=0 to sw step 16
      if x >= (sw-17) then x=sw-17
      if y >= (sh-17) then y=sh-17
      x2=x+16
      if x2>sw then x2=sw-1
      y2=y+16
      if y2>sh then y2=sh-1
      copy bitmap 1,x,y,x2,y2,0,x,y,x2,y2
      if x=sw-17 then x=sw
   next x
   sync
   if y=sh-17 then y=sh
next y
sync    

wait key

could we achieve something similar with memblocks? Yes. It's a little bit more complicated. The concept is similar:

1. you need a memblock that would hold the original image
2. you need a memblock that holds the second image
3. it's helpful to have a third memblock where you can write stuff to combining the first two images

One method could go something like this:

first thing is to make a memblock from bitmap 0 (your main screen)

A. make a copy of memblock 1 into memblock 3
B. find the position in memblock 1 that you want to change
C. copy or write the data from memblock 2 to memblock 3 at the position in memblock 3 you determined from memblock 1
D. make a bitmap from memblock 3 to bitmap 0 (MAKE BITMAP FROM MEMBLOCK 0,3)

Enjoy your day.

Back to top

Profile PM

Donald Smith

21

Years of Service

User Offline

Joined: 15th Nov 2002

Location:

Posted: 29th Jan 2019 22:28

Link

Latch,
Attached is the WipeDemo files.

Thanks for your help, Donald

Attachments

Login to view attachments

Back to top

Profile PM

Latch

17

Years of Service

User Offline

Joined: 23rd Jul 2006

Location:

Posted: 30th Jan 2019 16:28 Edited at: 30th Jan 2019 16:34

Link

Hi D.,

I looked at the wipe DBC code and also the Delphi code. I'm not familiar with Delphi but think I have a general enough knowledge of programming to kind of sort out what the code means. I could be wrong, but looking at the Delphi code, it looks like the operations are always on the full screen and a single step affects a NxN pixel block. There are main arrays that hold 768 positions (assumingly to allow a maximum screen resolution of 1024 x 768). I believe the block sizes are determined by the actual screen resolution and the blocks - the groups of pixels affected at once - are pulled based on the block position in the arrays. So for example, if array position 200 has a block value of 767 in it, it will affect the area of the screen somewhere in the lower right hand corner depending on the block pixel size. It seems that the transitions are hard coded to affect the entire screen. If you choose bumpup or spiral or whatever, it's going to affect the entire screen.

With all that being said, I don't think there is a way out of the box to affect just the lower number 9 square in your example with the wipe DLL. However, if I recall there was a program that came with the wipe demo that allows you to create a customized wipe. If so, you could probably create the effect you want. You could also alter the code at the end of the DBC example.

` this is a custom block transition effect, created with the transition maker.
`
` It is supposed to be a tree blossoming...
`

function setup_custom_block_data
   restore cdata
   for i = 0 to 767
      read tmp
      WRITE MEMBLOCK WORD 4,i*2,tmp
   next i
cdata:
data 751, 752, 719, 720, 687, 688, 655, 623, 591, 656, 559, 750, 753, 527, 495, 624, 462, 718, 721, 463, 431, 592, 686, 689, 560, 399, 368, 429, 397, 336, 529, 365
data 428, 304, 498, 332, 272, 528, 467, 496, 241, 209, 749, 754, 654, 657, 436, 437, 438, 404, 427, 394, 300, 267, 177, 239, 393, 235, 206, 146, 367, 471, 472, 115
data 113, 173, 266, 202, 424, 360, 373, 497, 466, 435, 342, 473, 504, 311, 442, 537, 279, 312, 337, 265, 464, 306, 423, 421, 326, 231, 137, 108, 47, 52, 276, 215
data 314, 412, 603, 420, 325, 230, 136, 76, 15, 20, 244, 183, 315, 413, 604, 452, 357, 262, 168, 77, 16, 21, 245, 184, 347, 445, 636, 453, 358, 263, 169, 109
data 48, 53, 277, 216, 346, 444, 635, 484, 389, 294, 200, 140, 79, 85, 309, 248, 378, 477, 668, 451, 356, 261, 167, 107, 46, 54, 278, 217, 345, 446, 637, 419
data 324, 229, 135, 75, 14, 22, 246, 185, 313, 414, 605, 388, 293, 198, 104, 44, 213, 152, 282, 381, 572, 485, 454, 422, 390, 391, 359, 327, 295, 296, 264, 232
data 199, 201, 138, 106, 110, 78, 80, 49, 51, 84, 86, 118, 117, 151, 214, 247, 281, 316, 348, 349, 382, 415, 571, 602, 634, 369, 370, 338, 516, 418, 260, 166
data 233, 139, 303, 284, 182, 55, 401, 667, 380, 443, 170, 171, 172, 174, 141, 112, 186, 218, 379, 339, 335, 486, 111, 83, 149, 249, 410, 638, 328, 204, 143, 81
data 119, 250, 283, 376, 570, 114, 42, 237, 329, 355, 455, 334, 305, 150, 116, 280, 411, 530, 392, 205, 180, 121, 219, 317, 409, 476, 601, 297, 302, 271, 82, 120
data 181, 273, 165, 73, 88, 252, 286, 154, 211, 212, 285, 74, 87, 153, 251, 105, 142, 148, 377, 539, 573, 234, 197, 179, 344, 499, 561, 465, 741, 709, 677, 644
data 456, 292, 323, 187, 220, 375, 243, 540, 531, 612, 532, 144, 236, 17, 45, 56, 350, 203, 580, 581, 387, 461, 613, 579, 196, 102, 41, 50, 123, 221, 343, 633
data 582, 549, 744, 747, 757, 762, 765, 736, 767, 704, 738, 712, 743, 715, 725, 730, 733, 735, 764, 760, 672, 706, 680, 683, 693, 728, 698, 701, 703, 758, 755, 745
data 739, 737, 740, 742, 746, 748, 756, 759, 761, 763, 766, 674, 714, 724, 731, 716, 707, 726, 734, 692, 0, 1, 32, 2, 33, 64, 3, 34, 65, 96, 4, 35
data 66, 97, 128, 5, 36, 67, 98, 129, 160, 6, 37, 68, 99, 130, 161, 192, 7, 38, 69, 100, 131, 162, 193, 224, 8, 39, 70, 101, 132, 163, 194, 225
data 256, 9, 40, 71, 133, 164, 195, 226, 257, 288, 10, 72, 103, 134, 227, 258, 289, 320, 11, 228, 259, 290, 321, 352, 12, 43, 291, 322, 353, 384, 13, 354
data 385, 416, 386, 417, 448, 449, 480, 450, 481, 512, 482, 513, 544, 18, 483, 514, 545, 576, 19, 298, 515, 546, 577, 608, 175, 268, 299, 330, 361, 547, 578, 609
data 640, 145, 176, 207, 238, 269, 331, 362, 517, 548, 610, 641, 208, 270, 301, 363, 425, 487, 518, 611, 642, 673, 23, 147, 178, 240, 333, 364, 395, 426, 457, 488
data 519, 550, 643, 705, 24, 210, 396, 458, 489, 520, 551, 675, 25, 242, 366, 459, 490, 521, 552, 583, 614, 645, 676, 26, 57, 274, 398, 460, 491, 522, 553, 584
data 615, 646, 708, 27, 58, 89, 275, 430, 492, 523, 554, 585, 616, 647, 678, 28, 59, 90, 307, 400, 493, 524, 555, 586, 617, 648, 679, 710, 29, 60, 91, 122
data 308, 432, 494, 525, 556, 587, 618, 649, 711, 30, 61, 92, 340, 371, 402, 433, 526, 557, 588, 619, 650, 681, 31, 62, 93, 124, 155, 310, 341, 372, 403, 434
data 558, 589, 620, 651, 682, 713, 63, 94, 125, 156, 590, 621, 652, 95, 126, 157, 188, 374, 405, 622, 653, 684, 127, 158, 189, 406, 468, 685, 159, 190, 407, 469
data 500, 562, 593, 717, 191, 222, 253, 408, 439, 470, 501, 563, 594, 625, 223, 254, 440, 502, 533, 564, 595, 626, 255, 441, 503, 534, 565, 596, 627, 658, 287, 318
data 535, 566, 597, 628, 659, 690, 319, 474, 505, 536, 567, 598, 629, 660, 691, 722, 351, 475, 506, 568, 599, 630, 661, 723, 383, 507, 538, 569, 600, 631, 662, 508
data 632, 663, 694, 447, 478, 509, 664, 695, 479, 510, 541, 665, 696, 727, 511, 542, 666, 697, 543, 574, 729, 575, 606, 699, 607, 669, 700, 639, 670, 732, 671, 702

endfunction

+ Code Snippet

` this is a custom block transition effect, created with the transition maker.
`
` It is supposed to be a tree blossoming...
`

function setup_custom_block_data
   restore cdata
   for i = 0 to 767
      read tmp
      WRITE MEMBLOCK WORD 4,i*2,tmp
   next i
cdata:
data 751, 752, 719, 720, 687, 688, 655, 623, 591, 656, 559, 750, 753, 527, 495, 624, 462, 718, 721, 463, 431, 592, 686, 689, 560, 399, 368, 429, 397, 336, 529, 365
data 428, 304, 498, 332, 272, 528, 467, 496, 241, 209, 749, 754, 654, 657, 436, 437, 438, 404, 427, 394, 300, 267, 177, 239, 393, 235, 206, 146, 367, 471, 472, 115
data 113, 173, 266, 202, 424, 360, 373, 497, 466, 435, 342, 473, 504, 311, 442, 537, 279, 312, 337, 265, 464, 306, 423, 421, 326, 231, 137, 108, 47, 52, 276, 215
data 314, 412, 603, 420, 325, 230, 136, 76, 15, 20, 244, 183, 315, 413, 604, 452, 357, 262, 168, 77, 16, 21, 245, 184, 347, 445, 636, 453, 358, 263, 169, 109
data 48, 53, 277, 216, 346, 444, 635, 484, 389, 294, 200, 140, 79, 85, 309, 248, 378, 477, 668, 451, 356, 261, 167, 107, 46, 54, 278, 217, 345, 446, 637, 419
data 324, 229, 135, 75, 14, 22, 246, 185, 313, 414, 605, 388, 293, 198, 104, 44, 213, 152, 282, 381, 572, 485, 454, 422, 390, 391, 359, 327, 295, 296, 264, 232
data 199, 201, 138, 106, 110, 78, 80, 49, 51, 84, 86, 118, 117, 151, 214, 247, 281, 316, 348, 349, 382, 415, 571, 602, 634, 369, 370, 338, 516, 418, 260, 166
data 233, 139, 303, 284, 182, 55, 401, 667, 380, 443, 170, 171, 172, 174, 141, 112, 186, 218, 379, 339, 335, 486, 111, 83, 149, 249, 410, 638, 328, 204, 143, 81
data 119, 250, 283, 376, 570, 114, 42, 237, 329, 355, 455, 334, 305, 150, 116, 280, 411, 530, 392, 205, 180, 121, 219, 317, 409, 476, 601, 297, 302, 271, 82, 120
data 181, 273, 165, 73, 88, 252, 286, 154, 211, 212, 285, 74, 87, 153, 251, 105, 142, 148, 377, 539, 573, 234, 197, 179, 344, 499, 561, 465, 741, 709, 677, 644
data 456, 292, 323, 187, 220, 375, 243, 540, 531, 612, 532, 144, 236, 17, 45, 56, 350, 203, 580, 581, 387, 461, 613, 579, 196, 102, 41, 50, 123, 221, 343, 633
data 582, 549, 744, 747, 757, 762, 765, 736, 767, 704, 738, 712, 743, 715, 725, 730, 733, 735, 764, 760, 672, 706, 680, 683, 693, 728, 698, 701, 703, 758, 755, 745
data 739, 737, 740, 742, 746, 748, 756, 759, 761, 763, 766, 674, 714, 724, 731, 716, 707, 726, 734, 692, 0, 1, 32, 2, 33, 64, 3, 34, 65, 96, 4, 35
data 66, 97, 128, 5, 36, 67, 98, 129, 160, 6, 37, 68, 99, 130, 161, 192, 7, 38, 69, 100, 131, 162, 193, 224, 8, 39, 70, 101, 132, 163, 194, 225
data 256, 9, 40, 71, 133, 164, 195, 226, 257, 288, 10, 72, 103, 134, 227, 258, 289, 320, 11, 228, 259, 290, 321, 352, 12, 43, 291, 322, 353, 384, 13, 354
data 385, 416, 386, 417, 448, 449, 480, 450, 481, 512, 482, 513, 544, 18, 483, 514, 545, 576, 19, 298, 515, 546, 577, 608, 175, 268, 299, 330, 361, 547, 578, 609
data 640, 145, 176, 207, 238, 269, 331, 362, 517, 548, 610, 641, 208, 270, 301, 363, 425, 487, 518, 611, 642, 673, 23, 147, 178, 240, 333, 364, 395, 426, 457, 488
data 519, 550, 643, 705, 24, 210, 396, 458, 489, 520, 551, 675, 25, 242, 366, 459, 490, 521, 552, 583, 614, 645, 676, 26, 57, 274, 398, 460, 491, 522, 553, 584
data 615, 646, 708, 27, 58, 89, 275, 430, 492, 523, 554, 585, 616, 647, 678, 28, 59, 90, 307, 400, 493, 524, 555, 586, 617, 648, 679, 710, 29, 60, 91, 122
data 308, 432, 494, 525, 556, 587, 618, 649, 711, 30, 61, 92, 340, 371, 402, 433, 526, 557, 588, 619, 650, 681, 31, 62, 93, 124, 155, 310, 341, 372, 403, 434
data 558, 589, 620, 651, 682, 713, 63, 94, 125, 156, 590, 621, 652, 95, 126, 157, 188, 374, 405, 622, 653, 684, 127, 158, 189, 406, 468, 685, 159, 190, 407, 469
data 500, 562, 593, 717, 191, 222, 253, 408, 439, 470, 501, 563, 594, 625, 223, 254, 440, 502, 533, 564, 595, 626, 255, 441, 503, 534, 565, 596, 627, 658, 287, 318
data 535, 566, 597, 628, 659, 690, 319, 474, 505, 536, 567, 598, 629, 660, 691, 722, 351, 475, 506, 568, 599, 630, 661, 723, 383, 507, 538, 569, 600, 631, 662, 508
data 632, 663, 694, 447, 478, 509, 664, 695, 479, 510, 541, 665, 696, 727, 511, 542, 666, 697, 543, 574, 729, 575, 606, 699, 607, 669, 700, 639, 670, 732, 671, 702

endfunction

In theory, since the DLL uses pointers, you could create small offscreen bitmaps that are the size of the square you want to wipe. You would then perform the wipe on this screen and copy the bitmap into the location on your main screen.

This possibility seems kinda interesting, so when i get home, I might tinker a bit.

Enjoy your day.

Back to top

Profile PM

Sorry your browser is not supported!

DarkBASIC Discussion / Putting a image memblock on a grid

Attachments