Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - TomTech71

Pages: [1]
1
Newbie / Re: Greetings From A DarwinBots Newbie...
« on: August 13, 2014, 01:34:13 PM »
It helps if the interface is programmed to be friendly to the User...and maybe some instructions...

I got indication that a cutoff date for current update work development is upon us.

My first contribution was a bug-fix. This one is a feature enhancement.

In code comment, and on the forum, I see a desire for a better indicator for SunStatus. I desperately needed that as well.

Here is a simple, but very effective solution.

* Plant a PictureBox on the MDIForm. It will probably try to set just below the toolbar, which is great: That's where I want it.

MDIForm1 Form File Control Parameters:
============================================
Begin VB.MDIForm MDIForm1   
  Begin VB.PictureBox picSunStatus
      Align           =   1  'Align Top
      BackColor       =   &H00FF0000&
      BorderStyle     =   0  'None
      Height          =   80
      Left            =   0
      ScaleHeight     =   75
      ScaleWidth      =   14295
      TabIndex        =   10
      Top             =   420
      Width           =   14292
   End
End
==============================================


* In the Vegs.feedvegs Subroutine, place one line of code at the end of the routine. Ends up looking like:
==============================================
    End If
    Next t
getout:
    MDIForm1.picSunStatus.BackColor = IIf(SimOpts.Daytime = True, &HFFFF&, &HFF0000) <++++++ ADDED LINE
End Sub
==============================================

What results is a thin color bar just below the toolbar, stretching the entire length of the parent form. Shows a dark (night) color when the sun is down, and yellow (obvious) when the sun is up. Is visible no matter what size and position the MDI form takes. Is not intrusive. Works Great For Me.

I'm very busy reverse-engineering this package (when I'm not busy just playing with it). I'm creating my own executable, descendants of the latest package, with enhancements and corrections for testing. I'm already enjoying using the software more with the changes I've made.

Tom

2
Newbie / Re: Greetings From A DarwinBots Newbie...
« on: August 06, 2014, 01:23:03 PM »
The OCX issue is the usual Common Control registration. Not an issue to clear up.

(laughs) Sorry...Misuse of the word 'dissertation'. It's just a bunch of bullets and such with a programmers 'User' perspective as I found myself obsessed with playing with DB2 when I discovered it a month ago. Quirks, unfriendly things, bugs, "why is it programmed this way"...things like that. In programming projects, I'm known as the 'front-end' programmer. Always putting emphasis on the user iteration with the program. The minute I realized I would want to get involved, I started jotting down notes as I played.

Installing VB6 on Win7 (32 and 64) is not an issue if you know the trick: Install the base program, then SKIP installing SP5, which introduces MDAC issues, and go straight for SP6B. Done this on several Win7 machines, and actively program VB6 at work and at home, both on Win7.64.

DB2 is already very standalone. I even run it from a stick no matter where I am. That's one reason I press the local-referencing for paths and such. To ensure it stays that way.

Tom

3
Newbie / Greetings From A DarwinBots Newbie...
« on: August 04, 2014, 07:18:36 PM »
I discovered this wonderful software a few weeks back....

Let me introduce myself....

In the following Darwin2.47.03 VB6 function:

MIDIForm1.loadpiccy_Click()

It is noted: "for some reason this doesn't work. I have given up on it for now"

Make the following changes:

    CommonDialog1.InitDir = App.path

Always, Always, Always (Enough Already)...Reference from inside your app. Especially if your looking for max portability, and true DRM free.


    CommonDialog1.Filter = "Pictures (*.bmp;*.jpg)|*.bmp;*.jpg"

The minute I ran into the issue with the dialog-box while using the app, I knew this would be the line. I had to go back and refresh on how to use that property correctly.

I have a lengthy dissertation (bug-report?) on this software if you want it. Thought of posting it on the forum as my introduction, then thought this would be more effective, once I got the VB project working on my Win7 (typical control-registration-issues)

You say you're looking for help?

Tom Nelson

Pages: [1]