Skip to content
This repository has been archived by the owner on Sep 14, 2018. It is now read-only.

IronPython and WPF only string binding #1234

Closed
simplicbe opened this issue Nov 3, 2015 · 4 comments
Closed

IronPython and WPF only string binding #1234

simplicbe opened this issue Nov 3, 2015 · 4 comments
Assignees

Comments

@simplicbe
Copy link
Contributor

Hello,

currently i have a problem with bindings in WPF/IronPython. It seems that only binding string works correctly and random binding errors occures. Here is an article on stackoverflow with the issue: IronPython binding works but throws binding-errors

Another curious thing is, that when opening WPF Windows which uses binding, getter get called much more often as using plane c# code. This makes large WPF user interfaces very slow. If the UI contains some DataGrids, it is not usable any more.

Where can i start debugging this behaviour, or does already a solution exists?

Thank you very much!

@simplicbe
Copy link
Contributor Author

Starting at MetaPythonObject does not seems to be correct. No other tips for starting to research? But i thought that all python objects are basing on this class, so why does the getter/setter not get called when using WPF binding? Thank you.

@jdhardy
Copy link
Member

jdhardy commented Nov 17, 2015

MetaPythonObject is involved, but debugging IDMOP classes can be a bit tricky. Combining that with WPF bindings and I'm not really sure where to begin either. Wish I could be more help.

@simplicbe
Copy link
Contributor Author

Maybe i found some thing else, which has to do with this issue. When i attach the debugger to the application, and activate that exceptions are displayed where they are thrown, i get this additional exception, when binding is executed:

ip_runtimeexception

IronPython is searching for the __dict__ attribute in a c# base class, which is implemented in all ironpython view models. But it does not found __dict__. The exception it self is catched in ironpython, so the application does no throw any exception.

Or am i totally wrong?

EDIT
Making the attributes accepts and returns available for WPF, may solve this issue.

@simplicbe
Copy link
Contributor Author

Related to #1232 and will be solved there.

@simplicbe simplicbe self-assigned this Aug 11, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants