Task #7718 (closed)
Missing jar
Reported by: | jburel | Owned by: | jburel |
---|---|---|---|
Priority: | minor | Milestone: | OMERO-4.4 |
Component: | Insight | Version: | n.a. |
Keywords: | n.a. | Cc: | jamoore |
Resources: | n.a. | Referenced By: | n.a. |
References: | n.a. | Remaining Time: | n.a. |
Sprint: | 2012-04-24 (13) |
Description
Currently if insight hangs during the init process (e.g. missing jar), the user does not know why. A force quit is required.
Let the user knows and shuts down.
Change History (3)
comment:1 Changed 12 years ago by jburel
- Milestone changed from Usability Backlog to OMERO-Beta4.4
- Sprint set to 2012-04-24 (13)
- Status changed from new to accepted
comment:2 Changed 12 years ago by jburel
- Status changed from accepted to closed
comment:3 Changed 12 years ago by jburel <j.burel@…>
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
(In [364a5485e7bf0ee2c104810342a569751605c624/ome.git] on branch develop) Exit splashscreen (see #7718)
Exit splashscreen when an error occurred during the
initialization sequence e.g. when a jar is missing.