Prevent Visio 2016 from creating curve connector bend points?

I have a state machine diagram that consists of a series of shapes, and many curve connectors that connect from the center of one shape to somewhere on the radius of another shape. There are many cases where for two shapes A and B, there are multiple connectors that connect the center of A to the radius of B. I have two problems:

  1. When I create a new connector, visio always uses a straight-downward initial angle for the connector, even if the destination shape is above the source connection point.

  2. Visio always creates excessive amounts of bend points in my curves, especially when it has to bend over backwards to accommodate an initial downward angle, and each of these bend points must tediously be deleted so that changing the initial angle doesn’t make the curve look insane.

  3. When attempting to move the shapes themselves, visio replaces the bend points that I deleted.

The deal breaker is really point 3 above, since the only reason I’m even putting myself through using Visio is to allow for changes to the layout, but when it completely changes the structure of the connectors like this the value is lost.

Is there a way to prevent visio from adding bend points to my curves? I really only want the angular controls at each of the connection points, with no bend points unless absolutely necessary. At present I don’t know that that necessity exists.

How do I prevent section from breaking vwcol?

Here is a minimal example that works:

documentclass{article}
usepackage[english]{babel}
usepackage{vwcol}
usepackage{lipsum}

begin{document}
  begin{vwcol}[widths={0.6,0.4},sep=1.0cm,justify=flush,rule=0pt,indent=1em]
    lipsum[1-3]
  end{vwcol}
end{document}

enter image description here

But when I add section, things get messed up:

documentclass{article}
usepackage[english]{babel}
usepackage{vwcol}
usepackage{lipsum}

begin{document}
  begin{vwcol}[widths={0.6,0.4},sep=1.0cm,justify=flush,rule=0pt,indent=1em]
    section{A Section Header}
    lipsum[1-3]
  end{vwcol}
end{document}

enter image description here

My guess is that section is somehow asserting its width (and thus the first column’s width) across the whole page, while the second column continues to compute its width based on the erroneous first’s.

How can I fix this?

How to prevent other roles from publishing content

I am new to Drupal. I am working on a website where I have 2 user roles: Site admin and editor.

The site admin has all permissions. I want the editor to only have the permission to edit content but not to publish or edit them. He can view his edited content but cannot publish them.

Different people suggested me different options, like use this module, use that module, but no body is showing me a neat and proper solution.

How do I prevent/hide the snap folder of Chromium in my home directory Ubuntu 18.10?

When I open Chromium I see in my home directory that there is a snap folder from Chromium browser, and when I remove the snap folder I see my bookmarks are gone!

How can I change this directory or hide it? By the way this happens also with the calculator!

Edit: even cookies are gone!

chromium in file browser

I created a .hidden file and inside it I typed s for snap, but nothing happened!

home directory in file browser with hidden files

home directory in file browser without hidden files

cat .hidden shows s

How will Flatpak prevent proliferation of out-to-date libraries?

With the current package system (RPM or Deb), there is usually only one major version of each library and program installed. All libraries should use Semantic Versioning, so new minor versions can easily be installed without breaking anything. If there is a security issue, the library is fixed and all dependent code directly benefits from the patch.

Now with Flatpak I see that people will just bundle everything, perhaps because they have slightly modified the upstream library. If there is a security update, all upstream developers need to update the library. Even with the “runtime” concept, an app could still depend on an outdated version of the library.

To me, dependency hell only comes from a lack of API stability discipline. If the libraries would properly keep their APIs stable or issue a new major release, it would all be just fine. In the Ruby and Python world I often see that there are lists of requirements with exact version numbers. All that is installed into a virtual environment and will never be updated once the software is deployed.

How is Flatpak going to prevent the proliferation of convenience copies of libraries with security issues?