Dear Martin,<o:p></o:p>
<o:p> </o:p>
We confirm that the problem your reported exists. It occurs in some particular situations when control bars are organized in some complex layout. It never occurs when control bars are organized in some simple layout, for instance, if all the control bars are docked vertically on left and each is single in its column of bars. All the bars in this case can be hidden or visible. The most important thing is that this simple layout does not have deep level nested splitter bar containers. This problem does not occur with dynamic resizable control bars (see SDI_DynamicBars sample application) because all the just allocated bars are organized in some simple layout like discussed above and state re-loading typically means re-allocation of all the bars because number of bars in different states can be different. We need additional time to find some appropriate solution.<o:p></o:p>
<o:p> </o:p>
Please do not hesitate to contact us if you have any questions.<o:p></o:p>
<o:p></o:p>
Best regards,
Technical Support Team<o:p></o:p>
<o:p></o:p>
FOSS Software, Inc.
Phones: (603) 894 6425
(603) 894 6427
Email: support@prof-uis.com<o:p></o:p>
<o:p> </o:p>
Sent: Thursday, February 21, 2008 6:10 PM
To: support@prof-uis.com
Subject: Re: Serialization bug: loading an archive file<o:p></o:p>
<o:p> </o:p>
Dear ProfUIS-Team,
just for my info: could you reproduce the described behaviour? Thanks in advance.
Martin
################################ First message #######################################
Dear ProfUIS-Team,
sorry for your inconvenience because of my holey description of the problem. ;-)
As an attachment you’ll find three archives that are used in the following procedure.
First of all, I have tried to load your archive_01.FPX and it works like shown in the image you sent me. Loading it immediately after the first load works without problems, too.
But on a second glance, I found out how to disturb the correct behaviour of loading that archive by performing the following steps:
1. Start Application from scratch after preceding deletion of archive_00.FPX (is ok, uses defaults)
2. Load archive_01.FPX (is ok, same as shown in your image file)
3. Load archive_02.FPX (is ok)
4. Load archive_03.FPX (is ok, should look similar to correct.jpg)
5. Load archive_03.FPX immediatly once more (is not ok, should look similar to INcorrect.jpg)
6. Load archive_01.FPX second time (is not ok, compared with original PNG)
It’s obvious that something in the constellation of archive_03.FPX confuses the loading of archive_01.FPX. Please note that step 5. is not necessary at all to disarrange archive_01.FPX. In contrast, replaying step 3. several times never leads to a bad result.
Would you please try to follow this procedure step by step using the attached archive files?
Best regards,
Martin
Prof-UIS Technical Support Team schrieb: <o:p></o:p>
Dear Martin,<o:p></o:p>
<o:p></o:p>
We compiled and run your application successfully. We found nothing wrong. The archive_01.FPX state file restores the main frame maximized state when others are restoring in the normal state. The single monitor computer was used in the test and monitor resolution was enough high - 1440x1050. All the state files do not contain description of floating bars.<o:p></o:p>
<o:p></o:p>
We tried to save/load different bar layouts using your test version of our sample application and everything was OK independently from the number of floating bars. Could you please describe some step by step actions which we should perform to reproduce the problem.<o:p></o:p>
<o:p></o:p>
Here is attached the ZIP file with the control state data file and PNG screen shot made on 1440x1050 single monitor desktop describing what you should get when restore the control bar state from the file saved on our computer. Please note, if you will restore our state file on a computer with smaller resolution desktop, then Prof-UIS will change positions of floating bars which are outside the desktop to make them visible.<o:p></o:p>
<o:p></o:p>
Please do not hesitate to contact us if you have any questions.<o:p></o:p>
<o:p></o:p>
Best regards,
Technical Support Team<o:p></o:p>
<o:p></o:p>
FOSS Software, Inc.
Phones: (603) 894 6425
(603) 894 6427
Email: support@prof-uis.com<o:p></o:p>
<o:p></o:p>
Sent: Friday, February 15, 2008 8:12 PM
To: support@prof-uis.com
Subject: Serialization bug: loading an archive file<o:p></o:p>
<o:p></o:p>
Dear ProfUIS-Team,
there appears to be a bug with floating window persistence if loading an archive file. We could reproduce the buggy behaviour after having implemented the archive load/save features in your ProfStudio sample application. I’ll immediately send you the corresponding souce code attached to an email for support@prof-uis.com.
The inconsistency especially appears when loading the file archive_01.FPX not only once but twice.
Best regards,
Martin <o:p></o:p>
<o:p> </o:p>