This content has been marked as final. Show 5 replies
What is your problem here?1 person found this helpful
In WHEN-BUTTON-PRESSED of item level(BLOCK1.BTN1) i'll be calling another blockSo, you have a GO_BLOCK here? If that works, isn't that all you want?
Can you show us your code and the problem you have with it?
All what i need is to display only BLOCK1.BTN1 since i'm clicking this button alone... Both form level and item level to show the same value....Sounds like you have a GO_BLOCK or GO_ITEM in your BLOCK1.BTN1 When-Button-Pressed (WBP) trigger. That being the case, what you are seeing is expected because you moved the cursor to a different item.
All what i need is to display only BLOCK1.BTN1 since i'm clicking this button alone... Both form level and item level to show the same value....Is this causing a problem with the Form Level WBP?
Any idea on how to proceed with this?Sure, when processing is complete in the BLOCK1.BTN1 WBP trigger make sure you send the cursor back to the BLOCK1.BTN1 item if your Form Level WBP needs it there.
Hope this helps,
Thanks a lot for your response. You have answered the question. Thank you.
Glad I could help! Happy coding...
Well, that is a bizarre "feature".
One would think :System.Trigger_Item would always report the original trigger button used to start the process. But apparently after navigating to a different location within the item-level WBP trigger, the higher level WBP trigger "forgets" what button started the process, and reports the cursor location (:System.Cursor_Item) as the value in :System.Trigger_item.