In Visual Studio 2019, using the Enhanced Scroll Bar, red square dots in the scroll bar's right-most column highlights where there are errors in the code. However, I have other red dots, smaller (half width, half height, approximately) in the left-most column of the scroll bar, or possibly at the very right end side of the editor window (?).
What do they represent?
Related
I have a simple 0-100 range of values representing percent using HorizontalBar and the TChart (Embarcadero edition) appears on a ScrollBox in this FMX app because I don't like the panning behavior I've seen in this Delphi 10.3.3 app for Windows. But the use of the ScrollBox means that sometimes the Bottom Axis is not visible, so I would like to have its Scale repeated as the TopAxis Scale.
Just having the Visible box checked for the Scale of the TopAxis does not produce the desired result.
Currently, I have a crude work-around that uses a separate chart that only exposes its BottomAxis Scale, positioned as a TopAxis Scale in the TChart that shows the data.
Is there a way to specify having the same scale on the bottom and top of one TChart?
On the series set the general option "Horizontal Axis" to Top and Bottom and for "Vertical Axis" to Left and Right.
The Apple Documentation has shown me how to place constraints between objects that are apart from each other in the view, like here. However, what if you have a display element that is contained inside of another, as shown below:
Is it possible to set constraints that will "trap" the gray square within the red square?
Make sure you have set the necessary constraints for the red box and place the gray box inside the red box.
Red box constraints:
In my case i want the red box in center of the screen with fixed width and height.
Gray box constraints:
Trapped inside the red box with the distance of 64 all side.
You can make the gray square a subview of the red square, then constrain it to the red square, which will be its superview.
The specific constraints would depend on how you wanted the gray square to size itself in relation to the red square.
I am creating an app for my kid:
The image has 5 section, each in a different color. Each section has a black box on each side of the section.
What I want to do is when touching a black box in a section I want that section to vertical flip around and in the process of flipping I want the whole screen to follow flipping vertical to a new screen.
Ex) I press the left black box in green section. The green sections starts to vertical flip around (to the left or counter-clockwise) its axis in the middle of the section. And when it has flipped/turned some 10 degrees I want the rest of the sections to follow and when all sections has flipped a new all green page is shown.
I hope I made it clear what I want. Is this possible? How can it be done in Swift?
I have seen the vertical page flipper but I want a bit more stylish:). I have seen other samples with flipping an image, but not this two-part flipping.
Thanks to all clever people,
Micael
I have now been bashing my head against this problem for a couple of hours and figured it was time to ask somebody else.
I have 2 views that must be the same size, within these two views there are 2 boxes (green and blue in the pictures below), which are of variable sizes, and a box (pink'ish) that is fixed size.
Here is a sample image:
The green and pink boxes are set to be at the top, and the blue box floats underneath them. The blue box should never be further down than 15pt from the lowest of the other two boxes. This means that if the green box becomes smaller (as seen in the next image), then the blue box should stay 15pt from the pink box.
Lastly, since the cells are fixed height then if the blue box becomes smaller, then it should stay at the other boxes, but leave space below itself to fill out the rest of the view (since it must be as big as the view next to it), as I tried picturing here:
The key point here is that we are working on the smaller view of the two.
(The green and blue boxes are both labels with text that must be at the top of the box.)
The best solution I've come up with is to add:
green.bottom >=15 blue.top
pink.bottom >=15 blue.top
blue.bottom >=15 superview.bottom
But I get an "Inequality Constraint Ambiguity" between them, because inequality is not "good enough".
You need to add two more constraints between the blue view and the green and pink views. The should be,
green.bottom == 15 blue.top priority 900
pink.bottom == 15 blue.top priority 900
Your >= constraints have the default priority of 1000, meaning that they are required. This will ensure that neither view is ever closer than 15 points to the blue view. Adding these new equal constraints with a lower priority, means that the system will try to satisfy them, but it doesn't have to. This will result in the system satisfying which ever of those two equal constraints that it can, without violating the >= constraints.
I'm not exactly sure what constraint you need to the bottom of the view (from the blue view) since I'm unsure what size you want it to be.
I have a jasper report set to portrait letter, which, in pixel terms, translates to 612 x 792 in iReport. I have the left margin set to 17 pixels and the right set to 10. That leaves the single column width at 585 with no spacing.
Now, I have two vertical lines that are used to form the report's border, and they're positioned at x-coordinates 0 (for the left bar) and 585 (for the right). When this reported is executed, the resultant PDF looks perfectly fine. However, when I go to print, the two vertical lines are missing, and I have to select shrink to fit (which sets the zoom to 94% and displays everything).
I've done some experimenting, and, without shrinking the report at print time, the vertical lines need to be positioned at x-coordinates 2 (for the left) and 575 (for the right) in order to display, which translates into essentially an x-margin of 19 pixels. Playing around some more, if I set the left margin to 19, the left vertical bar displays at print time when positioned at x-coordinate 0.
Is something else setting the margins at 19 pixels aside from the jasper report itself? I can't find any culprits in the report itself that seem to be responsible for the discrepancy. Any help is greatly appreciated.
Most printers can't print up to the edge of a page. It sounds like you are hitting this limit. The print driver is detecting that the PDF doesn't fit inside the printer's printable area and allows you to shrink the content to fit what the printer supports.
This is just a guess. In my reports I use the Background-Band in iReport and draw a rectangle for the background of my reports.