maximcus
Build problems
I have just download your source code and tried to build in vs2013 and i got a lot of syntax errors. How to build your code because i have problem with WindowsFormsHost and i want to see why my process disappear from WindowsFormsHost when virtual keyboard is opened.
I think that I used С# 6 in WPFTabTip and that you will not be able to build it in vs2013. You can download and install vs2015 or vs2017 Comunity Edition for free to build this project or alternatively you could fix syntax errors (change the code to be C# 5).
I have tried and tested on vs 2017 community and it is OK to build. But still have a problem with WindowsFormsHost. I debuged it and i saw that values to move window to up are good but still window just disappear like it goes somewhere. To sum what i have. I have main application and in that application i start another process (application) through WindowsFormsHost. In that new application i have built in WPFTabTip and when i press on textbox instead of window go up it blink and disappear. I tried various steps for moving but even on -1 or 1 it is same. It disappear.
I do not know what WindowsFormsHost is. Are you using WPFTabTip in WPF app or in Windows Forms app somehow?
I ma using it in WPF. In WPF there is XAML component WIndowsFormsHost in which you can put tags from old Windows Forms. I have one in which i open third party application. It is application in application but user think that this is only one application.
Only way to do this is to disable animation and to enable keyboard to shows only in docked mode.
If I understand you correctly this third party application you are talking about is a Windows Forms app. If that is the case then I guess you are out of luck because WPFTabTip was designed specifically for WPF.
No this third part application is also WPF application but if you want to open third party application as process and control it from host application it must goes through WIndowsFormsHost. It would be very very good if you can add some sort of settings where user can say i want keyboard to be open always docked. But in that case no animations (moveBy or moveTo must be always 0). Because animations are guilty for disappearing.
Animations are kind of one of the main points of this library actually. So I suggest you fork this project and change it in whatever way you need. I do not have plans to add new features, so you have little chance of missing something new if you fork this project.
something like: TabTipAutomation.Style = "BottomDocked"; (this is what i need) TabTipAutomation.Style = "BottomUndocked"; (this is how your application is right now) TabTipAutomation.Style = "TopDocked"; TabTipAutomation.Style = "TopUndocked"; TabTipAutomation.Style = "LeftDocked"; TabTipAutomation.Style = "LeftUndocked"; TabTipAutomation.Style = "RightDocked"; TabTipAutomation.Style = "RightUndocked"; TabTipAutomation.Style = "Flow";
Sorry i didn't see your last message but it would be good to have only one version that can be installed through nuget. And also you don't need animations when keyboard is docked. There is no point for animations then.
nothing stops you from hosting your own nuget feed or even hosting your packages on nuget.org (although in your case I would recommend the first option)