gvSIG bugs #4118
The scripting engines initialization is delayed
Status: | Closed | % Done: | 0% | |
---|---|---|---|---|
Priority: | Normal | Spent time: | - | |
Assignee: | Joaquín del Cerro Murciano | |||
Category: | Scripting | |||
Target version: | 2.3.0-2426 (rev. org.gvsig.desktop-2.0.132, NOT USABLE) | |||
Severity: | Minor | Add-on version: | ||
gvSIG version: | 2.3.0 | Add-on build: | ||
gvSIG build: | Add-on resolve version: | |||
Operative System: | Add-on resolve build: | |||
Keywords: | Proyecto: | |||
Has patch: | Hito: | |||
Add-on name: | Unknown |
Description
The initialization of the scripting engines is not a startup task (like in gvSIG 2.2), but it happens only when there's the need to execute a script for the first time (e.g. an autorun script, if available). So the user has to wait some seconds before the execution of the first script.
Related to #4025.
Associated revisions
refs #4118, inicializacion de los engines de scripting al arrancar la aplciacion.
History
#1 Updated by Joaquín del Cerro Murciano over 8 years ago
- Target version changed from 2.3.0-2447-final (rev. org.gvsig.desktop-2.0.153) to 2.3.0-2426 (rev. org.gvsig.desktop-2.0.132, NOT USABLE)
- Assignee set to Joaquín del Cerro Murciano
#2 Updated by Joaquín del Cerro Murciano over 8 years ago
- Status changed from New to Fixed
#3 Updated by Antonio Falciano over 8 years ago
- Status changed from Fixed to Closed