Hi,
The example is simple. I want to pass a single text from the caller to the listener:
But when doing this I get a message:
Specified argument was out of the range of valid values.Parameter name: Cannot read more arguments. Only 0 argument(s) were written.
What do I do wrong?
Regards
Tomasz
Hi Tomasz,
Triggering and handling events in OS (including sending input parameters) is very trivial with the built-in Events without having to use third-party components. So I'm wondering why you're using this component instead of the built-in mechanism.
Hi Aurelio,
But it is not an alternative to the native events. This is a powerful tool for sending messages from the parent screen to child blocks / webblocks (without touching the blocks' parameters!) or even to send them from a block to another block, placed somewhere inside the parent screen.
As a rule of thumb, I never use external components for functionality that can be achieved with the platform's built-in features. The issue you're facing with this specific component is exactly one of the reasons why. Add to that lack of proper support, the added overhead of having to keep an additional component in your factory, etc.
If you need to send messages from the screen to the block, you can do it without having to use the block's input parameters. Here's how. You can also easily use this to send messages from blocks to other blocks. For instance, block A triggers an event, the screen handles it and then uses the method above to send a message to block B.
I hope this helps!
All I'm saying is that I believe it's a bad idea to use a Forge component for something that can be easily achieved with the platform's built in capabilities.
As for resources, think about how much time you've wasted trying to make this specific Forge component work.
Since I've already expressed my opinion and, indeed, don't know how to fix the specific issue you're having with the component, I'll refrain from posting further in this thread.
Best of luck!
can you show what is going on in those Arg server actions (and why server actions) : i guess you are doing some sort of manipulation of the args being sent back and forth, i think maybe that's where your problem is
can you show the webblock in your screen with its properties : have you set the TriggerName and the event handler correctly ??
Dorine
As I understand, you never used this package if you ask me, what ArgText and Arg action do.
Thanks for being ready to help but I'm looking for somebody who uses this package and can easily, based on his/her experience, check, what is wrong with my actions.
This is usually my process :
In this case, after seeing your post last night, I downloaded that forge component and made a little demo app, and succeeded in triggering actions in different parts of my test screen / across webblocks.
I don't see an Arg an ArgText server action in the component (only one webblock and one client action), so I thought about asking you a bit more about them to maybe explain why I could trigger actions and you couldn't. That's all.
But hey, on to the next for me, good luck with finding help for this, maybe send personal message to the author will be quickest.
Regards,
Dorine,
Sorry for being, maybe, too harsh.
Events_ReactiveWeb (on Forge placed as Event System Reactive Web), as well as Event System, are only front-end wrappers over backend actions. These backend action (server an .NET in an extension) are placed in Event System and are the same for both versions. The Arg and ArgText belong to them.
I've written to Luiz - the author of this asset. I hope this will definitely help.