## Plotting – How do I set PlotRange-> All for data with uncertainties and prevent pruning error bars?

Mathematica 12 provides built-in plot support for data with error bars.

The following example looks good with the default settings:

``````ListPlot[Table[Around[i, 5], {i, 10}]]
``````

However, if I sit down `PlotRange->All`the error bars are cut off:

``````ListPlot[Table[Around[i, 5], {i, 10}], PlotRange -> All]
``````

Here's an example where PlotRange truncates error bars by default:

``````ListPlot[{Table[{i, Around[1/i, {-10, 10}]}, {i, -5.5, 5.5, 1.0}],
Table[{i, 3 i}, {i, 0.5, 5.5, 1.0}]}]
``````

and add `PlotRange->All` does not help either:

``````ListPlot[{Table[{i, Around[1/i, {-10, 10}]}, {i, -5.5, 5.5, 1.0}],
Table[{i, 3 i}, {i, 0.5, 5.5, 1.0}]},
PlotRange -> All]
``````

Is there a universal option to retrieve the full PlotRange for data with error bars?

## Probability or Statistics – Assign error bars for the y-intercept

Use the `Weights` Option with the inversion of the square of errors:

``````data = {{{1/10, 4.92997}, ErrorBar[0.00875039]}, {{1/20, 4.90374}, ErrorBar[0.00912412]},
{{1/25, 4.89318}, ErrorBar[0.00707122]}, {{1/30, 4.89534}, ErrorBar[0.00870608]},
{{1/40, 4.87807}, ErrorBar[0.00829155]}, {{1/50, 4.84442}, ErrorBar[0.0226886]},
{{1/100, 4.83867}, ErrorBar[0.0973819]}};
error = data[[All, 2]] /. ErrorBar[x_] -> x;
t = Table[{data[[i, 1, 1]], Around[data[[i, 1, 2]], error[[i]]]}, {i, Length[error]}];
lmf = LinearModelFit[data[[All, 1]], x, x, Weights -> 1/error^2];
lmf["ParameterTable"]
Show[ListPlot
``````

## How do I hide progress bars in PCManFM 1.2.5?

`````` I am having some problem with the PCManFM on my Lubuntu 18.04LTS. The "Copying Files" progress bar always appears on top of the viewer so everytime I want to navigate through the files I need to move it out the way, it won't let me hide it without hiding the viewer. I have my own reason that I need to search through the files while transfering files via FTP.
Since I don't have much experience with linux I don't know if there is any command or scripts that can do the job eventhough I would like to learn more about it. If it is just the nature of this FM I might consider changing to another lightweight one.
``````

## Labels of the r-X axis bound to histogram bars instead of following separate rules

If you use a histogram with x as the POSIXct value, I'm not sure how to align the ticks with the binsize of the chart.

If you set the tick size to the same size as the binsize, the line will shift slightly, but the offset will add up until it is no longer accurate.

``````until the month <- ggplot () +
scale_x_datetime ("", breaks = date_breaks ("60 days"), labels = date_format ("% m-% y")) +

...
Many geom_rects for background colors
...

theme (legend.title = element_blank ()) +

geom_histogram (data = dat, aes (x = iso, fill = name), binwidth = 30 * 24 * 60 * 60, position = & dodge & # 39;)
``````

I've tried experimenting with annotate () as well as the tick distance, but I think my approach here could be wrong by itself

This will cause a graph to look something like this

Graphic with staggered checkmark

Which is pretty annoying

## html – How to create navigation bars that are not unique to each page but universal?

I'm new here, so maybe I'm posting in the wrong place. Feel free to remove this.

I am relatively new to web design (back and frontend) and have a little question about navigation bars.

I've created a website where each button in the navigation bar leads to a new HTML document. Each HTML document has the same navigation bar, but if I suddenly wanted to add "About Us" to the menu, for example, I would have to do this in every single HTML document.

So how do you do that? Is there another way to handle navigation bars?

## Web App – scroll bars for an infinite layer

I design a web application to plan Minecraft builds. Basically, it's a pixel editor, except that each tile has a texture instead of a color. I turn to desktop browsers, although I want to keep tablets in mind.

One of my goals is to present the canvas as an infinite plane. (This is a key feature that distinguishes this design from existing alternatives.) The Minecraft world is infinite, so it makes no sense to specify a finite size in advance, and it's annoying a pointless hurdle.)

The canvas is zoomable and must be "scrollable" in both dimensions. The user should be able to view and edit any part of the canvas – even a million tiles away from the origin.

Scroll bars do not work perfectly here. The artboard has neither beginning nor end, and the origin point is not important to users, so there are no objective reference points. The filled-in areas of the canvas can serve as useful subjective reference points, and a scroll bar can be useful for navigating those areas.

I read a great question about infinite scrolling patterns, and although she did not deal with this particular case, it was very enlightening. After some consideration, I think that the application must support:

• Move the view to any given point.
• Move / zoom the view to include the entire padded area.
• Move the view precisely within and immediately outside the populated area (for example, a screen view, a measure that depends on the zoom).

A traditional scroll bar also gives the size of the view in relation to the entire document, which does not make sense to us. It might be useful to specify the size of the view in relation to the populated area, but I am not convinced.

Moving to a point or zooming / scrolling to see all the content can be implemented using buttons, menu commands, or whatever. The trick is to find a surface for scrolling behavior that is intuitive to use but meets the demands of the infinite level.

What I'm thinking at the moment is a kind of "peeling bar". Visually, it is a scroll bar (and can be implemented with native widgets). The button is locked in the middle when the user is not scrolling. If the user moves the button manually, the view is scrolled accordingly, and when it releases, the button jumps back to the center. This allows precise linear scrolling despite the lack of objective reference points.

As indicated, the user can not scroll over an unlimited distance in a single operation. To support this, the canvas area may be scrolled until the user releases the button or moves it away from the end.

Are there any good examples of infinite layer scrolling? And does the widget that I propose seem to be a reasonable compromise?

## nvidia – When moving windows and other objects, many flickers, black bars, and other visual disturbances were detected

That's why I've never used a Linux distribution and this is my first time that I've really dealt with things. Most of the time, I was able to find things for other problems or questions that I was just looking for online, but I seem to be missing out on this problem …

Let me first list what I use and what my specifications are.

I'm using Kubuntu 19.04 (64 bit) on my 7-9 year old gaming laptop (I know, I really need to upgrade). My laptop has a GTX 560M GPU (I use the latest NVIDIA legacy 390.116 driver), an Intel i7-2670QM CPU, and 16 GB of RAM. I also have a separate monitor connected to my laptop via HDMI, and use both the monitor and the screen of my laptop.

Here's a screenshot of one of the most common events: weird graphical glitch

I also have a lot of screen flickering when I open a new window or program, or even when a dialog box opens. Clicking out of the new window and then back in or moving to the other screen and then back to the other seems to stop the flickering, but it just happens again when a new window, program or dialog box is opened. I should note that it is not always the entire screen that flickers, sometimes it's 5/6 of the screen or a little less, and sometimes it's both screens.

I've tried a few different things, but nothing really did that problem. I really just hope someone has an idea of ​​what's going on and he can tell me what to do.

Many Thanks! 🙂

## Sales Order – Some bars are not loaded in Magento2 Admin

I added a customer group Column in the customer grid during order creation For Magento2, I filtered this grid basis according to two specific customer groups.

The customer grid works fine, but the module is affected by admin on some other grids. Example: The grid "Customer groups" in the customer menu is not loaded. The Themes grid and the Configuration grid in the Contents menu are also not loaded.

layout File is

``````[vendor][module] view  adminhtml  layout  sales_order_create_customer_block.xml
``````

Like this

``````

[vendor][module] Model  ResourceModel  Order  Customer  Collection

group
customer group

``````

Data Source Class is

``````[vendor][module] Model  ResourceModel  Order  Customer  Collection.php
``````

Like this:

``````joinField (
& # 39; # 39 ;, & customer group
& # 39; # 39 ;, & customer group
& # 39; # 39 ;, & customer_group_code
& # 39; customer_group_id = group_id & # 39 ;,
Zero,
& # 39; left & # 39;
);
return \$ this;
}
}
``````

di.xml

``````

``````

and this class is for filtering:

grid.php

``````getParam (\$ this-> getVarNameFilter (), null)) {
\$ this-> getCollection () -> addFieldToFilter (& # 39; customer_group & # 39 ;, array (& # 39; in & # 39; =>) ['retailer','wholesale']));
}
parent :: _ prepareCollection ();
}
}
``````

## Should progress bars accurately reflect how close the operation is to long operations?

I am creating a simple application. There is a specific operation that will take a very long time (~ 15 minutes), and I hope a progress bar will be displayed indicating how short the operation is to complete.

I've noticed that for some applications, progress bars are loaded slightly faster at the beginning than at the end. It may be due to the operation being performed, but it also appears to be a good strategy to keep the end user less frustrated, as it seems to load quickly, but in the end it does not go that fast.

Is this a good strategy to make users happier with long operations? What are the advantages and disadvantages?

## Dashboard – How do I show progress bars and value in a compact space?

Attempting to keep the number in the bar may give users information less fast, which corresponds to what a dashboard wants to achieve: insight into the status at a glance.

You can get more contrast by dragging the number up and zooming in. Then the progress is displayed as a contrast line, reserving the color just for the values ​​that are progressing.

I'm not sure what your other limitations are, but if the violet requires more contrast, you can make the text and the bar darker, but they can work visually as a unit.

It's easier to read an outstanding 7% than to calculate the fill position in the progress bar. Their current design is the other way around: The bar is prominent, but I'm learning the text.

Instead of two violet hues, gray stands for the lack of perfection.