SphereServer BugTracker - SphereServer
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001692SphereServerexecutable - genericpublic19-12-09 01:1919-12-09 16:00
ReporterTerrikate 
Assigned ToMrSugarCube 
PrioritynormalSeveritycrashReproducibilityalways
StatusresolvedResolutionfixed 
PlatformOSOS Version
Product Version0.56c Nightly 
Target VersionFixed in Version0.56c Nightly 
Nightly VersionNot Available
Experimental FlagsNone
Option FlagsNone
Internal Build Number
Summary0001692: Another strange problem with the execution of the following function
DescriptionBuild #1186

The following script doesn't work, at least not always.

SAVED FORCE

- Displays a dialog indicating that the server is being saved.
- Make the save.
- Close the previous dialog
Steps To Reproduce
Additional InformationIn other versions, it works.

[FUNCTION forzar_save]
SERV.ALLCLIENTS F_COMIENZO_SAVE
SERV.SAVE
SERV.ALLCLIENTS F_FIN_SAVE

[FUNCTION F_COMIENZO_SAVE]
TRYSRC <UID> DIALOG d_guardando

[FUNCTION F_FIN_SAVE]
TRYSRC <UID> DIALOGCLOSE d_guardando

[DIALOG d_guardando]
250,250
nomove
gumppic 100 10 5573
dtext 95 80 156 Guardando...

[DIALOG d_guardando BUTTON]
ON=0
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
19-12-09 01:19TerrikateNew Issue
19-12-09 01:19TerrikateNightly Version => Not Available
19-12-09 01:19TerrikateExperimental Flags => None
19-12-09 01:19TerrikateOption Flags => None
19-12-09 16:00MrSugarCubeStatusnew => resolved
19-12-09 16:00MrSugarCubeFixed in Version => 0.56c Nightly
19-12-09 16:00MrSugarCubeResolutionopen => fixed
19-12-09 16:00MrSugarCubeAssigned To => MrSugarCube
19-12-09 16:00MrSugarCubeNote Added: 0000338

Notes
(0000338)
MrSugarCube   
19-12-09 16:00   
Fixed the problem where DIALOGCLOSE isn't working when placed directly after DIALOG, but I suspect this script is still not working as desired because of the new network system which will queue up the packets until after the save completes.

To try to force the packets to be sent earlier you can either insert some kind of delay (TIMER/TIMERF) before starting the save, or change f_comienzo_save to use the FLUSH function:

[FUNCTION F_COMIENZO_SAVE]
TRYSRC <UID> DIALOG d_guardando
FLUSH