Issue 117709 - Assertion "Class: String, Id 57. Cannot load resource!"
Summary: Assertion "Class: String, Id 57. Cannot load resource!"
Status: CLOSED FIXED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: DEV300m103
Hardware: PC Windows NT
: P3 Normal (vote)
Target Milestone: ---
Assignee: Mathias_Bauer
QA Contact: issues@framework
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-06 06:42 UTC by Mathias_Bauer
Modified: 2017-05-20 10:32 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
suggested patch (615 bytes, patch)
2011-04-06 07:52 UTC, Mathias_Bauer 		no flags Details | Diff
patch for second assertion (634 bytes, patch)
2011-04-06 07:52 UTC, Mathias_Bauer 		no flags Details | Diff
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Mathias_Bauer 2011-04-06 06:42:49 UTC 
found in CAT0 test case tFileSaveWithPassword in w_updt.bas
Comment 1 Mathias_Bauer 2011-04-06 07:16:50 UTC 
In the same context we get the assertion "Dialog::StartExexcuteModal - Parent not visible"
Comment 2 Mathias_Bauer 2011-04-06 07:52:01 UTC 
Created attachment 76283 [details]
suggested patch
Comment 3 Mathias_Bauer 2011-04-06 07:52:25 UTC 
Created attachment 76284 [details]
patch for second assertion
Comment 4 Mathias_Bauer 2011-04-06 08:20:22 UTC 
When the Modify Password was implemented, a string was forgotten. I added this string in cooperation with fl. As this happened after localization freeze, I only added an English string.

The second assertion was caused by the fact that the parent of the error message dialog was the password dialog. As the error message was shown after the password dialog has been executed, the latter was invisible. I changed the parent so that the error message gets the same parent as the password dialog that will reappear shortly after the error message has been closed.

@mav: please review the second patch
@fl: please check the error message in the first patch
Comment 5 mikhail.voytenko 2011-04-06 08:36:26 UTC 
The second patch looks good.
Comment 6 frank.loehmann 2011-04-06 12:01:08 UTC 
First patch looks good too.
Comment 7 Oliver-Rainer Wittmann 2012-06-13 12:32:16 UTC 
getting rid of value "enhancement" for field "severity".
For enhancement the field "issue type" shall be used.