Program Testers

[Schmidt]

0.2.149

Finally , after hard work here there is the Full Functional Version.

Now it's possible to tweak parameters values (Disabled in previous vbRichClient-GUI version)

Go to #1 post of this thread to download

Nice so far.

Maybe a hint again for your currently needed Installer/Uninstaller (which I think is only
used for the vbWidgets.dll).

As already written further above - to create new Widgets you will simply have to
Paste the following small Function into a *.bas-Module (e.g. into the same one, which contains Sub Main)

Public Function NewWidget(ClassName As String) As Object
  If App.Logmode Then 'we run compiled
     Set NewWidget = New_c.RegFree.GetInstanceEx(App.Path & "\vbRC5BaseDlls\vbWidgets.dll", ClassName)
  Else 'we run in the IDE, so we create the instance from the registered version
     Set NewWidget = CreateObject("vbWidgets." & ClassName)
  End If
End Function

Now, with that routine in place, you should do a global project-search for the string:
'New cw' (without the apostrophes)

This should stop on all positions, where you create any Widget-Instances...

Now you will only have to decide, if the "marked" WidgetCreation line in your current search-
result specifies a Widget from vbWIdgets.dll (as e.g. cwVList) - or if one of your own
(Project-Private defined cwMyWidget-Classes) was found.

In case of a Widget from vbWidgets.dll, you can then use:
e.g. instead of:

Form.Widgets.Add New cwVList, ..., ...

The new regfree Creation-Routine from your *.bas Module this way:

Form.Widgets.Add NewWidget("cwVList"), ..., ...

This shouldn't take more than 2 Minutes or so.

The little NewWidget-Function Auto-Detects already, whether you run your Project within the IDE -
and in this case it uses the recently compiled (or registered) version of vbWidgets.dll -
or in case you run compiled - it will "draw the Widget-Instance" regfree from the vbWidgets.dll
which was placed in your \vbRC5BaseDlls\-Folder (sitting there beside vbRichClient5.dll).

Just take care (in case you edit stuff on vbWidgets.dll and recompile yourself), that this recently
compiled or registered version of vbWidgets.dll is placed also in the \vbRC5BaseDlls\-Folder,
before you test it in Binary-Format, or "zip it for deployment". That latter one is a requirement,
because the IDE will "link in the interfaces from the Widget-Classes" always from the recently
registered (or compiled) Version of vbWidgets in your System - so when you later run your
Executable-Binary - those "linked in interfaces" have to match with the ones it finds in the
regfree loaded version of vbWidgets.dll, it finds in your \vbRC5BaseDlls\-Folder.

That's because the vbWidgets.dll Project is still in development - and although many of its
Widgets are already "interface-stable enough", there's still some Widget-Classes where some
changes or enhancments are made - and thus this Dll-Project is (other than the vbRichClient5-Dll)
not yet switched into "Binary-Compatibility Mode" (it still is at "Project-Compatibility"), which
allows for easier creation of Project-Groups for Debugging.

HTH

Olaf