This repository was archived by the owner on Sep 2, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 11
Mono V2 Testing #13
Open
Local9
wants to merge
22
commits into
manups4e:mono_v2
Choose a base branch
from
Local9:mono_v2
base: mono_v2
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Mono V2 Testing #13
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
Author
|
Personally not a fan of the |
manups4e
reviewed
May 20, 2023
Remote type will probably get more functionality added, not removed. But you're always free to convert them into a
😏 |
Have I understood this correctly? The invoke needs to be changed.
```cs
DynFunc dynFunc = Func.Create<T,R>(MyFunc);
dynFunc(remote, arg1, arg2, arg2); // which is the same as:
dynFunc(remote, new object[] { arg1, arg2, arg2 });
Delegate dele = dynFunc;
dele.DynamicInvoke(arg1, arg2, arg3); // calls: dynFunc(arg1, arg2, arg3); which is wrong
dele.DynamicInvoke(remote, new object[] { arg1, arg2, arg3 }); // calls: dynFunc(remote, new object[] { arg1, arg2, arg3 }); which is correct, but slow
```
- Send Remote down from the Event Handlers due to use of DynFunc - Client doesn't know what a Player is? maybe I'm missing something? - Client doesn't get information back but the method on the server is invoked, still there is a arguments issue which needs to be addressed.
Collaborator
Author
|
Will install RedM tomorrow and do some RedM testing too. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SubstringerrorCurrently have an issue where events sent from the client are not showing any activity on the server console, this requires more investigation but currently builds are working so it can be tested.
Client:

Server:

ignore the MySql.Data error, its not related to the current issue and doesn't stop the resource from working