rothman

Newbies
  • Content count

    1
  • Joined

  • Last visited

Community Reputation

0

Profile Information

  • Gender
    Male
  • Location
    GER - Heidelberg
  1. Hello everyone maybe i've searched for the wrong key words but i could not find an existing thread about this "Issue". i’m (happily) using paint.net for a while now and just recently bought the MSStore version to support this great piece of Software Unfortunately with the Metro/App Store executable it’s not possible to call PDN from another program anymore In my case i’ve just linked „PaintDotNet.exe %1“ from my (Faststone) picture browser and could directly open PDN with the picture in it for editing... OFC i've tried to link to Program Files\WindowsApps\dotPDNLLC.paint.net_4.21.6589.0_x64__*\PaintDotNet.exe instead but it just wont start. In a search for a solution i came accross this stackoverflow thread. I can now start the app from CMD line via explorer shell:AppsFolder\dotPDNLLC.paint.net_h55e3w7q8jbva!dotPDNLLC.paint.net (id might be different for you) but it wont accept any handover params like a filename So one workarround to call a Metro App with any handover values seems URL handlers e.g. like start netflix: start ms-windows-store:updates start pdn:<filename> ?? Another option would be to register PDN as default app for all possible image filetypes and then invoke a "start <filename>" respectively link it as "cmd.exe /c start %1" But then you loose the option to simply open your pictures in your picture browser in 1st place of course -_- I know M$'s way to implement Windows Store Apps is not the DEVs fault but maybe defining Paint.Net Metro App's properties to act as (e.g. pdn:) url handler would be an easy to implement "feature" to externally call PDN without breaking the user's favorite filetype assignments. Cheers, rothman