kumara | Comment on Munoz-Rodriguez et al

I'm assuming the line console.log(responseJson.results) gives you the JSON response that you've provided above. If that is so, then results is a JSON object and within it you've got several key-value pairs. To access the value, simply use its key like this:

I'd think this is by design. When we create multiple windows for an app, each window behaves independently. Each window operates in its own thread. The Application.Resources used in each window is also independent.

Application.Resources is a ResourceDictionary object and ResourceDictionary class inherits from DependencyObject, so Application.Resources is also a DependencyObject instance.

All DependencyObject instances must be created on the UI thread that is associated with the current Window for an app. This is enforced by the system, and there are two important implications of this for your code:

• Code that uses API from two DependencyObject instances will always be run on the same thread, which is always the UI thread. You don't typically run into threading issues in this scenario.
• Code that is not running on the main UI thread cannot access a DependencyObject directly because a DependencyObject has thread affinity to the UI thread only. Only code that runs on the UI thread can change or even read the value of a dependency property. For example a worker thread that you've initiated with a .NET Task or an explicit ThreadPool thread won't be able to read dependency properties or call other APIs.

For more info, please see DependencyObject and threading under Remarks of DependencyObject.

So each Window has its own Application.Resources. In secondary view, the Application.Resources is re-evaluated from your ResourceDictionary. The BackgroundBrush would not be affected by the setting in main view as with the following code

I did it using List.it may not be the best approach.but it solved my problem.

First i mapped "JavaRdd Row to JavaRDD Tuple2