Hopeeveryone is well. I have an error message on my store that says: Liquid error (Layout/theme line 80): internal. As a result it does not load up and the preview is greyed out. Can someone that can help please assist.
I think I must be misunderstanding something about the line = argument in theme(). According to the documentation in ?theme, line = is supposed to affect all line elements in the plot. However, changing the color doesn't do anything, while changing size does work.
The elements do inherit as advertised, however, they might have parents in between child panel.grid.major.x and grandparent line. This is for example the case for the theme_gray(), which is the default. To test this, you can manually set all theme elements with 'empty' elements. Like so:
As for why your theme(line = element_line(color = "green", size = 5)) doesn't change the color of any lines in the plot, it sets a default color for lines, which can be overriden. It seems like the default theme_grey() overrides the default line color for every type of specific line (major and minor panel grid lines which are the axis lines, axis tick lines, etc.), though some of the sizes must use the default or are set relative to the default, which is why the panel grid lines get huge with your size = 5.
I hate to ask such a stupid question but I am relatively new to Obsidian. I presume to update the theme one re-installs and overwrites the existing theme. Is that correct or is there another way to update themes that I am not aware of?
If you add update_geom_defaults("line", list(size = 1.75)) to the file where you store your custom theme, your geom defaults will also update when you source() your mycustomtheme.r file, and you'll get the linetype you want. Note that setting defaults this way only changes the exact geom specified (line), and does not affect line elements in other geoms (boxplot borders, error bars, etc.), so you will need to define geom defaults for each individual geom you plan to use.
I thought maybe I had used the wrong field type. So I tried defining new WYSIWYG fields and copying the text from the multi-line field to the new WYSIWYG field, still no line breaks displayed on the front-end. The text looks fine on the back end.
Themes are a powerful way to customize the non-data components of your plots:i.e. titles, labels, fonts, background, gridlines, and legends. Themes can beused to give plots a consistent customized look. Modify a single plot's themeusing theme(); see theme_update() if you want modify the active theme, toaffect all subsequent plots. Use the themes available in complete themes if you would like to use a complete theme such astheme_bw(), theme_minimal(), and more. Theme elements are documentedtogether according to inheritance, read more about theme inheritance below.
grid lines (element_line()). Specify major grid lines,or minor grid lines separately (using panel.grid.major or panel.grid.minor)or individually for each axis (using panel.grid.major.x, panel.grid.minor.x,panel.grid.major.y, panel.grid.minor.y). Y axis grid lines are horizontaland x axis grid lines are vertical. panel.grid.*.* inherits frompanel.grid.* which inherits from panel.grid, which in turn inheritsfrom line
Alignment of the plot title/subtitleand caption. The setting for plot.title.position applies to boththe title and the subtitle. A value of "panel" (the default) means thattitles and/or caption are aligned to the plot panels. A value of "plot" meansthat titles and/or caption are aligned to the entire plot (minus any spacefor margins and plot tag).
The position of the tag as a string ("topleft","top", "topright", "left", "right", "bottomleft", "bottom", "bottomright")or a coordinate. If a coordinate, can be a numeric vector of length 2 toset the x,y-coordinate relative to the whole plot. The coordinate optionis unavailable for plot.tag.location = "margin".
The placement of the tag as a string, one of"panel", "plot" or "margin". Respectively, these will place the taginside the panel space, anywhere in the plot as a whole, or in the marginaround the panel space.
should strip background edges and strip labels be clippedto the extend of the strip background? Options are "on" to clip, "off"to disable clipping or "inherit" (default) to take the clipping settingfrom the parent viewport.
facet labels (element_text(); inherits from text). Horizontal facet labels (strip.text.x) & verticalfacet labels (strip.text.y) inherit from strip.text or can be specifiedseparately. Facet strips have dedicated position-dependent theme elements(strip.text.x.top, strip.text.x.bottom, strip.text.y.left, strip.text.y.right)that inherit from strip.text.x and strip.text.y, respectively.As a consequence, some theme stylings need to be applied tothe position-dependent elements rather than to the parent elements
set this to TRUE if this is a complete theme, such asthe one returned by theme_grey(). Complete themes behavedifferently when added to a ggplot object. Also, when settingcomplete = TRUE all elements will be set to inherit from blankelements.
Theme elements inherit properties from other theme elements hierarchically.For example, axis.title.x.bottom inherits from axis.title.x which inheritsfrom axis.title, which in turn inherits from text. All text elements inheritdirectly or indirectly from text; all lines inherit fromline, and all rectangular objects inherit from rect.This means that you can modify the appearance of multiple elements bysetting a single high-level component.
My cover image has a feint grey line under the image (see attached) that I don't seem able to remove. I have tried different screens and added _NOPROCESS_ to the file name, but nothing is working. It happens with all images in that orientation in that theme.
Sorry to hear that you ran into this issue. Would you mind sharing a copy of the image file that you're using for your cover so we can test the behavior? Alternatively, you can reach out to our support team by opening a case here and we'll be glad to take a look at your Rise 360 course in its entirety to see if have any fixes available that we can share.
This is the image I am using which is an iStock photo.
I tested increasing the title of my course Kelly, and that didn't remove the line in this case.
I have produced a lot of courses using the Apex theme, and like you, did not experience this problem before.
Hello, thanks for your response. In my case, I am not using an image file for the cover. My cover is just a single colour using the Apex theme. When I increase the length of the course title the line disappears. But there is a line appearing when I decrease the length of the course title to between 1-3 words.
Sorry for the trouble with the unwanted line. I appreciate you sharing the screenshot and the image! The good news is that I do not see that issue in my tests using the latest version of Google Chrome.
If you're already using the latest version of a supported browser, please try clearing your browser cache and see if it helps. If the issue persists, could I have you connect with us in a case so we can determine what's happening? We'll reach out soon after we hear from you.
Renae, apologies I totally thought that was a regional spelling like color/colour, we have such a diverse community here. This is a recent video where I show how to add a Theme Component (css file) to your exported SCORM package. =MbLjv4mkuA8
Robert McKee (STORY) calls it the Controlling Idea. John Truby (THE ANATOMY OF STORY) calls it the Theme Line. I call it a Thematic Statement. It is a sentence that takes a broad theme and condenses it to give a particular story a particular meaning.
Theme is the big concept of your story: love, honor, justice, betrayal, loyalty, family, courage, duty. A Thematic Statement refines the broad idea to address your Story Question. In doing so, the Thematic Statement guides your characters in every choice they make and helps you, the writer, by providing a moral framework.
In the new RStudio you can create and download new themes. Does anyone know if there is a way to increase the line spacing?
I'm trying to use the theme editor from herokuapp, but I don't see any line spacing options.
Hi All,
.JSON file is a preset of settings, right?
Situation->
So, I've included in the file, that the lines should default to "Stepped".
Funny thing is it actually PREVENTS you from changing it to something else. Well, you can change it to "linear", but the change won't actually happen on your screen. It will be "hardcoded" to stay as stepped.
Question -> Did anybody had a similar issue with ANY other field in a .JSON file? Is it a bug? Should it work like this?
Maybe this is an idea for improvement instead if others in App Studio are experiencing this issue - I've attached what this chart looks like outside of app studio, you can see clearly defined colors are set as default:
I can't recreate this. Changing the custom colors in App Studio does change the colors in a line chart. It looks to me like you have "Gradient" colors turned on for the card, so I would double check that, because any color settings manually entered in the card will overwrite any styles applied by the color palette in App Studio. Maybe the card you're looking at outside of App Studio isn't actually the same card, but a duplicate that doesn't have gradient colors turned on?
I am writing regarding the theme builder option. I am having a difficulty to adjust the line height in the main menu; I cannot find the option do so. I am using Overlay Main Menu or Empty Menu Style.
But it appears the formatting doesn't allow any linebreak. When I tried writing on the line below it, the text won't appear. I tried adding /n as a mean to add linebreak, but the /n/ wasn't read as linebreak.
Is it not possible to add linebreaks in Wordpress theme's description? I think linebreaks may be useful when theme designer wants to outline something in points/bullets (what I've been trying; that is I want to outline several features of the theme).
3a8082e126