471,348 Members | 1,169 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,348 software developers and data experts.

invisible gui

I have a program that process files on a hard drive. Everything works fine,
it shows a progress bar as it processes the file. The problem occurs when I
have the program look for files to process on startup. The gui is invisible
untill it processes the files it finds as it startsup. After which it
appears and everything works normally when the next file needs to be
processed.

Is there anyway to tell the program to not look for files untill the
interface is visible? I need a method like onGUIAppears.
Thanks in advance.
Jun 27 '08 #1
5 1417
On Thu, 15 May 2008 18:01:25 -0700, Dave <DW**@newsgroup.nospamwrote:
I have a program that process files on a hard drive. Everything works
fine,
it shows a progress bar as it processes the file. The problem occurs
when I
have the program look for files to process on startup. The gui is
invisible
untill it processes the files it finds as it startsup. After which it
appears and everything works normally when the next file needs to be
processed.

Is there anyway to tell the program to not look for files untill the
interface is visible? I need a method like onGUIAppears.
It's difficult for me to understand how your GUI can show progress if the
processing begins after the GUI is shown, but not before. Perhaps you've
made a mistake in your initialization by starting the processing before
some specific initialization within the GUI is done. The question of
visibility shouldn't matter.

That said, you can override OnShown() in your form class to know when the
form is actually being shown and delay your processing until that point.

Pete
Jun 27 '08 #2
You misunderstood, I mentioned the progress bar as a reason to why I wanted
to see the form before processing begins. You CAN NOT see the progress bar
on startup.The files are processed correctly even though you can't see the
progress.

I beleive the OnShown() will do what I need. Can you post a short example on
how to use this?

Thanks,

Dave.

"Peter Duniho" <Np*********@nnowslpianmk.comwrote in message
news:op***************@petes-computer.local...
On Thu, 15 May 2008 18:01:25 -0700, Dave <DW**@newsgroup.nospamwrote:
>I have a program that process files on a hard drive. Everything works
fine,
it shows a progress bar as it processes the file. The problem occurs
when I
have the program look for files to process on startup. The gui is
invisible
untill it processes the files it finds as it startsup. After which it
appears and everything works normally when the next file needs to be
processed.

Is there anyway to tell the program to not look for files untill the
interface is visible? I need a method like onGUIAppears.

It's difficult for me to understand how your GUI can show progress if the
processing begins after the GUI is shown, but not before. Perhaps you've
made a mistake in your initialization by starting the processing before
some specific initialization within the GUI is done. The question of
visibility shouldn't matter.

That said, you can override OnShown() in your form class to know when the
form is actually being shown and delay your processing until that point.

Pete

Jun 27 '08 #3
On Thu, 15 May 2008 22:14:31 -0400, "Dave" <DW**@newsgroup.nospam>
wrote:
>You misunderstood, I mentioned the progress bar as a reason to why I wanted
to see the form before processing begins. You CAN NOT see the progress bar
on startup.The files are processed correctly even though you can't see the
progress.

I beleive the OnShown() will do what I need. Can you post a short example on
how to use this?

Thanks,

Dave.
Something like this should do:

using System;
using System.Windows.Forms;

class Class1 : Form
{
bool firsttime = true;
protected override void OnShown(EventArgs e)
{
if (firsttime)
{
firsttime = false;
// ##put your code here##
MessageBox.Show("I've been shown! (for the first time)");
}
base.OnShown(e);
}
static void Main(string[] args)
{
Application.Run(new Class1());
}
}

If you need more help, you'll need to post some code. Please follow
this guidelines:

http://www.yoda.arachsys.com/csharp/complete.html

Mach
Jun 27 '08 #4
Hi Dave,

When a Form is loaded, it's Load event is fired first. The Form won't show
until all lines of code in its Load event handler finish executing. After
that, the Form's Activated event is fired and then the Shown event.

If the Form does some time-consuming work in the Activated or Shown event
handler, the UI of the Form will be blocked, i.e. all controls on the Form
are not painted properly or not responsive. This is because the main UI
thread is busy and doesn't have a chance to paint/refresh the UI of the
Form.

To show a Form and then do some time-consuming work without blocking the
UI, I suggest that you do the time-consuming work in a separate thread. You
can create a Thread instance or call the BeginInvoke method on the delegate
to the time-consuming method to do it, if you're using .NET 1.x.

If you're using .NET 2.0, I recommend you use the BackgroundWorker
component, which provides a concise multiple-threads programming model and
is very easy to use. You can start a BackgroundWorker in the Form's Load
event handler in your practice.

For more information on how to use the BackgroundWorker component, please
refer to the following MSDN document:
http://msdn.microsoft.com/en-us/libr...backgroundwork
er.aspx

Hope this helps.
If you have anything unclear, please feel free to let me know.

Sincerely,
Linda Liu
Microsoft Online Community Support

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
ms****@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Jun 27 '08 #5
Hi Dave,

How about the problem now?

If the problem is still not solved, please feel free to let me know.

Thank you for using our MSDN Managed Newsgroup Support Service!

Sincerely,
Linda Liu
Microsoft Online Community Support

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
ms****@microsoft.com.

This posting is provided "AS IS" with no warranties, and confers no rights.
Jun 27 '08 #6

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

3 posts views Thread by Jose_Csharp | last post: by
reply views Thread by Fir5tSight | last post: by
5 posts views Thread by my.shabby.sheep | last post: by
1 post views Thread by Ronak mishra | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.