Support 2

[Support 2]

The original Formativ Stationery applet looks for ‘HTML Document’, which is the default file type when Internet Explorer is installed. It may be that your HTML document type is showing as ‘HTM Document’, which would not be seen by the applet (you can tell by looking in Windows Explorer at the files in your data folder). This is a limitation of the original applet and we have posted an update which should resolve the problem.

You can download the updated applet from the same URL, http://www.advansyscorp.com/formativ/applets/formativ%20stationery.vbf.

Please let us know if the updated applet does not resolve your problem.

Thanks,

Advansys Support

[This message was edited by Support 2 on January 24, 2002 at 03:59 PM.]

[This message was edited by Support 2 on January 24, 2002 at 04:00 PM.]

[Support 2]

You will not see any menus or buttons etc. unless:

a) you have one or more encoded applets in the local applet folder, i.e. the installation default is c:program filesadvansysformativlocal; or

b) you have published applets to one or more Formativ eDirectory libraries to which the user is subscribed by an associated Formativ Configuration object.

The Formativ Client runtime software will only execute applets which are encoded, or published to eDirectory, by the Formativ Admin application. No applets are automatically installed with the Formativ Client, only with the Formativ Admin product.

The quickest way to check whether everything is OK is to encode one of the shipping Formativ Admin applets:

• on the workstation with Formativ Admin installed, open FormativCentral and right mouse-click on the applet of choice and select Encode (first ensure that the applet integrations are not disabled with the selection at the bottom of the Integrations tab);
• copy the encoded applet from the Formativ Admin Encoded folder, default is c:program filesadvansysformativencoded, to the ‘local’ applet folder on the workstation with Formativ Client installed;
• when you start the GroupWise client you should now see a menu and the applet should be operational.

I hope this helps.

Thanks,

Advansys Support

[Support 2]

Sorry, unfortunately there is no OnShutDown event available in Formativ. There is one in GroupWise but it closes down Formativ before it can successfully execute any code associated with the ShutDown event.

Thanks,

Advansys Support

[This message was edited by Support 2 on December 10, 2001 at 03:02 PM.]

[Support 2]

Thanks very much for your post and feedback. I’ll discuss this application with our engineers and give you a full reply as soon as it is possible. Formativ cannot currently provide the change/modify event functionality. Unfortunately, GroupWise C3PO APIs do not expose a ‘change’ or ‘modify’ event. We will need to research if this could be done by using another GroupWise interface, such as a custom third party handler (TPH).

Thanks,

Advansys Support

[Support 2]

Thanks for trying again. As we cannot explain the problem, nor reproduce it, I have rebuilt the installation file in full and you can download it here.

Let’s hope the full reinstallation will work like it did previously.

Thanks,

Advansys Support

[Support 2]

We could not find a problem with the file internally, so just in case, I’ve uploaded the file again to the same location. If downloading and re-installing the file does not assist, you may need to try re-registering the file by using the command line is:

regsvr32 utilityobject.dll

This assumes 2 things:

1. Regsvr32.exe is in the path. If not, it will have to be copied into the Formativ directory.

2. The current directory is where Formativ was installed (i.e C:Program FilesAdvansysFormativ is the default).

Thanks,

Advansys Support

[Support 2]

I’ll check into this and find a resolution. It may be a corrupted upload.

Thanks,

Advansys Support

[Support 2]

We have found the rogue line of code which was causing an incorrect width calculation for the last control on the dialog. This was a hangover from an earlier beta version which used a different technique to autosize the last control.

We also revised the last control autosize function, which will now only expand the last control’s height if it is less than the remaining blank space on the dialog form. Only variable height controls such as Memo, MultiLineLabel and list boxes are processed by this function.

A pre-release test version of the updated utilityobject.dll can be downloaded by clicking here. You can download this file and replace your existing utilityobject.dll file in the Formativ program directory, usually c:program filesadvanysformativ. Please let us know how you progress.

Thanks,

Advansys Support

[Support 2]

I can replicate the problem where the control becomes too wide (i.e. the apparent scrollbar issue as reported in your other post), but I can’t replicate the issue where the control is a minimum of 120 pixels high. Are you able to post the full example code which illustrates this problem?

BTW, if you encapsulate your code by using the Instant UBBCode ‘Code’ button, this will place special codes around your source code to preserve the spaces used in code formatting.

Thanks,

Advansys Support

[Support 2]

There are two ‘SpaceAbove’ lines in your code sample. When I removed the ‘.SpaceAbove = 20’, the ‘.SpaceAbove=120’ became active and seemed to resolve the problem during my testing. Please let me know if this is not the case for you.

Thanks,

Advansys Support

[Support 2]

Thanks for the feedback. It looks like the problem is related to the .CaptionPosition = afvLeft setting, which is causing an incorrect width calculation for the Memo control.

We will look into it today.

Thanks,

Advansys Support

[Support 2]

The Formativ engineering team reviewed the issues and agreed with your observations. Today we updated the installation file to include the following fixes/enhancements:

• Fixed a bug that caused an index out of bounds error if a dialog with no controls had its AutoSize property set to TRUE.
• Button 6 on the standard dialog is no longer hidden if the Wizard Image is turned off.
• Added a new property to the standard dialog – CancelButton. This property specifies which Formativ dialog button functions as the Cancel button. The default is Button 2 (Btn2).
• Added a new property to the standard dialog – DefaultButton. This property specifies which Formativ dialog button functions as the Default button, which has the initial focus. The default is Button 1 (Btn1). If another button does not have the focus, then the default button value is returned when the Enter key is pressed.
• StdDlgButtons constants have been updated to reflect the new internal values used to represent the six standard dialog buttons. The return values are now sequential from 1 to 6 and directly relate to the number in the button name. As long as you have not hard coded button values in your macros, this change will not affect you. If you have hard coded button values for Buttons 5 and 6, you should replace them with the appropriate StdDlgButtons constants (i.e. Btn5 and Btn6) to ensure correct behavior.
• Updated some of the shipping macros to take advantage of the new CancelButton property.

The modified macro example below illustrates a couple of the updates.

code:

---

Sub Main(Client, GWEvent)
  const SIGNATURE_LOCATION = "c:signatures"
  set SigDlg = Utilities.NewControlBoxDialog
  with SigDlg
    .Caption = CAPTION
    .Title = "Select Signature"
    .CancelButton = Btn1
    .Button1Caption = "&None"
    .Button2Caption = "&Personal"
    .Button3Visible = TRUE
    .Button3Caption = "&Casual"
    .Button4Visible = TRUE
    .Button4Caption = "&Disclaimer"
    .Button5Visible = TRUE
    .Button5Caption = "&View/Edit"
  end with 
  SigDlg.Height = 120 
  SigDlg.ShowWizardImage = FALSE
  rButton = SigDlg.Execute
  SigList = Array("Cancel","Personal","Casual","Disclaimer","ViewEdit")
  if rButton <> 1 then
    SigFile = SIGNATURE_LOCATION & SigList(rButton - 1) & ".sig"
    MsgBox(SigFile)
  else
    MsgBox("Canceled!")
  end if
End Sub

---

Thank you again for your feedback. We hope that this update will more effectively address your and other users dialog requirements. Please download the update from the Formativ download page and let us know if you have any further problems or suggestions.

Thanks,

Advansys Support

[Support 2]

Thanks for the additional code and background. The AutoSize problem appears to be a bug caused by no controls being added to the dialog, such as edit box, text box, check box etc..

The second issue is that Button 6 does not appear. This is due to the WizardImage being hidden, in which case Button 6 is automatically made invisible.

We will research the best way to resolve these issues and get back to you.

Thanks,

Advansys Support

[Support 2]

Thanks for your feedback. The return values of the buttons are effectively arbitrary numbers. It is correct that Button 5 returns a value of 6 and you will find that Button 6 returns a value of 7. This design is based on the value of constants used within the ‘behind the scenes’ code in the Utility Object DLL.

The best way to make your code appear more intuitive is to use the inbuilt Formativ constants for the button return values, i.e. Btn1 for Button 1, Btn5 for Button 5 and so on. For example,

if rButton = Btn5 then
‘do something
end if

In regards to the OK and Cancel button positioning, you can simply change the captions of the first two buttons (buttons 1 & 2) to achieve your desired interface requirements and use the Btn1 and Btn2 constants when you check the dialog return value.

I hope this helps clarify the operation of the dialog buttons. Please let me know if you have any other questions.

Thanks,

Advansys Support

[Author]

Replies