MMF 2 - Static text and SubApp Bug Found

[droberson]

I believe I have found a bug or conflict between static text control and subapp control within an application set to MDI.

First, creat a new appliction. Add a static control and change the background color to blue. Now add text and enlarge and bold it. So background of static box is blue and text is black.

Now, change the application to MDI in the properties box.

Run the application and you should see the frame background is gray with scrollbars and the black static test with a blue background.

Now create another new application. Add an RTF box. and save it.

On the first application add the SubApp control and tell it to use the second application. Make the windows style:
popup, clip siblings, border, dialog frame, resizable, caption, tool caption.

Run the first application. You should now see the blue static text box and you should see the second application as a subapp.

Now drag the sub app over the static box test and see it change the background color from blue a light yellow of the static text on the first application.

Is this a bug???? I was able to repeat it. Could someone confirm???

[droberson]

This is a real problem for my application. It is a form and I changed to MDI to be able to have scroll bars on the windows. But this bug is messing up all of my static text boxes.

[Yves]

Could you post yor example in the File Archives forum? Thanks.

Yves.

[droberson]

The examples are in the file archives. Bug - Subapp and Static text.

[Yves]

Thanks for the files.

Well, it's an odd use of the MDI option... This option is intended to be used in conjunction with MDI Child sub-applications. Why do you use this option?

If you don't need this option, unselect it and just do a Set Frame Background Color (Storyboard object, build 243) with SysToRGB( "Background System Box", MDI background( "Background System Box" )). Note: if you do that and select the "No display surface" option in the frame, the window background won't be refreshed, it'll be fixed in the release version of the build 243.

Yves.

[droberson]

Well as you see I needed the scrollbars. But in a normal (non-MDI) window I could not have scrollbars. There was no scrollbar object or window property at the time. (I see a beta version of EasyScrollbar is coming out.) The form (frame) is larger than the window and really scrollbars should just appear by default with an option in the properties windows to turn them off.

Bottom line, scrollbars need to be added to the normal window as a property you can turn on and off.

Really I was using this application to see how easy it was to create a simple form with a couple of popup windows for note taking and adding new list items to lists. Then I wanted to be able to encript the information and store it in an XML file that is sent over the internet to a server for processing. I did not want to write anything to the hard drive of the local machine since I wanted to be able to distribute the form via Vitialize, so everything take place in memory. That's the project. It has been a challenge due the number of objects needed and lack of documentation for objects, but I feel I am getting close. Without the forum and help form others on the forum this would have been impossible. I wanted to use this as a demo with a school I am working with. I also plan to write up some MMF tips and tricks for other users about some of the objects used here and use this as an example application.

I am not nearly as good at MMF as others but I love the product and have been follow its growth for several years. I would like to see faster release of updates, patches and fixes. But I assume there is a reason for putting them into a release version as a group.

Anyway thanks for help in getting this tracked down.

[droberson]

Yves, this bug was to be fixed in 243. But I have the build 244 latest beta but I still has the problem.

Any update on when it might be fixed or if scroll bars will be added the normal frame so I don't need to use MDI?

Thanks

[Yves]

No, I didn't say this would be fixed, I just said that the refresh problem in the workaround I mentioned would be fixed. The MDI option shouldn't be used for that.

I don't know when the scroll bars will be added for normal frames, it's in the "to do" list.

[Gerblegod7]

We shouldn't really be holding Clickteam to anything we think they say. They are busy enough. They have had 5 updates in 5 days, and the ever impending question of when is Vitalize!4 being released? i am sure I am not the only one who respects Clickteam and realizes that a lot is on their plates.

[droberson]

Yves, thank you. I misunderstood your orginal reply. I didn't understand you were referring "only" to the refresh problem.

I agree the MDI is an odd way to solve the scrollbars on the window problem, but 3 motnhs ago there was not another option, not even a scrollbar object. That's why I was hoping scrollbars could be turned on in the normal window just like in the MDI window and the refresh problem corrected. Then I would have used the normal window which is what I origianlly tried. But as the MMF2 documentation says: "there are lots of way in MMF to address a problem and don't be afrid to experiment"...and this was the best way I could find at that time and presently also.

Gerblegod, I was not trying to hold clickteam to anything and I was just asking, after 3 months, the status of something that is important for my applications. (I deal a lot with forms.) If there was a status report showing "what is on the to-do list" I would have looked there butI am not aware of one existing.

Do you have a suggestion on how to find out information without asking?

Your reply seems to imply I "disrespect" Clickteam and do not "understand" they have a "lot on their plates". If that is the case I can assure you that is not true.

I have a great respect for Clickteam and the work they have done. That is why I have been a loyal customer for several years. I stated in my post 3 months ago:

>I am not nearly as good at MMF as others but I love the product >and have been following its growth for several years. I would >like to see faster release of updates, patches and fixes. But I >assume there is a reason for putting them into a release version >as a group.

>Anyway thanks for help in getting this tracked down.

Sorry if you took my post the wrong way.