On Wed, May 3, 2017 at 1:03 PM, Ian Clark <mrroos...@gmail.com> wrote: > On 2 May 2017 at 08:02, Robert Iakobashvili <corobe...@gmail.com> wrote: > [snip] >> >> Is it correct to say that a Store app cannot be an editor opening >> files in any location permitted, >> writing texts, Save As for the files etc. - complete sand-boxing like at iOS? >> > It depends on the app type. > > Apps built for the Windows runtime (WinRT apps) are heavily sandboxed > and restricted. > > Classic 'desktop' apps converted for the store have fewer > restrictions, and behave almost like their desktop counterparts. > > The restrictions on converted Win32 apps are outlined in more detail: > > https://docs.microsoft.com/en-us/windows/uwp/porting/desktop-to-uwp-behind-the-scenes > >> Is there a way to get permissions to function as a simple editor? >> > Coincidentally, the app I'm currently trying to submit is a text editor. > > My converted app installed and running locally is able to access all > the files that the standard desktop build can. > > Cheers, > > Ian >
Sorry for more one question. Is it correct to say that "converted desktop apps" are subject to Microsoft Store managed licensing? If yes, where is the licensing API to be used? Is it different for converted desktop apps from WinRT apps? Thank you in advance! Kind regards, Robert _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
