Is it possible in RStudio to change the width of the field with the names of the variables? I often have variables with long names that are not fully shown. Of course, I could simply make the whole window larger, but then the editor window gets smaller, which I don't want it to.
It's currently not possible
Further informations on the RStudio Support page: Environment-pane-cutting-off-variable-names
The official comment is:
Unfortunately this is currently not possible but its something we're looking into implementing going forward. In the meantime, hovering over the variable names in the Environment pane should bring up a tooltip that states the full name of the variable - hopefully that will be helpful to you for this purpose.
Related
See the "..." before "layout-1c"? Firefox seems to have some rules defined for when it should collapse a lengthy element attribute. I want to disable this. Just show me everything, always. How?
EDIT double-clicking the attribute is not good enough. It loses wrapping and makes you manually scroll through a ton. Firebug does everything right from the get-go and I'd like the same behavior for the built-in inspector.
In the official mozilla docs it explains how we can tweak whether to truncate or not, and also how many characters will be shown before being truncated:
Truncate DOM attributes
By default, the Inspector truncates DOM attributes that are more than 120 characters long. Uncheck this box to prevent this behavior. This setting works by toggling the about:config preference "devtools.markup.collapseAttributes". To change the threshold at which attributes are truncated, you can edit the about:config preference "devtools.markup.collapseAttributeLength".
There is a convenient checkbox in developer tools.
To find it click the three dots in the upper-right corner and go to Settings:
Truncating long attribute strings is, so far, a feature of the Firefox inspector, as in some cases, attributes may be really long and make it hard to use the tool. Think of base-64 image data-URLs for example.
I understand that this feature might not always be wanted, but for this to change, the inspector's code needs to be changed, there isn't a setting you can use. 2 options:
Increase the limit after which strings are truncated to make sure only really long attributes are,
Or add a setting (off by default to preserve today's behavior) to turn this off entirely.
But to answer the original question, no you can't disable this (other than by changing the code, or writing an addon that would monkey-patch this).
You can double-click the attribute value to show the collapsed content. Note that this is a non-persistent solution.
The most optimal workaround speed-wise seems to be right-click "Edit as HTML".
Fortunately we have a bug filed now https://bugzilla.mozilla.org/show_bug.cgi?id=1198073
Is it possible to change the width of the text editor in VS2012 - I've got a fairly wide screen and use fairly small text so I end up with a lot wasted real-estate in the middle of my screen.
I don't want to turn off word wrap - I just want the wrap to start further right on the line. If that makes sense!?
You can set this with HTML in Visual Studio 2012 but there is no global setting and it's missing in quite a few languages.
You can just put another "dummy" window next to the one you are writing in, so the actual editor window will be smaller. You can put it on the left if you want to pan the text to the right, and to the right if you want to shorten the lines.
I actually found the answer elsewhere; VS doesn't appear to provide this functionality but Resharper does. Resharper -> Options -> Code Editing -> C# -> Formatting Style -> Line Breaks and Wrapping -> Right margin (columns)
I put mine to 200 which fixed the issue
I know that this is not what you are looking for, but I believe it solves the same problem. I too have a fairly large screen and try to make use of it as optimally as possible.
I hate tabbing between code or design tabs and try to avoid that as much as possible.
VS has a feature that permits the user to create Horizontal or Vertical Tab groups and ever since I have started using it, I have found it very helpful. These options are present in the context menu by right clicking the tab or in the VS Window Menu (Menus are seen only if the tab groups feature is not active).
I have created a screenshot with Vertical Tab Groups created as shown below. In this example, I have a overview of both the designer and the code view at the same time.
We can use tab groups whenever there is a dependency such as comparing code, redesigning a module, etc. I know it takes a little time to get used to this feature but try it out and see :)
Is it possible to view variable values in Eclipse when debugging? Right now when I "mouse over" a variable all I get is the definition.
e.g. for [int mLastView] I get [com.company.samples.MyClass.mLastView] instead of 1. The value that was assigned to it.
Also, is there anyway to improve debugging in Eclipse?
For starter: making the breakpoints visible as in VS (see below)?
Eclipse Break Point
Visual Studio Break Point
I posted this over at Stack Overflow and one of the suggestions was to go into Window -> Preferences -> Java -> Editor -> Hovers and select the Variable Values option and assign a modifier.
When I was first trying to resolve this issue, this was one of the options I looked at, but oddly enough, there was no Variable Values preference available, it was missing. Once my “fix” above was applied, it magically appeared:
Click to see the pictureBroken Link
Actually, since eclipse3.4, not only do you see the value of a variable when you pass the mouse over it, you can actually inspect it:
When debugging, hovers for variables have been enhanced to display an object inspector. The inspector will display logical structures according to the toggle setting in the visible Variables or Expressions view.
If you hit the breakpoint while you are debugging, you do see the value of the variable when you mouse over. You can also select an expression, and inspect the value of it's evaluation using the "Inspect" menu option. You can also use the "Variables" view to see the current value of all in-scope variables.
About breakpoint visibility:
Right-click on the right outline of the editor, you'll see some Preferences, and there in Annotations you can select Breakpoints. I personally added Text as Highlighted and some pinky colour. Shame that the highlighting is really buggy, sticks here and there, breaks between lines, etc. But it somehow works for most cases.
(Another shame is that breakpoint bullet is often hidden behind some suggestion icon or what - why they can't make the gutter wider like Idea does, I don't know.)
I got similar but a little different problem with the thread-starter. Sometimes during debugging, I mouse over a variable, I see it current value. Sometimes it's just the definition, like in coding mode. So what caused the first case, what the second?
PS: Of course I can always choose to view Variables (Alt+Shift+Q,V) but it's faster if you have mouse over value instantly.
Thanks
Okay, I'll bite.
I've got really pleasant code/window colors set up in Xcode. Ordinarily, my selection color is very visible.
When I am doing a project search and iterating through the results, however, the results list stays in focus and the found text remains out of focus, using a different background color. This color is extremely hard to detect, especially when the text is embedded in a larger code block and the view is shifting around as it scrolls to the results.
Here's an example:
Left side is in focus (just normal selection), right side is out of focus (during project find)
Often it takes a few seconds to find where the heck the selected text is.
Unless I'm just missing it, Xcode seems to offer no way to change this particular selection color. Interestingly, it also doesn't seem to follow the selection color from the Appearance panel.
Does anyone know a way to change this color or force it to be more visible, short of changing my entire color scheme around?
Use this Xcode plugin:
http://github.com/tjw/XcodeSelectionColorFix
Instructions for using it are here: http://github.com/tjw/XcodeSelectionColorFix/blob/master/README.markdown
You can manually edit the theme file, which might allow a different selection color. If I recall (not on my dev machine), personal themes are in ~/Library/Application Support/Xcode/(should be intuitive from here/can't remember)
You can edit them in Property List Editor, if I remember right. The Xcode preferences don't expose all of the options available in the theme file.
This is a GUI application (actually MFC). I need a command window with the ability to display a prompt like such:
Name of favorite porn star:
The user should be able to enter text after the prompt like such:
Name of favorite porn star: Raven Riley
But I need to prevent the user from moving the cursor into the prompt area. Users should also be prevented from backspacing into the prompt in order to prevent the following:
Rrraven Rrrileeey Ruuuulez!!! Name of favorite porn star:
Also need to control text selection and so on. And finally, I should have no problem retrieving only the text the user entered (minus prompt text).
Will it be better to create my own window class from scratch (i.e inherit from CWnd) or should I reuse the Windows EDIT control (i.e. inherit from CEdit)?
A similar command window can be seen in AutoCAD and Visual Studio (in debug mode).
I think you'd be better off creating a subclass of CEdit and limiting filtering key-presses. I suppose the hard part is not letting the user move the caret to the prompt area, but you can probably write some code to make sure the caret always get sent back to where it belongs (the input part).
Anyway, if you really, really want to implement your own control (it's not that difficult after all) I recommend you read Jacob Navia's "technical documentation" on how he built the LCC compiler and environment. Actually, it seems the docs are not online anymore, but I'm sure you can get them through his e-mail (jacob#jacob.remcomp.fr).
Edit: I liked your previous example better. Keep it classy, LOL :)
I had a very similar requirement and did exactly what davidg suggested; subclassed a edit control and filtered key presses. This was actually using Qt not MFC but the principle will be exactly the same.
You need to remember to filter keys such as home as well as left and backspace. I just checked to see if the move would move the caret into the prompt and if it did ignored the keypress.
Another thing to watch for is pasting multiline text, you will have to choose whether to just paste the first line or all lines, adding the prompt on all lines after the first. When subclassing the control you get lots of behaviour which won't work exactly as you want it.