Is it possible to customize the looks of GitAhead to resemble TortoiseHg workbench?
I'm not asking for fonts or colors but for the position and display size of elements.
branch selection + sort and filtering in one line full width at the top
history log to be full width at the top under branch selection and filtering line
commit details to be under with split screen (left for file list, right commit message and file changes)
output log leave where it is (at the bottom)
If yes but only by modifying its source code on github https://github.com/gitahead/gitahead then I would appreciate some guidance
The design is hard coded. Any docks are used to change the look.
I tried to implement a mode to fullscreen the diffs or the commit list. Maybe you are interested in it
https://github.com/gitahead/gitahead/pull/408
At the moment the author is quite busy and is not able to have a look at all these changes.
Related
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.
In this documentation (under section "Specifying a Custom Executable to Run") I noticed that there is mention of what looks like a variable %{buildDir} in the field "Working directory".
I have struggled for a while now to find documentation for this feature. I would like to know first of all is there documentation for this somewhere?.
Secondary questions:
What other variables are available?
In which fields can they be used?
Can I access variables that I created in my project's .pro file?
Are there any other eval features or is this mechanism limited to variables?
Thanks!
As mentioned in the comments there is a "variables" button... supposedly for use all over the qt environment. However I have only found it available in obscure places that are not very useful!
However, you can at least get the list of vars from these places and use them where you actually need them. To find this, navigate to:
Tools (menu) --> Options --> Environment (tab) --> External Tools
Click "Update Translations..."
Click inside "Working Directory.." and you should see a "AB->" icon in colour to the right.
Click the icon for your list of vars.
You will notice that the style is a little different then %{BuildDir} but I believe the equivalent is %{CurrentProject:BuildPath} - You can see on the second screen shot I have right clicked and it asks you what you want to insert (the variable, or the value of the variable).
Annoyingly I could not figure out how to copy / paste the whole list as it is single line click only... maybe someone more clever can figure that out and we can stick that list in some Qt wiki :o
Here are the screen shots... Notice in screen shot 1 the little icon at the right side of "Working Directory" text-edit box.
In text edit widgets within Qt Creator (v5.14.0 and possibly earlier), there is an icon at the right end. Click on it, and a dialog of all the possibilities comes up. Make sure that the caret is at the proper position in the text edit widget.
I am trying to automate the process of turning display layers on and off in a modeling program using AutoIt. I am currently using code that simply simulates a mouse-click at a particular pixel position and as that of course needs to be set up differently depending on the screen being used at the time, I would like to replace the mouse-click simulation with getting the information from the window, looking for a certain text, then checking or unchecking the "Map" and "Legend" check boxes.
My problem is that I don't know how to do that. If someone has a good way to include or point to screen shots let me know but until then I will try to describe everything the best that I can.
The window:
The window I am referring to is titled "Map Layers". The area that I am specifically interested is looks like a large list box (it takes up the vast majority of the window space) and it has 4 columns: Layer Name, Map, Legend, and Sample. Name has the name of the layer, Map has a check box to control which layers are displayed, Legend has a check box that controls which layers appear in the legend window, and Sample for some layers has the symbol that will appear in the legend. for my purpose the Sample column is irrelevant.
AutoIt v3 Window Info:
When I use the finder tool I can't get it to highlight the "list box" area, only the surrounding boarder that it and some buttons are in. The window info says that this surrounding boarder area (which seems similar to a panel) has a class of Button.
So my fundamental question is what code to use to drill into that "Button", find out what the list view looking thing is, and get the info from it, then interact with the map and legend check boxes without referring to pixel location (or at least grammatically get the pixel position).
If I have left out any important information or was unclear anywhere please let me know.
Edit: Forgot to mention and don't know if it helps but the info given using the finder tool for the column headers is Control: Class: SysHeader32
Try RanorexSpy and see if it can give you more details.
Apparently everytime a script returns a new line the Build panel/Console on ST2 scrolls to the bottom, which is good so we can always see the latest output information, however when having huge stacks of information with long history it is natural that before a process finished you may want to scroll back and debug the information print before.
Since ST2 always scrolls to the bottom when a new line is inserted into the console, this becomes impossible to achieve.
My question is if is there any way to disable this 'automatic scrolling' for new lines on the build output panel or if somehow it is possible to make it behave just like terminal, where it will only continuing to scroll if your cursor or scroll location is already on the latest item and it becomes inactive as soon as you scroll up.
I hope that makes sense.
thanks in advance
I turns out I was dumb enough to not find out that by double-clicking the console panel it will then stop the scrolling and let me navigate through it. once I scroll again to the bottom, it continues from there.
I'm reasonably sure that this is hardcoded in, but I can be certain since I'm not Jon Skinner :) Most "consoles" act like this, continuously streaming the information as it is collected. Terminal emulators often include a "scroll on output" option to modify this behavior, but in my experience I haven't found anything like this in ST2 or ST3. If your programs are generating the output, you can always sprinkle in statements like print "==========" or something similar to break up the output somewhat, and perhaps give you an idea of where you are when you scroll back through.
We have a library bar filled with items, which can be dragged from and dropped onto it. Now the client wishes to see something like a scrollbar or arrows on the side, to have an indication if items are outside of the visible port.
As you can see in the librarybar template below, it contains a surface scrollviewer. Yet I don't seem to be able to reveal these scrollbars.
Any suggestions on how to resolve this issue?
The librarybar template:
http://pastebin.com/QVnvqbNm
Managed to solve it. Answer was easier then expected. Found out that the scrollbars were cleanly removed, but all properties regarding it were still present. Kind of misleading.
Easiest way to solve:
Open expression blend.
Insert SurfaceScrollViewer
Open Template from the SurfaceScrollViewer
Copy SurfaceScrollbars & necessary templates to the templates/resources
from your library bar
Adjust the templates to meet your requirements