I was wondering if anyone has any experience or knows if there is any way to add options to a system context menu in a windows phone 8.1 built in app. Specifically, I would like if possible to add a "copy to" option that copies data directly from a message to my app instead of having to select
-> copy to clipboard -> find my app -> paste into application.
Is this possible? Is there any other technique I could leverage?
No, it's not possible. You can make your app a share target to accept data shared from apps which do so, but that won't help for your specific case since the Messaging app doesn't share its messages.
Related
Actually, I created a simple app in C# which creates a snapshot of the screen and upload to One Drive automatically. But the problem is I need to open my application when i want to do the operation. So, to minimize the effort and enhance the accessibility, am trying to add an extra menu option to the context menu of title bar of all the installed applications. Is there any method to do the same. Please suggest.
Expected UI
I want the user to be able to select both files and folder in a picker dialog. Is it achievable in UWP?
The only way around this that I can think of is to create a flyout menu for the browse button that allows you to choose a folder or file item to pick then opens the corresponding dialog. But I want the user to decide after the dialog is shown or even choose both files and folders at the same time.
Should I just include the old OpenFileDialog? It seems like the wrong way to go about this.
I want the user to be able to select both files and folder in a picker dialog. Is it achievable in UWP?
As far as I know, it is not possible now in traditional UWP app. When your call the file/folder picker in your app, it calls a single, unified interface to let user pick files/folder from the files system or from other apps. As we know, UWP apps work in sandbox(app container), file/folder pickers break this container by using brokers, this is handled by system.
But it's just in traditional UWP app, there is method now to use Win32 APIs in UWP app if your app won't be published to Store. If you are interested in this method, you can refer to Brokered Windows Runtime Components for side-loaded Windows Store apps.
Our suggestion is that you may submit a request to add this new features for developing through the Windows Feedback tool.
I want to give user an option to restart immediately to apply different theme, using https://msdn.microsoft.com/en-us/library/ie/windows.ui.xaml.application.requestedtheme
Retargeting to 8.1 is not an option.
There is no way to programmatically restart a Windows Store app, and Windows 8 (as opposed to 8.1) doesn't support ThemeResources to apply theme updates to existing controls after they've been created.
You will need to tear down the existing visual tree and rebuild it, but there isn't a good way to do this on the existing page. The easiest way would probably be to navigate away and back.
I am developing a WPF application (C#) for Windows 7. I want to add my WPF application in right click menu for some file types.
It's like if you select some mp3 files and right click on it there is a option "Add to Windows Media Player List". I want to copy same behavior.
Any suggestion will really help.
It is a bit old question, but it can be done via C#. It is called "context menu shell extension".
https://github.com/dwmkerr/sharpshell
It is not so simple (shell extension needs to be registered for file types etc.), but this library simplifies the development and installation process.
I am trying to add a button to one of the existing tool bars in any windows explorer instance.
After much research i figured out that BHO (browser helper objects) are the best way to hook
to windows explorer.
My question is :
Is that the correct way to go about it ?
In the SetSite of the BHO i get the comObject that is the explorer window. What now ?
If i can get the hWnd of the explorer window can i use win API to add my button ?
Note i am developing in C# for XP.
Thanks.
1 In pre-XP you can add custom items in the default folder template because the folder window is actually a webpage. In XP and later that is no longer true. A Deskband is the supported way to extend the UI.
2 The site is the same. You can even sink DWebBrowserEvents2 to get notified when the folder view is ready.
3 using window functions on explorer is not supported. The supported way to customize the explorer is to create deskbands. it is theoretically possible if you have the resource to test your code against each and every version of Windows Explorer used by your client audience and continue to do compatibility testing when each new version (or new language) of explorer.exe is released.
BHO can not add deskband. If you want to start BHO and deskband programming, look at Paul DiLascia's article "My Band is Your Band" in the November 1999 issue of MSJ. There is another article "Building Browser Helper Objects with Visual Studio 2005" in MSDN for BHO. Basically you need to handle the DocumentComplete and BeforeNavigate events and be careful not to access the folder view when the document is not ready. You can use any communication method that you see fit between your BHO and your deskband, such as hidden window with special window class, static variable if the two are in the same dll, shared memory, named pipe, etc.
Microsoft does not support creating In-Process extensions in managed code until .Net 4.0