Chains update

Valley Software’s 2nd application ever, Chains, received an update today*

The new version 3.1.1 of Chains now includes the ability to archive Chains.  So you can keep you history but clean up your Chain list.


Valley Software.


*for the UWP version.  Sorry, 8.1 development has ceased.

Voyer update

Hi there,

Voyer has received an update:

  • Major stability improvements in GIF heavy threads along with minor bug fixes.
  • (Requested) Ability to select the comment text, be it hyperlinks or other.
  • (Requested) Show name of the file (if any) as it’s often referred to in subsequent comments.

It is in certification now with Microsoft so hopefully rolling out towards the end of this week.

Keep the requests coming!

Valley Software.

Pinnie becomes Pins for Pinterest and enteres a quiet release phase.

“Pinnie”, my shelved Pinterest client has just become Pins for Pinterest and been uploaded as a concept to the Windows Store for Windows 10 devices.

The name change was necessary as some months ago another app was released with a startlingly similar name.

Pins for Pinterest is hidden from search, but available on request at the moment as it is still fairly early in development.  I am however allowing access to it by request.

So, what is Pins for Pinterest and why?

Pins for Pinterest is a 3rd party companion Pinterest app for Windows 10 devices.  Simple board and pin browsing using the Pinterest API, not a web wrapper or web scraper.  This limits it in some ways (the Pinterest AP doesn’t allow public searching, or even access to private boards!) but also gives it the power to interact via a Share Target and Set As Background/Lock Screen.

Also this simplicity will also be beneficial on Xbox.

It’s free (ad support and donation) and if well received will become more public in future.

This slideshow requires JavaScript.

Valley Software.

FlipView SelectedItem binding

For what ever reason, I’ve just lost some hours working around an issue with FlipView on Windows 10 ARM.
In the hope of saving you some time, lets take a walk through it together.
Consider this basic example:
  DataContext=”{Binding MyDataCollection}”
  ItemSource=”{Binding Items}”
  SelectedItem=”{Binding Current, mode=TwoWay}”>
Assuming you have an object (MyDataCollection) with an ObservableCollection (Items) and a Current property, you’d expect this to just work.  And you’d be right!
…Unless you’re on ARM.
On ARM it looks like the SelectedItem is ignored.  On closer inspection the FlipView is actually overwriting it.  First with the correct value, then with null, then again to the 0 item in the collection…
To work around this (I’m uncomfortable calling this a “fix”) you can set the SelectedItem binding in code behind after the loaded event fires which would otherwise screw everything up.
First, remove the SelectedItem Binding from your FlipView XML.
Now, add a Loaded event handler to the FlipView, and add the following code:
Binding b = new Binding();
b.Mode = BindingMode.TwoWay;
var p = new PropertyPath(“Current”);
b.Path = p;
fv_Items.SetBinding(FlipView.SelectedItemProperty, b);
This works because the FlipView is trying to set itself to the 0 item, regardless of what you say, and overwrites your property value in the process.
In this method, you are not setting the SelectedItem binding until after that tom-foolery is completed.