Threaded Mode | Linear Mode

**darksun84** · 02-27-2015 07:51 PM

Probably is caused by this:

When you dclick(@charDclick) the vendor, the gump is sent to the player and the only reference inside the gump is the player and not the vendor.
So it's actually looking in the player tags instead of looking in the vendor tags.
The solution is to pass a reference (the vendor uid) along with the gump.

Wrong Example

PHP Code:

ON=@CharDclick
dialog d_test_gump,0,<act>   //act holds  the vendor uid,    0 is the gump page 

[DIALOG d_test_gump]
0,0
REF1=<args>  // args holds the uid of the vendor, it will be saved inside REF1, REFx  can holds uid of  items and chars
page 0
resizepic 0 0 2620 150 100
page 1
dtext 10 50 1152 Hello <ref1.name> //Here we show the name of the Npc dclicked
button 30 70 2473 2472 1 0 1000

[DIALOG d_test_gump BUTTON]
ON=1000
 
      SYSMESSAGE  Bye <ref1.name>
     // Problem ! When the button is clicked Bye 0 will be displayed, that's because we have lost the reference to the vendor.
     //REFx "exists" only inside the block of code  in which we have declared it.
     //We can't use ref1=<args> inside the button block, because the vendor uid is actually sent only "graphic" part of the gump. 

A simple right example is to store the vendor uid inside a player tag

PHP Code:

ON=@CharDclick
tag.vendorUID = <act>
dialog d_test_gump   //We don't have to send the uid of the vendor anymore
                             //Because we can directly access it from the player.

[DIALOG d_test_gump]
0,0
REF1=<tag0.vendorUID>  //We save the tag in REF1, we use tag0 for precaution
page 0
resizepic 0 0 2620 150 100
page 1
dtext 10 50 1152 Hello <ref1.name> //Here we show the name of the Npc dclicked
button 30 70 2473 2472 1 0 1000

[DIALOG d_test_gump BUTTON]
ON=1000
      REF1= <tag0.vendorUID>
      SYSMESSAGE  Bye <ref1.name> 

Anyway, this solution will create other problem that you will discover sisi

Threaded Mode \| Linear Mode Problem with Player Vendor System
Author	Message