Course loading/buffering circle

Hi Howie.

Are you sure you uploaded the right picture? All I see is a black Windows 10 desktop...

You must be talking about the spinning "wheel"?

Hmm, there's a feature request here so I'm afraid the answer is "NO"...

https://community.articulate.com/discussions/articulate-storyline/changing-color-of-preloader

Exactly. The buffering circle is a very dark grey.

Hi Howie,

I'm also not sure I'm looking at the right image...could you share a link to the course? That way we could at least see if we're able to replicate the same behavior! 

Hi Ashley,

It's just the spinning preloader color, actually!

That's it Pierre. Due to the colour of my screen being black, it's very hard to see. If you look closely on the picture, it is there. 

It's not that i'm saying there's a fault with the course, there isn't, i just wanted to know if it was possible to change the colour of the spinning pre-loader?

I don't think you can, it would be good if it was content aware and changed colour

Ahhh thanks Pierre! I was starting to think my eyes or my mind were really going...

There isn't a way to change that preload spinner color though - so if you've got a course with a transparent or non-existent player I could see how that could cause this display issue on a dark screen.

The reason that i am asking if it was possible is because I've built some training which is being used by staff in bars/restaurants.

The staff are mainly doing these on a tablet and the broadband speeds in these places are pretty erratic meaning that the loading circle's quite important as it lets the user know that the course is still working and not just frozen. 

I can't change the background colour as it is part of the company branding. 

I have found on tablets that I show a layer that says loading before the jump to next slide sometimes that helps in this situation. But looks like on your screen shot it is that part of the load where it blanks the screen

The main issue i have is with the test at the end. The LMS i'm using doesn't work great with ipads so when you click submit, it looks for a couple of seconds that it's frozen. Due to the delay, the users can sometimes assume they've not clicked the button properly and then press it again which causes it to crash. 

Phil, when you suggest another layer,  would i be right in assuming  you attach a trigger to the player button (in my case submit) and then get it to jump to the next screen when the timeline on the layer ends? 

I normally show layer when user click next and jump to slide when user clicks next, this way the layer shows with loading on screen and then it sits there for a while as it preloads but more often than not loading is on screen

This isn't foolproof as sometime it jumps to a blank screen first and other times the layer does not show. I had the same problem with dark screens and slow loading and an invisible spinning wheel.

Thanks Phil.