GithubHelp home page GithubHelp logo

Comments (9)

ccgould avatar ccgould commented on May 11, 2024

This causes a problem with refreshing the nodes tho

from nodenetwork.

Wouterdek avatar Wouterdek commented on May 11, 2024

It seems you have copied and modified the example code. I can't really investigate this without a reproducible example. Could you upload your code?

from nodenetwork.

ccgould avatar ccgould commented on May 11, 2024

I tried it in the demo project as well if you install the new propertychanged.fody it crashes

from nodenetwork.

ccgould avatar ccgould commented on May 11, 2024

image

from nodenetwork.

ccgould avatar ccgould commented on May 11, 2024

image

from nodenetwork.

Wouterdek avatar Wouterdek commented on May 11, 2024

Here is what happens:
After compilation, fody inserts a call to RaisePropertyChanged in any property of a class that implements the INotifyPropertyChanged interface (directly or indirectly).

Before fody:

public PortType PortType
{
    get => _portType;
    set => this.RaiseAndSetIfChanged(ref _portType, value);
}
private PortType _portType;

After fody:

public PortType PortType
{
  get
  {
    return this._portType;
  }
  set
  {
    if (this._portType == value)
      return;
    IReactiveObjectExtensions.RaiseAndSetIfChanged<CodeGenPortViewModel, PortType>((M0) this, (M1&) ref this._portType, (M1) value, nameof (PortType));
    this.ReactiveUI.IReactiveObject.RaisePropertyChanged(<>PropertyChangedEventArgs.PortType);
  }
}

As you can see, this does not make sense. It seems this is not a NodeNetwork issue, but rather that PropertyChanged.Fody is not really compatible with ReactiveUI.

Is there any reason why you are not using ReactiveUI.Fody instead? It is specifically tailored for ReactiveUI, is supported by the ReactiveUI team, and seems to work perfectly here.

from nodenetwork.

ccgould avatar ccgould commented on May 11, 2024

Yea it is a Fody and ReactiveUI issue. When I used ReactiveUI.Fody I lost my property changed functionality did yours work or is there an extra step I am not familiar with ReactiveUI that much

from nodenetwork.

Wouterdek avatar Wouterdek commented on May 11, 2024

It worked fine for me after following the guide on the github page: https://github.com/kswoll/ReactiveUI.Fody/blob/rxui7beta/Readme.md

I am closing this issue because it is not related to NodeNetwork, but rather to Fody/ReactiveUI

from nodenetwork.

ccgould avatar ccgould commented on May 11, 2024

Ok ill give it a try

from nodenetwork.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.