How do I enable this view? To show current cursor position (line, column) and number of selected characters? I think I've checked all possible values in the settings, yet I still do not know where to find it.
If you don't see the position and selection count, it is probably the case that you have too much items in the status bar. Disable the ones are not relevant to you by right clicking on the status bar:
Also if you don't use your entire screen width, they also disappear if there isn't enough real-estate. Unfortunately I don't think there is a way to set priority to the items.
Please follow these steps
View -> Appearance -> Show Status Bar
It looks like the functionality you ask about was added quite recently. Here it is said that "line number and column number are shown in version 1.46, May 2020. On selection, they disappear."
Related
I am currently using the Ag-grid enterprise angular version 20.2.0 in a project and we cannot find an option to deselect already selected cells during the range selection. In addition to that, I cannot find any information about that option in the given doc. https://www.ag-grid.com/javascript-grid-range-selection/.
Is there any possibility to deselect cells with ctrl and another key or do I have to create a feature request, so that they may implement that?
Just as further information, we use the api.getRangeSelections() to process and visualize the given values in a custom status bar component. We expect that customers demand to exclude unexpected data instead of deselecting everything and restart from scratch.
Thank you in advance for your assistance :)
Very good question. After a quick research on the doc, I can recommend you to enable advance range selection, and prompt users that they can exclude their selection only if they go around the cells they want not to select.
For example:
Here above, I selected cells with 'advance range select' ( CTRL + selection ) and remained a cell none-selected. Before I start to select with range, I figure it out which one I am not going to select, so it becomes easier to manage cells to be none-selected.
Go and experience yourself with this link: https://www.ag-grid.com/javascript-grid/range-selection/#example-range-selection-advanced
Others have asked this question before, but no one has provided an actual answer to it. I can't get all of the marks/labels to display in my Tableau visualizations.
Selecting "allow labels to overlap" does not fix the problem. That displays several hidden labels for the smallest of the areas, and it places those labels at the top of the bars, ignoring the formatting that sets the labels to the bottom. However, whether or not that option is checked, the empty areas in the screen shot stay empty. And those areas are clearly large enough to display the missing labels without encroaching on any other label.
I'm guessing this is a bug in Tableau because there's no reasonable explanation as to why this is happening, but I'm new to Tableau and unsure how to address this.
While I can offer no explanation, this has been a reported problem for several years. Tableau's own documentation states to check the Allow marks to overlap checkbox, yet that doesn't always work.
I don't know if it's a bug so much as it is a complicated calculation for the rendering engine to determine what will and won't fit into a space. To the human eye it will fit but it's possible the underlying calculations inside Tableau don't see it that way. I find that particularly on dual-axis charts (like yours) this happens more frequently. I've done two things to get around it when it comes up:
Change font family or font size
Put more info into the tooltips so the end user sees the data when they hover.
If you wish to pursue this as a bug, you will need to contact Tableau Support and file a case. They will ask you to submit a twbx file to reproduce the issue.
I hope that helps.
Label -> Font -> Automatic solved the problem for me
You can select individual marks, right click to pop up a menu, and specify whether to always hide or always show the labels for the selected marks (overriding the default behavior)
The tracks in my timeline are massive. If I max out the window on my 15" macbook I can see 9 tracks in total. Is it possible to change their height somehow?
I feel like this should be possible as I've seen screenshots where they are a lot smaller, but nothing I do seems to work. Zooming only works on x-axis and there doesn't seem to be any scale handles at the edge of the tracks...
Use Crtl + mousewheel to change height of track...
I just ran into this problem, too. Although there seems to have no direct way to change the track height, I found a way modify the preference file of Timeline editor.
Find a file located under your project's Library/Timeline folder (its name should be xxxxx.pref), open it with a text editor, change the number after trackScale to 1, and you should be fine.
Screenshot: Timeline preference screenshot, the left one has trackScale of 1, whether the right one has trackScale of 3.79
You can scroll through using mouse wheel.
Last time I checked, the height was not changeable. You may have seen Track Group.
Also, a good idea is to group the tracks. To add a Track group, click the Add button and select Track Group from the Add menu. You can also Right-click an empty area of the Track list and select Track Group from the context menu.
More about this: https://docs.unity3d.com/Manual/TimelineOrganizingTrackGroups.html
When using a browser in my progress application the scroll bars never work correctly. It will show that I can only scroll down a little but then keeping going. Is this a bug in progress or is there something I can do to fix this problem?
define query browse-4 for customer.
DEFINE BROWSE BROWSE-4
QUERY BROWSE-4 NO-LOCK DISPLAY
custNum name
/* ENABLE name */
WITH NO-ROW-MARKERS SEPARATORS SIZE 32 BY 6.46 FIT-LAST-COLUMN.
.
open query browse-4 preselect each customer no-lock.
enable browse-4.
wait-for window-close of current-window.
You can adjust the MAX-DATA-GUESS property for the browse. You can get the value from NUM-RESULTS after the preselect query has been opened. Or you can set it to a suitable guesstimate without using preselect.
Keep in mind that using preselect causes every record to be read instead of just enough to fill the first browse window. That is potentially a lot of extra DB reads and network traffic just to get the scrollbars correct.
You may be confusing the scrollbar on the containing frame with the scrolling of the browse.
Do you see two boxes outlining the browse? If you add "with no-box" to your "enable" does the scrollbar that is bothering you go away?
If it does then the problem is that your containing frame (which is the default un-named frame because you have not specified a frame phrase with the ENABLE) is smaller than the browse viewport. So you are seeing a scrollbar on the FRAME, not on the BROWSE, that is trying to tell you that you can scroll the frame up and down to see the complete viewport of the browse. The browse may also scroll within that containing frame depending on how much data there is.
If you are running this code in a character (Unix) environment you should also be aware that many GUI features of the BROWSE are not available. Especially anything related to appearance. Like scrollbars.
This is a known "feature" of Openedge GUI, unfortunately.
The position of the slider on the right of the browse is not directly related to the number of records in the query, but to the "Max Data Guess" property of the browse.
You can set this value yourself in the property dialogue for the browse widget (it's just below the "query" editor, in v10 at least).
Just set it to a really big number (say 10,000) and the browse will behave as it should.
the main problem for my question is mainly ,i am deleting temptable before completing the excecution,that is the main reason for the vertical-scrollbar is not working,after eleminating this temp-table deletion statements .automatically vertical-scrollbar is working.
for each ttdummy:
delete ttdummy.
end.
Short version: I have a working solution using a UISegmentedControl but I don't like how it looks. When I use Safari, it "dims" either previous or next when it's at the beginning or end of the list of input fields. I can't convince a UISegmentedControl to do that, so how did they do it?
Long version:
I have a UITableView with cells that have text fields. The text fields take numeric inputs (floating point numbers, generally). That means I present the keyboard with keyboardType = UIKeyboardTypeDecimalPad. That also means no return button, so I need a good method to move between cells OTHER THAN touching the cells. I'd like to do it the same way as, say, iOS Safari does it - with a little toolbar that says "previous | next ... done."
I have code that does all of that (sets the textField.inputAccessoryView to be an instance of a UIToolbar with the appropriate buttons), using a UISegmentedControl for the previous and next button. I have that working so that next moves to the next cell and previous moves to the previous cell.
So why am I here? I can't get the dimmed previous/next behavior seen in iOS Safari to work with a UISegmentedController and I don't really want to implement all of that myself if I don't have to (at that point, my CCB will invoke one of the two rules it uses to reject changes: Rule 1) If I don't think it's a good idea, then I won't implement it; Rule 2) If it's easy, I'll probably do it).
(I would have posted pictures, but I'm too new to SO - sorry)
When I try to do the same thing it looks and acts like a Safari middle text field, but I can't seem to get it to look like the Safari version of first or last text field.
I've tried enabling, selecting, even changing the bar background color, but none of them seemed to work. The background color seemed to get closest, but I had to have 3 different toolbars based on when it was first, last, or middle, and even then it wasn't great.
Solved. The issue was that the "enabled" setting of the various segments as set in IB does not make it to the executable. I have to programmatically disable the previous or next segment in the view controller. Once I did this, it now appears as I want it.
When I set up the UISegmentedControl in IB, I set one segment to enabled and the other to disabled (== not enabled). In the debugger I started trolling through the settings of the various segments and found that actually setting the segment to disabled makes it work in the way I wanted.
For example, in the "nextToolbar" that contains a UISegmentedControl that is attached to "nextControl," only the Next button should be shown as active. That means I have to set the Previous button to disabled. The Previous button is at index 0, so disabling it means to do this somewhere before it's used (I put this in viewDidLoad:):
[self.nextControl setEnabled:NO forSegmentAtIndex:0]
Similarly, for the prevControl, where only the Previous button should be active, I use:
[self.previousControl setEnabled:NO forSegmentAtIndex:1]