Hi @aly22, yes that process is normal. The upgrade used to be automatic, but it was failing for some users due to the plugin filename changes. Personally, on my own systems I had no problems at all. But apparently other users were. Possibly due to different hosting setups, etc. I actually tested on 7 WordPress installs before release! Just goes to show you that you can never be too sure.
As a result, I decided to make the system manual in v18.104.22.168. Again, not ideal, but at-least it was guaranteed to work when the user did click the import button. If they failed to do so, simply no slideshow would show. If they were logged in as the admin, they'd get an error message. Un-obtrusive, so users visiting the site wouldn't know that anything was wrong.
The styling options were held back for the initial release of v2.0. I'm working on adding them as we speak, with a new visual editor. I'd hope to have it added and released as v2.0.2 soon, possibly before the end of this week. However, I think the priority at this moment in time is to nail of the teething problems and bugs. Nearly there.
You should be able to style the slideshow yourself using CSS. The new version has been designed to be much easier than before to re-style. If you are finding that certain CSS properties aren't being applied, try adding ' !important' to the end of the value to override the defaults. As you can imagine there is a lot of structural CSS (that can be a little tricky to override) in place to make sure the slideshow is structurally sound from the word go.
You can also always style it entirely yourself by disabling the styling via the "Settings" Easing Slider admin menu. Grab the core slideshow CSS yourself from the 'slideshow.css' file, then do the rest yourself, if you're feeling adventurous!