Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6964841
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 27, 20262026-05-27T15:58:33+00:00 2026-05-27T15:58:33+00:00

Now with at least 300+ variations of manually created forms I’ve created in the

  • 0

Now with at least 300+ variations of manually created forms I’ve created in the past 5 years, I’ve never seen this problem. I have of course a main form, and then a bunch of smaller child forms. These child forms are not auto-create, they’re declared and created manually in my code. This project is still very premature, meaning there isn’t that much code in this project that I might be missing something. But the problem is, all I do is create the form, assign the parent to the main form, and without any code to show the form, it shows its self anyway.

FControlPanel:= TfrmControlPanel.Create(nil);
FControlPanel.Parent:= Self;

That’s all the code I have to create it. Absolutely no code is in the actual child form at all. It should take at least FControlPanel.Show for it to be visible, but for some reason it’s visible anyway.

I do have a hunch what might have caused this behavior to begin with. But I can’t put two and two together. I attempted to use the MDI form capabilities, to keep the forms within the main form. But after a number of trial/error scenarios, I gave up and set my properties back. The only properties I changed were the FormStyle – The main form I switched (for trials) between fsMDIForm, fsNormal, and fsStayOnTop. The child forms I switched them to fsMDIChild. After I gave up, I switched them all back to their default, fsNormal. It’s after this playing around when this “auto show” started happening.

Also, probably an important note, these child forms are inherited from a master form. This master form practically has no code either, at least no code which might show it. Nowhere in any of my code am I telling it to show these child forms, but it does anyway. And I know they’re not auto-creating.

What could I have done wrong?

PS – The problems implementing the MDI in general is subject to another question, I’m not asking about MDI but it may be what caused this to happen, as changing properties of components is known to permanently switch internal properties of the component, for example, on a TPanel, switching “ParentBackground” to true then back to false again causes it to properly show the specified color when using XPMan.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-27T15:58:34+00:00Added an answer on May 27, 2026 at 3:58 pm

    IIRC seting form’s style to fsMDIChild changes the Visible property of the form to True. So now whenever you create a form it is visible by default… change the forms Visible property back to False and it should end the “auto show” behaviour.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Let's say I have this array int[] anArray = { 100, 200, 300}; Now,
I have spent at least 2 weeks now trying to find out how to
I have jqGrid with enabled EDIT, DELETE, ADD and VIEW , Now my problem
I have created a table like this: CREATE TABLE #TEMP(RecordDate datetime, First VARCHAR(255), Last
I have at least 100 xml files each about 300 MB with email messages
Thanks to Oleg, my jqGrid now looks like this, and works fine. (my problem
In my application I have created 20 buttons with in a scroll view, now
It appears that ffmpeg now has a segmenter in it, or at least there
newthing = Link(user=request.user,last_updated=datetime.datetime.now()) However, this uses datetime , not the MYSQL now(). How can
I have a form that I validate it using the JavaScript. Now when I

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.