Split Compare Differences Window - asp.net

I am using Visual Studio 2012 Ultimate on a Windows 8 platform. Before I commit code, I open Team Explorer > Pending Changes and then Compare with Latest Version each file. I use the Diff window to cleanup my own code and for code review with a colleague. It's really a wonderful feature.
I have multiple monitors and can't figure out how to split the Diff window. I can float the window and stretch it, but it gets clunky when I want to minimize only one half and I can't see some text near the margin between monitors.
Google helped me find a tool called WinMerge that allows for different (I won't say better) floating of the diff windows, but it's still contained in one clunky box that cannot be split.
Is there a way to "split float" the left and right halves of my diff Window to two different monitors but keep them line-number aligned?

Your issue is that Visual Studio does not have the functionality to allow two windows to scroll simultaneously. Your best course of action may be to try using a different text editor such as Vim to compare your code.

Related

JupyterHub - how to debug UI issues?

We use jupyterhub cluster and without any noticeable change on our side, the notebook cells' height turned huge and static (attached a picture)
Tried to fix the issue looking at - How do I increase the cell width of the Jupyter/ipython notebook in my browser?
Managed to decrease the cells size but it's still static.
Any suggestion what has might caused the change? And how to fix this?
This is how our cells look today -
Potential fixes
My suggestion to uninstall your extensions one-by-one until the problem goes away may honestly be the fastest way to get a fix. If have a reasonably recent version of Jupyter you can list all of your installed extensions with:
jupyter nbextension list
You would then start by uninstalling any extension that relates to theme and/or styling of the notebook. It's possible that list will miss some things (eg an improperly installed extension, or issues with your own config files). The next step (after getting rid of at least all suspicious extensions) would be to go through all of the user-space data and config files that Jupyter sets up in the background. You can get the paths to all directories containing such files by running:
jupyter --paths
Small note, you can probably ignore all files in the runtime dir, these probably aren't the problem.
If a mass uninstall of your extensions makes you squeamish, another option would be to debug the CSS of a live notebook and figure out exactly where the styling of the code cells is getting screwed up.
Detailed instructions for debugging the CSS
The following instructions are for Chrome, but if you're using another browser you should be able to figure out an equivalent:
start up a notebook
right click on a code cell and select "Inspect"
this will bring up a view of the DOM node hierarchy and highlight the node representing the code cell (or some at least some part of it) that you just right clicked on
on the right side of the screen will be a window with a bunch of tabs at the top. Select "Computed", which contains the style that is actually displayed in the browser, as computed from the sum of the effects of all CSS selectors
in particular, pay careful attention to the width and height properties of the computed style. Walk up and/or down the DOM hierarchy until you find a node with a suspicious looking width or height
If a value is greyed out, that means that it's being set in a parent node
start with a suspicious looking value, then go up the hierarchy until the values seem normal again
on one side of that transition point, you should have the top-most node in your hierarchy with bad values. If you examine the "Computed" tab, you should be able to see exactly which files are setting the bad values
The identity of the files screwing up your notebook styling is the payoff here. Examining those files should help you a great deal in uncovering the real problem.

SSRS reports rendering differently in the ReportViewer than in Visual Studio

My SSRS rdl report is rendering differently in the ReportViewer in an ASP.NET application than it does in BIDS (for this project we are on SQL Server 2008 R2 and BIDS). It renders the way I want it in BIDS, but the Report Viewer changes the placement of some of the textboxes. Specifically, it's pushing some text boxes down the page and creating a large area of whitespace.
I am using version 10.0.0.0 of the report viewer DLL.
Running the report in the ReportManager web UI in SSRS displays the report the same way as in the Report Viewer (not the way we want it).
BIDS is on SQL Server 2008 R2 SP3.
Ideas on how to mitigate this?
SSRS report elements when rendered in certain formats such as HTML cannot overlap in any way, whereas in the VS/Report Builder preview or formats such as PDF they can.
Due to this, if you aren't very careful to avoid these overlaps in your design you will see a different layout in the ReportViewer where SSRS has 'pushed' your report items around to remove the overlap.
We have similar issues, but different versions of SSRS. This page and many similar ones give information about rendering, but none of them seem to answer the questions "does this text fit in this box?" and "How big will this box be?" Rendering to IE, Chrome, Safari, Word, and PDF was an exercise in frustration and compromise, especially considering that Visual Studio and Report Builder were also different. In all cases, the height and width of the text boxes changed, the font size changed, the spacing around the text changed.
Our technique was to prioritize the various output formats, then find settings that produced the best output based on those priorities. Given this, users see better (but still not quite perfect) results than we see in Visual Studio.
I was able to find a solution for our particular problem by minimizing scenarios where SSRS will resize an element during rendering. For example, we had a text box that had the default height on the canvas (roughly the height of one row of text). The text had an expression with HTML content that included several line breaks. This caused SSRS to resize the textbox and push other elements down the page, even though there was space to fill without moving other elements. When I increased the height of the textbox on the canvas to fill the available space, SSRS stopped moving other elements around on the page.
My lesson learned is to set the size of an element on the canvas based on how big it is likely to be when it's rendered. If SSRS decides it needs to increase the size of an element, it starts moving other elements around on the canvas (even if there is space to fill without moving things around).

How to resize the designer-space in qt-creator if needed when developing?

As I am putting more widgets on top of more layouts in my application, the space where I design the GUI is getting also bigger for the Qt-creator interface.
I have many buttons and frames which are out of reach. I cannot see them (or click them, of course). I don't know how they look until I run the whole application for debugging.
Is there is a way to zoom out/in the main frame (the whole playground) so that I can see my full GUI design on the UI of Qt IDE?
P.S.: I am working on macBook 13"
Zooming is not possible. You can use Tools -> Form Editor -> Preview.
If the viewport gets too small the QtCreator shows scrollbars which allow to move the part of interest into view.
Note, on some system configurations the scollbars may be very small and hard to handle.
You can use this steps
Tool-->options-> Text editor ->zoom
Text editor

Section Lines Disappearing Graphical Issue

I am having a display issue with Infopath. My section lines and section text disappear in the form designer. The lines are initially there but then disappear after I click a few times and scroll. They still exist and can be clicked but I cannot seem them. I am not sure right now what exactly is causing them to disappear.
I am able to get them back again by switching views. This problem occurs both with infopath 2010, and 2007. It also happens to different forms. So it appears to be some sort of display issue. I have not noticed display issue's in any other programs.
I think the likely cause is because I recently formatted my computer, swapped graphics cards for the same model number but what looks like a newer revision because the fan failed on the last card. My specs may be relevant: I am using an AMD FirePro V4900, latest driver 13.352.1009 as of posting. 3 Monitor setup. Windows 7 x64.
Has anyone else run into this and found a fix?

Using QT For Creating a Screen Dimmer

I'm trying to implement a screen dimmer using QT4 and I wanted some advice before I get cracking instead of going into this blindly.
I want to create a top-level window that has no frame. I was thinking of making the background black and messing with the opacity so that it will dim the screen out after the system is idle for a given period of time.
The problem with this is that if this window is always on top, how can I pass click events to the window underneath it? I'm not the least bit familiar with the windows API (the solution only has to work under windows), but I'm guessing that's a good place to start. Can anyone point me to some useful classes/functions or suggest another way of doing this via QT?
If anyone's interested in the solution I came up with and the windows API functions I used, you can check out my blog posting here: http://sarcastichacker.com/getnextwindowandgetforegroundwindow
I will be updating the source and making another related posting on the same blog within the next couple of days.

Resources