Windows 8.1: 2.0.3-rc3 throws invalid string position on some sets

[halian]

When attempting to open some MTG set files (examples attached) using Cajun's Mainframe 2020 template pack, fully updated, on MSE 2.0.3-rc3, I get the following error:

[Window Title]
Error

[Main Instruction]
An internal error occured:

[Content]
invalid string position
Please save your work (use 'save as' to so you don't overwrite things)
and restart Magic Set Editor.

You should leave a bug report on http://magicseteditor.sourceforge.net/
Press Ctrl+C to copy this message to the clipboard.

Call stack:
[00] 00007FF6464D6A17
[01] 00007FF64696C486
[02] 00007FF64690AF20
[03] 00007FF646902BE1
[04] RtlCaptureContext                       
[05] 00007FF64647657C
[06] 00007FF6466C3AD4
[07] 00007FF6466F27D4
[08] 00007FF6466F3A03
[09] 00007FF6466F26D8
[10] 00007FF646555CCE
[11] 00007FF6466F272C
[12] 00007FF6466F355A
[13] 00007FF6465FC809
[14] 00007FF646604202
[15] 00007FF6465319E6
[16] 00007FF64660158A
[17] 00007FF646601E30
[18] 00007FF64654422C
[19] DispatchMessageW                        
[20] MsgWaitForMultipleObjects               

[OK]

I reported it to him first and he said it was a Twan issue.

[CajunAvenger]

Will pitch in a few bits. I've not run into this issue with any of my files, but I do get the warnings when I try to open Halian's files on any 2.0.2 build, and not 2.0.1.

On the rc-2 build I get a much shorter error:

[Window Title]
Error

[Main Instruction]
An internal error occured:

[Content]
invalid string position
Please save your work (use 'save as' to so you don't overwrite things)
and restart Magic Set Editor.

You should leave a bug report on http://magicseteditor.sourceforge.net/
Press Ctrl+C to copy this message to the clipboard.

Call stack:
[00] 0158069F
[01] 014EC2AF
[02] wxAppConsoleBase::CallEventHandler      


[OK]

and on the rc-3 build I get a similar but different one than Halian, but do get the same one on all four files.

[Window Title]
Error

[Main Instruction]
An internal error occured:

[Content]
invalid string position
Please save your work (use 'save as' to so you don't overwrite things)
and restart Magic Set Editor.

You should leave a bug report on http://magicseteditor.sourceforge.net/
Press Ctrl+C to copy this message to the clipboard.

Call stack:
[00] 000000013F9F6A17
[01] 000000013FE8C486
[02] 000000013FE2AF20
[03] 000000013FE22BE1
[04] RtlRestoreContext                       
[05] 000000013F99657C
[06] 000000013FBE3AD4
[07] 000000013FC127D4
[08] 000000013FC13A03
[09] 000000013FC126D8
[10] 000000013FA75CCE
[11] 000000013FC1272C
[12] 000000013F8E2D7E
[13] 000000013F99657C
[14] 000000013FBE3AD4
[15] 000000013FC127D4
[16] 000000013FC13A03
[17] 000000013FC126D8
[18] 000000013FC1355A
[19] 000000013FA5329B
[20] 000000013FA5A3BB

[OK]

and rc1 gave a very different stack:

[Window Title]
Error

[Main Instruction]
An internal error occured:

[Content]
invalid string position
Please save your work (use 'save as' to so you don't overwrite things)
and restart Magic Set Editor.

You should leave a bug report on http://magicseteditor.sourceforge.net/
Press Ctrl+C to copy this message to the clipboard.

Call stack:
[00] 015C2AAF
[01] 01535DFF
[02] wxAppConsoleBase::CallEventHandler      
[03] wxEvtHandler::ProcessEventIfMatchesId   
[04] wxGCDC::ReleaseHDC                      
[05] wxToolBar::MSWCommand                   
[06] wxWindow::HandleCommand                 
[07] wxTopLevelWindowMSW::MSWWindowProc      
[08] wxFrame::MSWWindowProc                  
[09] ImageList_Duplicate                     
[10] ImageList_Duplicate                     
[11] InitCommonControls                      
[12] gapfnScSendMessage                      
[13] GetThreadDesktop                        
[14] GetClientRect                           
[15] CallWindowProcW                         
[16] wxWindow::MSWDefWindowProc              
[17] wxWindow::MSWWindowProc                 
[18] wxToolBar::MSWWindowProc                
[19] KiUserCallbackDispatcher                
[20] GetThreadDesktop                        

[OK]

[twanvl]

The issue is triggered by the cycling keyword, on a card with normal cycling. It happens with this set because it has its own copy, while normally typecycling appears after cycling.

It is still an MSE bug.