Related
I'm trying to use the WSL console in Windows 10 (version 1909) for some development work, but I find that often running processes will simply appear to have hung, but when I send a keystroke to the terminal it will update back to the bash terminal (as if had completed all along but hadn't updated).
I am running the latest version of the debian package from the store.
Is there anyway to make this problem go away or am I wasting my time trying to use the default terminal?
Just a hunch, but I am guessing you are ending up in select mode. If you click anywhere in the terminal the title of the window will change to be prefixed with "select" and the terminal output will freeze so that you can select text without it changing while you try to highlight it. Pressing any key will cause you to exit select mode.
If this bothers you you can turn it off by right clicking on the title bar, clicking properties, and disabling quick-edit mode. Alternately, might I recommend the new Windows terminal, which handles selection and the clipboard in a more intuitive way.
I use in my project a statistics box with min, max and avg functions, everything works fine in desktop mode. If I select a value in my statistic box, data are filtered using the value selected (As I want).
Using WebView in desktop mode works also.
After deploying the project on qlik server and access the project, using Firefox or IE nothing happens selecting value in the statistics box.
Is there a trick to make statistics box "clikable" in web mode ?
Thanks in advance for your help.
I've never used the statistics box, but I've just tried it and it works in AJAX.
Which QV version is the server running?
Did you try with a basic QVW file to test it?
Just add the test script and try with a simple chart, statistic and selection box)
I have several reports created with multi value parameters. They are deployed to the report manager and run fine from chrome. When ran from Internet Explorer 11, when a parameter is chosen, I cannot click on the down arrows or scroll bar of the multi valued param. When I do it closed the param and would not scroll. I can use the scroll wheel but clicking does not work. This only happens in IE 11 which happens to be what 90 percent of our users use. Any ideas on a fix? This is SQL Server 2016.
I have connected IntelliJ to a remote JVM, and would now like to disconnect from the remote JVM without the remote JVM stopping. In Eclipse there are two buttons that explicitly stop the JVM or disconnect from the JVM, but the buttons on the debug windows in IntelliJ aren't clear. The tooltips and the online help aren't much help.
Stop (red square) - "Click this button to terminate the current process externally by means of the standard shutdown script."
Close (red X) - "Click this button to close the selected tab of the Run tool window and terminate the current process."
Rerun (green arrow around a grey square) - "Click this button to stop the current application and run it again"
I'm pretty sure it's the Stop button, but none of them makes it clear what will happen to the remote JVM.
Which button should I press to safely end the debugging session without killing the remote JVM?
Press the big red stop button (debug panel, on the left). It'll stop the debugger, not the remote process. I don't think you can use the debugger to explicitly kill the remote process -- you're only connected to the debug port and I don't think it can do things like that, unless you deliberately execute a System.exit(0) command in one of the code evaluation windows.
In my case I was looking for the red stop button which was not visible. But I found it on the left side of the debug window when hoovering over a blank section. Perhaps a bug since I am using color scheme Darcula?
Ctrl-F2 also works.
I have a strange situation. IT installed SSMS on my laptop and it runs well the first time, connected to my SQL servers remotely etc. But then it's frozen. I forced quit and then started SSMS again. Now it's totally frozen, no popup window at all to enter the server-connection text string. Then I did a force quit and got a pop up window (see it here ).
Microsoft SQL Server Management Studio has detected that an operation is blocking user input. This can be caused by an active modal dialog or a task that needs to block user interaction. Would you like to shut down anyway?
Has anyone seen this before? My IT department has no clue.
Often this is due to the new connection dialog being off screen (usually due to changing monitor setup e.g. 1 to 2 monitors or resolution change etc).
If so the really easy fix (if your connection dialog just needed approval without changing fields) is :
Focus on SSMS and Hit Enter/Return
..or the easy fix (if above does not work - as your last connection is not ready to go) is:
Alt Tab to SSMS
Alt + Space - context menu
M - select Move (in offscreen context menu)
Arrow Key(s) - to move it back onto screen
As per answers here from #Eirik Toft and here from #Lee Chetwynd
Fixed an issue which presented the same on my machine today by renaming a entry in my registry:
After some digging there seems to be multiple issues that can produce the same error (Application, settings, registry). This blog entry covers it pretty well:
http://www.armedia.com/blog/2012/08/sql-server-management-studio-freeze/
In my case deleteing the SQL server management studio folder under AppData ( c:\users\%userName%Appdata\raoming\microsoft\ ) didn't work.
However I was successfully after deleting / renaming the regisitry entry:
[HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server]
(update)
Worked out the underlying issue on my laptop - was using additional 2 screens with much higher resolutions which caused windows / SSMS to open up the connect to new data source dialog off all of them. If your using multiple screens try returning to just use the native laptop screen to see if you can find the dialog that SSMS is waiting on your input for.
I just had this same situation, with two additional screens connected to my laptop. SQL Server Management Studio was opened on the third screen, with the modal dialog nowhere to be seen.
Two options:
Press tab three times and enter. This cancels the dialog. Now you can move the window to another screen.
Set Windows to only use one or two screens. SSMS opens on the first and should still open there when you move back to using three screens.
When SSMS is on your primary or secondary screen, the modal dialog opens on the first and should be usable.
It was because multi screen display. Turning off multiscreen to single one resolved it. Reenabled multi screen display after ssms started working
In my case, "Run as Administrator" option worked like charm. I was accessing my server screen with the windows RDP. And when I open SQL Server Management Studio and Visual Studio 2010 user hangs at the moment and wont operate unless sign off r disconnected by administrator.
But when I set compatibility mode of both the application to the "run as Administrator", it starts working fine.
the problem also occurs if you have a touch screen. I fixed this by disabling the local thouch screen when I switch to RDP.