I would like to set up a conditional rule that hides a visualisation if the base size is less than 10.
Any help is much appreciated.
Under the format visual options there is a tab called Rules, although I cannot work out how I would use this to this ends.
Related
We are a 3rd-party vendor that adds components / UI elements to our clients' websites. We sometimes hide/change the size of this container in run-time, based on contextual parameters or as part of A/B testing.
It is impossible for the website owner to know the final size of the element before we have all the contextual data, so the height cannot be set on the server-side.
To minimize the effect on CLS, the website owner can set an initial height for the container, but this has two issues:
It does not completely eliminate CLS, only reduces it slightly
It creates a bad UX where the page loads up with a white space which then disappears / changes height
What is the recommended approach for eliminating the CLS impact of such an element?
We sometimes hide/change the size of this container in run-time, based on contextual parameters or as part of A/B testing.
Any time you change the size of content at runtime, you risk shifting other content on the page around, and that can negatively affect the use experience. Before you spend a lot of time trying to "fix" CLS for your use case, you might want to consider whether your use case if the right experience for users.
If you cannot change your system and just want to minimize its impact on CLS, here are some options:
Collapse the area only after user input (perhaps ask users to close the container, or, wait for some other expected reason for page re-layout).
Only collapse if all affected content is outside of the viewport. It sounds like you already do this for below-the-fold? For above-the-fold content, you may be able to simultaneously remove content and adjust the scroll position by the exact same amount.
And, perhaps some broader alternatives are:
Don't collapse the area, but replace it with some default content that cannot fail.
Likely not an option, but maybe there are ways to delay showing content until you know if the conditional content will be needed? This depends on how late loading your content is and will have negative tradeoffs with loading performance if you cannot answer that success test quickly...
a bit background
I am currently using the clHighlight color together with a StyleServices.GetSystemColor call to set the background color of controls that are:
not focused
have a NULL value (field.IsNull=True)
and are about a required field (field.required=True)
Its not about how to do the highlighting itself, I figured that out already.
Currently I am using system color clHighlight, but this makes confuses my users as they think the entire contents of the field is selected (see screenshot).
But I also have style support implemented, so using a custom predefined color is not really what I am looking for. after googling a bit I found quite a list here https://learn.microsoft.com/en-us/dotnet/api/system.windows.systemcolors?view=netframework-4.7.2 but I am unable to find what I am looking for.
Using RAD studio Rio 10.3.1 Enterprise.
The actual question
So - what system color should I use? (not really looking for subjective suggestions, but for a more or less "officially recommended" constant to use.)
a screenshot
Answer: There is no more or less system color constant defined for this specific purpose.
Solution/workaround:
Thanks all for the suggestions. I decided to go for the clInfoBk constant (background color for hint windows), this looks far less confusing. One could interpret the color as a "hint" for fields that need to be filled out.
And it looks like this, in the default color scheme:
My crosstab looks fine in the web viewer but when I export to PDF it's clipping it like showin in the image. It's also making the columns much wider than they need to be. (The web version isn't doing that.)
Does anyone know how to fix it? I tried searching for an answer and didn't see anything.
Without seeing the parameters you're passing to your RenderTask it is hard to tell exactly, so I'm going to guess that you have PAGE_OVERFLOW set to CLIP_CONTENT rather than FIT_TO_PAGE_SIZE.
A note of caution though. This discussion on the Eclipse forum mentions that page-break interval settings might override the page size render options. Note that the OP on the linked discussion was having a problem with the PDF exported from the HTML viewer.
EDIT: according to the docs inside genReport.sh you are able to pass parameters on the command line (-p pageOverflow=FIT_TO_PAGE_SIZE) or you can create a parameter file (-F params.txt)
It is unclear to me whether you can pass the constant (FIT_TO_PAGE_SIZE) or must pass its expected value (2), so you might have to try both.
I think you have restricted the width/height of your report
goto Master Page then click on the general settings and there you find the type drop-down choose Custom.
Through this custom options you can give your own height/width of your report and too in the report layout.By doing this you can expand your report width
NOTE: The master page width should equal to the width of your layout.
I want all my inno set up pages to look like below :
The small wizard image is accessible using WizardForm.WizardSmallBitmapImage which is of type TBitmapImage.
You can change the size and position of this control to suit your design (within the top panel). You can also hide/reposition the labels (WizardForm.PageNameLabel and WizardForm.PageDescriptiontLabel) in the same way.
As for the extra fields, see this question.
I have text objects on a Crystal Report in Visual Studio with an initial capital. When I print the report, the text is all lower case.
And the reason is?
We have found a workaround for this problem. Not sure how this works :) - can any expert explain?
We found that this problem of case change was happening whenever the extent of text within any page / section of the report was going beyond the settings of the page size minus gutter, left/right margins, top/bottom margins set for the report.
As a workaround, we have asked all our reports developers to keep the text (for A4 size reports) to within 7.5 inches X 7.5 inches. The problem does not happen when this is adhered to.
Would definitely like to know exact reasons for the misbehavior though.
This might be affecting by some of the settings.
But if you go and edit the field , you can see it automatically change to lowercase.
If you agains change it back your case, then it will work fine.
It looks like it happend for one time. To be honest, I don't know why this happend