In my application we use AvalonDock for a docking manager, and have a variety of different windows. One of those contains an AvalonEdit editor. We recently noticed one specific interaction issue which I figured out to be caused by the AvalonDock.
When trying to block select code, you can use a bunch of different methods: Alt + click and drag, Alt + Shift + click and drag, Alt + Shift + arrow keys, and so on. One specific method, Alt + click and drag doesn't work. Specifically it does select, but typing doesn't work until you press either escape or space once. With Alt + Shift + click and drag it works fine.
I tested the AvalonEdit sample project as well as making my own simple example and it worked fine. When I put a test AvalonEdit window in a Window control instead of within a UserControl that's docked in my docking manager, it works fine. So something is going on with the interaction between having the AvalonEdit window within a AvalonDock vs. having it within some other window. Has anyone worked with these two controls together before? I know they're both used in SharpDevelop so I'd expect that they should work well together.
I found another issue which also has an alt-related issue with AvalonDock but it doesn't seem to be exactly what I'm seeing: AvalonDock Now Loses Alt Key Adornments. Also they claim that issue has been fixed, and I can't even test the solution in the answer as I don't have/use Blend. Looking at that bug makes me think it's more an issue with AvalonDock though and not AvalonEdit
In the end it turned out that AvalonDock wasn't the culprit directly. The real issue was a WPF Ribbon control which was stealing the focus when you pressed Alt. Killing hotkeys on the Ribbon fixed the editor interactions.
Related
On the iPhone's Instagram app browser(in app) if you open a website that includes html inputs of any type, something strange happens.
In the beginning everything is working, but once you tap an input and type something ( and the keyboard is opened), after you close the keyboard you can't click on anything anymore because all buttons/inputs/elements are clickable in a different location than where they showed ( button is showed in the original 100px location but click events are now on 50px).
It looks like after the keyboard opens the whole location calculation is shifted up(because the keyboard pushes the whole body up)
How to even begin to debug such thing ?
Honestly, I've been there. There is no way to debug the in-app browser (you can try on an iphone device mirroring with Chrome in MAC, but you will eventually fail), but I've tried without success.
It turned out that after digging around with similar issues, there was a caching issue and some disabled features with WP ENGINE from my client. They were able to fix it by allowing some parameters on nginx settings and then the In App browser wasn't stucked anymore.
I know every issue is different, but at this time, I haven't found a way to debug the In - App browser.
I can't speak to iOS specifically, but there definitely are ways to remote debug things.
My go-to for stuff like this (speaking from experience of browsers on gaming consoles) is Weinre: https://people.apache.org/~pmuellr/weinre/docs/latest/Home.html You get something similar to Chrome Developer Tools, but it works over a Socket.IO connection.
Another tool I like to use is Fiddler. While it won't help you with your DOM issues, if you ever need to debug network stuff on oddball devices, it's perfect. It serves as a proxy server and can intercept all your connections, including HTTPS. https://www.telerik.com/fiddler
Turns out, that it's a fixed position and it's not supported, which means when keyboard is closed, the system will push back the whole view but click events stay up (because it's being pushed up when you open a keyboard).
So instead of make it an absolute modal, which has it's own problem, we keep it fixed, BUT, we do the pushing up/down by our own.
We could just push the screen back down on input unfocused, but if user click the next field you get unwanted behavior, so we create a delay based machine like so :
var isfocused=0;
var focusTimer=0;
$("input").blur(function() {
isfocused=0;
focusTimer = setTimeout(focusDone, 150);
});
$("input").focus(function(){
isfocused=1;
});
function focusDone(){
if(isfocused===0)
$(window).scrollTop(0,0);
clearTimeout(focusTimer);
}
This works great on social browsers, with fixed positioned modals that has inputs inside them.
In one of my PCs when I use inspect tool in chrome, I can't select some part of a property or a value, so I have to retype all the value again. As many times as I click on the selected text, the caret doesn't go to the place I need and the selected text doesn't deselect.
the following picture shows what I want and what happens.
There is no problem in another PC.
Both are windows 10 64bit and google chrome 62.
Try holding shift or control while clicking. Haven't tried it, but it may work. My guess is that it's simply a UX workflow that DevTools doesn't handle well.
I have installed ArcMap Desktop 10.5.1 on a new computer and have a problem. I have never experienced with any previous versions of ArcMap.
Pressing the button of the toolbar for the Editor
I can’t access the toolbar.
I also can see that the program notices that I have pressed the button by the ArcMap-window ‘flickering’ and I see the Editor-window that should open for less than a second at some occasions.
I have tried to see if it ends up hidden somewhere, but it does not seems like it.
Printscreen of the ArcMap window with the editor button
Does anyone know what can be the problem and how to handle it?
I have tried to search for answers both at the ESRI help-page, here in stackoverflow and in other broad search engines, but this doesn’t seem to be a common problem.
This problem can have many causes and there are 2 different ways to open the editor toolbar.
Try click Customize > Toolbars > Editor (I will add a pic for it)
Right-click while your mouse on the main menu. The toolbar will be open directly and check the editor. Same solution.
If you have still this problem you must see another reason for the problem.
For example, do you using a second monitor? If you using it maybe the editor toolbar coming from another monitor. Check your monitor/monitors also.
If you still have problems, please write. There is another solution.
However, I am not writing now because it will reset usage of interface.
I want to switch tabs with the Ctrl+Page Up/Down shortcuts on Chrome (using the latest version). It always works correctly when I use the left Ctrl button, but with the right Ctrl button, it only works properly on some days. When it doesn't, it becomes page up/down instead of correctly being next/previous tab. I usually browse tabs for the same few sites, so I don't think it's due to the websites. I'm not sure what causes this. Is this supposed to be happening? How can I make the shortcut always work when using right Ctrl?
Edit: Found that it's basically any "ctrl+" shortcuts and not just next/previous tab. Also, I changed my keyboard recently, but this problem has existed since my old keyboard which I've used for 4 or more years, over at least two different computers, and Chrome is the only browser I use so I don't know if this problem will still exist if I switch browsers.
Your right ctrl button is not working properly (hardware problem). Maybe it's damaged or somewhat.
Some pages maybe does not alove that shortcut's. I'm saying this because i found that on some pages, and my shortcut's doesn't work on them.
I don't see other posible solutions for that.
I am trying to use monodevelop. Just at the beginning I came across an issue:
I was following a tutorial on building a Gtk application (http://monodevelop.com/Stetic_GUI_Designer). I was trying to drag a button from the Widgets Palette. Nothing happened. I'd been trying quite a few times without any luck.
After a break I launched monodevelop again and I simply placed a button on the window of the application. After that I removed it, dragged VBox container, and placed menu bar on the window, according to the tutorial instructions. I was pleasantly surprised.
By the second try the same problem occurred - I was not able to drag any widgets. Dragging was beginning, there was a “+” sign at the cursor and then - nothing was happening. I cannot figure out what happened by the first time, what the difference was. Have anyone had a similar problem? Monodevelop looks promising, but I can't go on with it. (I tried placing 'Fixed' container on the window, with no result - I could not drag it.)
(monodevelop v. 2.4, ubuntu 11.04, Polish language.
I did look for an answer to my problem, without much luck, that is why I post this question. The problem is described quite precisely. There is a probability that others encountered the same issue.)
You need to drag a container on the form first before you can add widgets to it. The VBox container is an example of a place where you can put your widgets.
If you want to place widgets where ever you want you can use the Fixed container. If you want things to align you can use the VBox, HBox or Table containers. Placing in a widget in one of the fields will automatically adjust the size of this field to fit the widget you have dragged into it.
So basically,
Create a form
Drag a container on the form
Drag a widget inside the container.
These widgets are not to be confused with the custom made widgets (in your Solution browser, right click the folder User Interfaces and click Add Widget...). These are like forms. I use these to create GUI's in advance so I can call these while the program is running.
FYI: if you want to create code for a widget (like a button) you can't just double click it like in Visual Studio. You need to select it, the go to the properties pane, and change the tab from Properties to Signals. You can then double click the "signal" to create the event for which you want to create code. For a button this is usually the Clicked event (somewhere at the bottom of the list, you'll need to open the Button Signals)
You can always visit the IRC channel of Monodevelop on irc://irc.gimp.org/monodevelop (IRC.Gimp.org #monodevelop)
I also sit in this channel and can help with smaller problems and I also still use Monodevelop 2.4.