Forum Discussion
SVG File Issues
I'm having trouble incorporating .svg files to my storyline file. When I add the .svg files (Picture 1), the color and fill is perfect on the screen. When I preview/publish the file, the fill seem...
When i preview the slide on its own its fine, however when I preview the whole project that's when the issues I mentioned happens.
Hi Michael! Sorry to hear you're still having issues with SVG files after trying some of the suggestions provided by the community.
Are you currently using the latest version of Storyline 360? Here's how to check:
- Open an existing Storyline project or create a new one.
- Go to the Help tab on the Storyline ribbon and click About Articulate Storyline. Find your version details on the screen that appears.
Please check if you're using the latest version, Build 3.63.27674.0. If you still have issues, please submit a copy of your file and a sample image, along with some short details of what you've already tried by submitting a case to our Support Engineers directly.
Yes, that was obviously one of the first things I checked. I still have the issue. I have raised an issue with support and sent over a file.
Great! We'll continue assisting you in the support case!
Hi Renz,
Can someone from Articulate take a look at the latest conversation in this post between Jurgen and me about SVG and buttons. It appears that buttons and images use states differently. Where in plain images states are used properly and the normal state is hidden/removed so its not visible in a hover in buttons this is not the case.
Would be best if this would be changed like it is in image states...as you create a hover you want the normal state hidden.
Further more when using SVGs this way it doesnot work like this. Both in images and buttons the normal state always shows. Ideally you donot want that. You want only the actual state shown.
Jurgen Schoenmeyer gives a really nice comment on why they work differently. Whether this is a bug report or a feature request im not sure. Leaving that up to you to decide ;-)
Thanks in advance.Hi Math
I came across this issue myself recently and spoke to one of the articulate engineers. They are acknowledging it as a problem, but I don’t know of a fix in the works.
At the moment, for me, SVGs seem to be too unpredictably supported for me to use them. I swapped them out for PNGs in my current project because they were so broken.
Nic
Thx Nicola, and allthough SVGs are part of the issue... another issue really popped out in the discussion between me and Jurgen. The different approach of buttons and images with states.
Do check especially my 'no button with transparancy png.story'
Attached here too. In that one you can see ( and readup the cause of it in Jurgen's explanation ) that buttons are treated differently then images with states. In fact both are the same...they both can have triggers and thus act as buttons.
Issue is that buttons will always show the 'normal' state. Also when in hoverstate or whatever. Thus limiting the use of transparant pngs, because then you always need to use opaque images. When you recreate a button by just using images.. as you can see in Review here...and the .story... it works the way buttons are meant to work with pngs. Transparant in any state.
https://360.articulate.com/review/content/104cacc8-fa22-4b73-95fb-2c7a3f141d65/review
