I hadn't really seen this as a problem until my client mentioned that the majority of his clicks on buttons on the app I'm developing do nothing. I enquired a little about what exactly he was doing and it turns out that he was clicking (using a mouse, this is a sencha touch app that is embedded inside of a windows application and will ultimately be running on a windows 7 UMPC 'tablet') on a button and releasing BUT the pointer had moved between the click and the release (by a couple of pixels). However this seems to not trigger the tap handler for the button. The only way it works is if you click and release in the exact same spot with no dragging inside of the button at all.
I think thats a little odd - clicking and moving the pointer and then releasing, all while still inside of the button - should trigger the event handler IMO. Clicking, moving and releasing OUTSIDE of the button shouldn't (which it does, as expected).
Anyone else experience this or know of a way to counteract this behaviour?
Thanks
Turns out that this only happens when the app is hosted within WebKit.NET browser control - if I just run it within Chrome the click behaviour is fine - can click and move the mouse and release (while inside the button) and the onTap event fires fine.
Related
I have a problem with Xamarin.Forms.Buttons. I want my app to execute an action when the user presses the button, and a different action when the user releases it. The problem is that once you have pressed the button if you move the finger(while you are still touching the screen), the released event will never be triggered even when you release the finger. When you move the finger, the button makes the animation like it was released/lostFocused but the "Released" event is not triggered. If you press and release again the same button without moving the finger, both events are triggered.
I would like always to know when the user has finished pressing a button.
Is there a way to make the "Released" event trigger in that situation?
Can I make the button has a "IsPressed" property or something simillar, so I can check it?
Can I check for example a "Screen.IsPressed" to know that the whole screen is not touched anywhere?
Thank you very much in advance.
If I make a new project with a simple button, I am not finding that problem either. In the project that I have the problem, my button is part of a ViewCell that is part of a ListView. Maybe that is causing the problem. By the way, I was able to solve the problem using a CustomButton.
https://forums.xamarin.com/discussion/comment/423607#Comment_423607
I have a window in my mac app, and when I click on any control in it, the window moves. This only happens when the window is not activated (focused?). If the window is already the main window, it works fine.
What would cause this? I'm thinking I'm not returning some kind of 'handled' value so that the mouse event is getting passed back to the window's move routine, even though I am not over the move bar.
Thanks for any suggestions!
I have some old VB 6.0 code that I need to get running on Windows 10. We are not allowed to use Compatibility mode due to security and client refusal issues.
The only problem I am having is that whenever a button is clicked on the interface the menu items (across the top) become unresponsive. If you mouse over them the shading changes but clicking does not drop down the menu. Additionally, if I generate a message box pop up and click OK the menus come back to life.
I've tried setting focus to the main form in different situations, tried refreshing the parent and child forms. Also added a brand new button with no code behind it - not even an empty click event handler - and that button when clicked causes the same issue.
I should also add that the main form is an MDI form with three child forms. The buttons of course reside on the child forms.
I'm not sure how to proceed with this at this point. I certainly can't have a message box pop up after every button is clicked. Has anyone seen this before or have any ideas as to what causes it?
I have a very large accounting system. In a user preferences section, the program has begun to act abnormally on my development machine only. No customers are reporting this, nor can I duplicate it on any of my other computers. Running Windows 8.1, others are on 7.0. Not exactly sure when this started happening because it's not the kind of thing one goes into on a regular basis. The preferences screen consists of a tab control and various standard controls. At the bottom is Okay, Cancel, and Apply buttons. All three buttons seem to be acting with the same strange behaviour. Clicking with a mouse does not generate a click event yet does not hang the system - mouseup follows and you can click it again and see the mousedown and mouseup but no click. However, since the Okay is defined as Default, pressing enter DOES create the desired click event, and all the code inside that even runs fine. Cancel and Okay also unload the form, but when clicked, that doesn't happen because none of the code gets executed, yet you can still navigate the screen (move between tabs and controls) but you can't even click the "X" button to close the form at that point.
Also, if you go straight in, and press enter, everything works and the form unloads, but if you do anything before pressing enter (or escape to cancel), like change a tab and/or edit a value, then press enter, the click event again does not run and the system semi-hangs.
I tried turning-off my anti-virus thinking that might have something to do with it, but no-go. Debugging is frustrating because while I finally got it execute the click event, the stop command inside that event (after debug.print "click") would allow stepping and success if just straight in and enter, but if anything else done as before described would stop at the stop statement (keyboard enter only still no mouse clicks under any scenario) and would do a total lock-out. In other lockouts where it would let me navigate, almost always selecting a new tab would cause a fatal error and it would force-unload VB for me, otherwise I had to use the task manager.
This is driving me nuts, but I don't know how else to debug it.
The culprit was tv_w32.dll which is Team Viewer. Turning-off Team Viewer allows my program to run normally.
I know how to implement the back button. My question is about the desired behaviour (as I experienced there is a hype around it that the good implementation of back button is required to sell the app in the store).
There is the official source:
http://msdn.microsoft.com/en-us/library/windowsphone/develop/ff402536(v=vs.105).aspx#BKMK_BackButton
But I have never used a WP8 for more than 5 minutes. I understood that the "Windows" button/key is the same as android home and ios home buttons. Is it true, that the WP8 back should be the same as the android back? (Briefly navigate back through pages (screens/activities), dismiss alerts or cancel confirm popups, or if it is the first/only/final page/activity, the app should exit.)
As I experienced, there is a long-press on the back button, which brings up the app switcher (~ios double home). Is it true that I should not take care about of this button? Is the default behavoiur the same for the remaining buttons (windows, power off, camera (half and full), search)? Should I override them? Can I override them (I think I can use camera, but can I use volume controls for other purposes)?
The certification requirements lay out what the back button should do pretty well. In short, it sounds like how you described the Android back button - here are the relevant requirements:
(5.2.4.1) Pressing the Back button must return the app to the previous page or return to any previous page within the back stack.
(5.2.4.2) Pressing the Back button from the first screen of an app must close the app.
(5.2.4.3) If the current page displays a context menu or a dialog, the pressing of the Back button must close the menu or dialog and return the user to the screen where the context menu or dialog box was opened.
You don't have to handle triggering the long-press, nor do you need to handle navigation specifically (assuming you're using the NavigationService for page navigation.)
You can definitely override the camera button, but search, power, and volume are off limits.