Forum

Please note that you can subscribe to the individual forums. A subscription for news only covers the news.

Continued bug with ...
 
Notifications
Clear all

Continued bug with line writing for Version 4.1 beta 2

6 Posts
2 Users
0 Likes
1,004 Views
0
Topic starter

Hi Sven,

Sorry I'm late in testing this, but the bug with line writing has continued into 4.1 beta 2. The program now crashes when the writing assignment has been completed. 

 

[report-test line punishment]
punishmentgroup=test
punish=2

[punishment-Test line punishment]
text=
text=PUNISHMENT-TYPE LINES TO TEST- Deadline: {!zzdeadline}
group=test
grouponly=1
weight=3
value=2
min=2
Title=Write # lines to test
Type=Lines
Line=test

 

Chazz

6 Answers
0

Hi Chazz

Thanks for reporting this. It is fixed in the new beta 3.

Sven

0
Topic starter

Thank you so much Sven! I really appreciate it!

 

Chazz

0
Topic starter

Hi Sven,

I hope all is well. I received the below error after running the line writing punishment and the system crashed, but when I test it by itself it works fine. Any idea what might have caused it? 

 

Report from program crash:

we 14 2:45:40 PM Started Write "I want to be the best I can be." 4 times (Deadline 16-07-2021 2:44:32 PM)

we 14 2:46:29 PM "Page accepted"
we 14 2:46:31 PM Response time 1 second
we 14 2:46:31 PM "Your lines are accepted, "
we 14 2:46:32 PM Response time 1 second

we 14 2:46:32 PM Done: Write "I want to be the best I can be." 4 times

we 14 2:46:32 PM Write "I want to be the best I can be." 4 times lasted 51 seconds
we 14 2:46:32 PM Merits: +8, sum=825
we 14 2:46:33 PM Response time 1 second
we 14 2:46:33 PM You were punished for this reason:
we 14 2:46:33 PM   Being 4 hours 6 minutes 17 seconds late with Not doing the task assigned
we 14 2:46:33 PM   on 14-07-2021 2:44:32 PM
we 14 2:46:33 PM Access violation at address 0040C200 in module 'VirMst4.1 B3.exe'. Read of address 6E6F6970
we 14 2:46:33 PM > tDatamodule1.AppException

 

Punishment:

[punishment-Write Lines]
text=
text=PUNISHMENT-TYPE LINES - Deadline: {!zzdeadline}
MustStart=1
DeleteAllowed=1
group=test
value=4
min=4
max=10
; AnnounceProcedure=addpunishmentpoint
respit=2d
RemindPenalty=2,14
remindpenaltygroup=mod
; startprocedure=submerit50
Title=Write # lines about your owner
Type=Lines
Select=random
;Line=I want to be the best I can be.
Line=test

;=BLOCKED TO TEST

 

Test:

[report-LINE PUNISH ERROR TEST]
punishmentgroup=test
punish=2

 

Chazz

0

Hi Chazz,

It seems like what seemed to be a small change, to lock the window while writing lines, to prevent the sub from returning to the main window, was more complicated than I thought.

First it gave the previous error. And now this. I will try to recreate it using your information. And then hopefully be able to solve it.

Thank you for give so full information about what happened.

Sven

0

I have an idea for a possible cause. But I am absolutely not sure. And I cannot reproduce the error either. I will make some changes, that I hope will make the program more robust.

Has it happened more than once?

Sven

0
Topic starter

Hi Sven,

Sorry, it took so long to get back to you. Yes, it continues to happen but appears to be when combined with other aspects of the script. Using the sample test script does not reproduce the error. 

 

The crash error that came up this time was:  Access violation at address 0040B424 in module 'VirMst4.1B3.exe' Read of address 7570205C. 

I'll continue to test and see if there is any pattern. Please let me know if you need anything.

 

Thanks,

Chazz