Silverfrost Forums

Welcome to our forums

%ff format code not working with salflibc.dll dated 11/17/20

1 Dec 2020 4:34 #26655

The following %ff code worked for the past 25 years through version 8.5 (using salflibc.dll, dated 4/29/19);however, version 8.7 using salflibc.dll dated 11/17/20 does not work with the following %ff code. Version 8.7 using salflibc.dll dated 4/29/20 does work however..........

C...Transmission Penalty Factor i=WINIO@('%ff%tcPhantom Transmission Penalty Fact:%tc %ta'// 1 '%fl%7rf&',iTextColor,-1L,0D0,999D0,dHRDispFactB(1)) i=WINIO@('%il %rd %tc%^?rb[MCS]@%bh%tc&',0,MXM, 1 dMCS_HRDispFactB(1),iTextColor,iDispMCS(17),DispMCS,HelpStr(9), 2 iHelpTog,-1L) i=WINIO@('%ta%fl%7rf%il %rd %tc%^?rb[MCS]@%bh%tc%cb&', + 0D0,999D0,dHRDispFactB(2),0,MXM,dMCS_HRDispFactB(2),iTextColor, 2 iDispMCS(18),DispMCS,HelpStr(9),iHelpTog,-1L)

FOLLOWING FORM FEED %ff NOT WORKING....SEEMS IGNORED******

  i=WINIO@('%ff%ob[scored]%nl%tc%taInstallation%ta'//
 1'              Retirement%ta                 '//
 + 'Spin Reserve Fraction              Blocks%tc&',iTextColor,-1L)
1 Dec 2020 6:53 #26657

Sorry about that.

An adjustment was made for %ff within %ob because it was causing problems. This has had and unexpected impact on some existing code. You may need to modify your code in order to use the latest DLLs.

This may be just a case of (say) replacing %ff by %nl. If it is not obvious then let me know and I will take a look.

1 Dec 2020 7:20 #26658

%nl does not work with the 4/29/19 DLL so I assume it won't work with the new one either. I have an application with at least a hundred input windows and thousands of input variables. These variables are arranged in boxes as is seen in the code I sent. This is a major issue for me as the code has worked for 25 years prior and the windows are useless if the %ff don't work properly. What is your suggestion if I have a major box (%ob)with several internal boxes that get placed below each other using the %ff format code.

1 Dec 2020 7:32 #26659

One thing I've used is the %ob option of [bottom_exit]. This forces the next box to be below the current box. Just like of a %ff was issued.

1 Dec 2020 9:15 #26660

Thanks for the suggestion; however, that doesn't work either. It seems to have something to do with a box inside another box.

1 Dec 2020 9:21 #26661

Actually I did get the %ob[bottom_exit) to work....added it to the the wrong %ob.

1 Dec 2020 10:41 #26662

Paul,

The the %ob[bottom_exit) doesn't work on many of my input windows. Is there another solution?

2 Dec 2020 7:58 #26666

tbell

I will take a look. It may be necessary to provide a ClearWin+ option that restores the previous %ob%ff behaviour.

2 Dec 2020 9:56 #26667

tbell

I will need the whole of a winio@ construction in order to check this out.

Can you find a simpler/shorter sample of a complete winio@ sequence and either post it here or put it on DropBox.

2 Dec 2020 2:44 #26677

INCLUDE <WINDOWS.INS>

  INTEGER*4 i

C..Test %ob within %ob with %ff C.......Test Box 3 should be below Test Box 2 i=WINIO@('%ob[scored]Test Box 1%ff%nl%ob[scored]Test Box 2%cb'// + '%ff%ob[scored]Test Box 3%cb%cb')

  END
2 Dec 2020 4:55 #26683

INCLUDE <WINDOWS.INS>

  INTEGER*4 i

C..This code shows the issue with the [bottom_exit] option as I want Test Box 4 C..to display below Test Box 2 not Test Box 3 i=WINIO@('%ob[scored]Test Box 1%ff%nl%ob[scored]Test Box 2%cb'// + '%ff%ob[scored,bottom_exit]Test Box 3%cb%ob[scored]'// + 'Test Box 4%cb%cb')

c i=WINIO@('%ob[scored]Test Box 1%ff%nl%ob[scored]Test Box 2%cb'// c + '%ff%ob[scored]Test Box 3%cb%cb') END

2 Dec 2020 7:09 #26685

This turns out to be a regression that has now been fixed.

New (post v8.70) DLLs will be made available shortly.

2 Dec 2020 7:49 #26688

Thanks much!

30 Dec 2020 7:17 #26853

Paul,

When do you expect the new DLL to be available. Thanks.

31 Dec 2020 7:38 #26855

Please see you personal messages.

Please login to reply.