Jump to content
Xtreme .Net Talk

Photovoltaic

Members
  • Posts

    14
  • Joined

  • Last visited

About Photovoltaic

  • Birthday 04/11/1986

Personal Information

  • Occupation
    Government Pot Farmer
  • Visual Studio .NET Version
    Visual Studio .NET 2003 Pro
  • .NET Preferred Language
    VB.NET

Photovoltaic's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. You don't necessarily need a DVD-/+RW drive, but it's a good idea to invest in at least one drive that can read DVDs. Microsoft is starting to distribute larger software (e.g. VS.net 2003) in DVD format; who knows what that will affect. You can purchase a DVD-ROM/CD-RW combo fairly cheaply right now. The big-screen is great isn't it...I have a 61" with 10 speakers...I love it so much I'm sleeping in the TV room now :)
  2. I've raised this issue several times with McAfee during the beta testing process. They refuse to do anything about it, so the only thing I do is disable ScriptStopper.
  3. Run services.msc, and check if the Machine Debug Manager service is disabled. If it is, enable it. If that doesn't solve the problem, check if the Event Viewer has any additional information.
  4. In Windows 2000 and up, the indicators are hidden until you use the ALT key, or Windows otherwise determines that you are using the keyboard to navigate. I guess Microsoft thought it was ugly...:)
  5. It's so simple I guess no one bothered to put it on the Internet :). Just set the form's TopMost property to True.
  6. Did you ever get EnableVisualStyles() to work? Try using it with a new project; add a button and once you get the XP styles to work, add the flash object and see what happens. There's been a few times when .net 2003 has just quit working for me (won't load my controls, won't indent, etc, and sometimes it even makes VB case-sensitive).
  7. Did you set all the controls' FlatStyle property to System?
  8. VB 2003 has native support for visual styles. Try setting each control's FlatStyle to System, then use Application.EnableVisualStyles() in your startup form, i.e.: 'right after #Region " Windows Form Designer generated code " Public Shared Sub Main() Application.EnableVisualStyles() Application.Run(New Form1) 'where Form1 is the name of your form End Sub
  9. Me.Width = Me.MinimumSize.Width Me.Height = Me.MinimumSize.Height
  10. But this event will be fired EVERY time the user switches back to that form, not just when the form is first shown. You should be able to make the Form_Load event Public, then when you do frm.Show (assuming you've Dimmed the form somewhere), use frm.Form_Load after it. Since my notebook with .Net installed is out for repairs, I have no way to test this.
  11. Are you talking about the screen resolution? You shouldn't change the user's resolution unless you are making a fullscreen application. What doesn't work in your app?
  12. Are you using the same key each time? If so, try another one (it might be a keyboard issue). You could replace the code in your timer with the Beep() function, change the interval to 100, and check to see if the time it takes to stop is always the same or if a pattern appears.
  13. What if you use the KeyUp event?
  14. If ListView1.SelectedItems.Count = 0 Then varTheIndex = -1 End If
×
×
  • Create New...