1 Oct
2014
1 Oct
'14
5:10 a.m.
I don't like splash screen for the purpose of a splash screen (like ESET do) but I feel your pain if you have a slow computer and you don't know if Inkscape is actually starting up or not. The best solution I've seen to this problem is the one GIMP uses. They have a splash screen _with_ a loading bar for all modules and settings that are loaded during start up.
Just as Martin Owens says, something needs to be shown to the user in about 500ms otherwise another instance is started with another double-click on the icon.
Martin, what do you mean with a "build flag for a splash screen"? a loading bar just like GIMP?
--
Christoffer Holmstedt
2014-10-01 4:38 GMT+02:00 Martin Owens <doctormo@...400...>:
> On Wed, 2014-10-01 at 00:39 +0200, Johan Engelen wrote:
> > For me, a splash screen makes sense for start times above a second or
> > so.
>
> Actually two human ticks, so about 400 to 600ms is when people start to
> question if their action actually did anything and may prompt clicking
> on the icon again.
>
> But part of that is just every operating system in existence not telling
> the user that something is happening with an application they've asked
> to load.
>
> Maybe a build flag for a splash screen would be nice.
>
> Martin,
>
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.cl...
> _______________________________________________
> Inkscape-devel mailing list
> Inkscape-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/inkscape-devel
>