Josh,
Did you also migrate to PFC 7.0 when you went to PB 7.0?
If so, below is an excerpt regarding a PFC 7.0 enhancement to the PFC
Status Bar Service. It was written by Boris Gasin in PowerTimes
http://www.powertimes.com/ Not sure if it is your problem per se, but it
may provide some insight... And it's interesting reading anyways.
If not, which PFC version are you using? And what is the problem with your
status bar?... Are there two black holes? Or is the position off a
little? Or is your user not able to restore the frame after minimizing?
Have fun,
~Sharon
--
Sharon Weinstrom Buntz | mailto:[EMAIL PROTECTED]
Cheat Sheet for PFC/PB Help | http://www.pfccheatsheet.com/
>>>>>>>From PowerTimes http://www.powertimes.com/ March'99 Boris Gasin>>
The last change worth mentioning is a bug fix to the statusbar window
pfc_w_statusbar. To align the status window with the MDI microhelp area,
the of_GetSystemSettings function read the registry to determine the
current value of the window border width:
// NT 4.0 registry.
registryget('hkey_current_user\control
panel\desktop\windowmetrics','borderwidth',ls_temp)
li_border = abs(integer(ls_temp)) * 15
ii_borderheight = unitstopixels (li_border,yunitstopixels!)
I have nothing but respect for PFC developers, who even in their blunders
get the code to work, at least most of the time <g>. The first problem is
that unitsto-pixels conversion should have been pixelstounits (the registry
contains values related to pixels). Second issue is that the multiplication
by factor of 15 should be a division. Would you believe two wrongs cancel
each other out making a right! Well, almost The problem is that the
registry to pixel coefficient of 15 may vary depending upon the selected
system font size or whether the control panel settings were ever
configured. If you have implemented a fix that reads the registry for the
value of window border, it may still fail in some cases. A better way to
solve this problem is to get the value through windows API, which is
exactly what was done in 7.0. A very versatile API call
SystemParametersInfo was added to the win32 platform service, which is the
real reason I mentioned this bug in the first place.
Function boolean SystemParametersInfoA
(uint wActon, uint wParam, REF int pvParam,
uint fUpdateProfile) Library "USER32.DLL"
Along with providing information about the current window border width, the
SystemParametersInfo API function can read and set a multitude of other
system-wide parameters. To name just a few, you can enable or disable the
screensaver, change accessibility options, control various keyboard and
mouse settings, and so on A detailed description of the function arguments
and options is available at the MSDN site:
http://msdn.microsoft.com/library/sdkdoc/sysmgmt/sysinfo_4p67.htm
<<<<<<<
[EMAIL PROTECTED] wrote:
>
> After migrating from PB 6.5 to PB 7.0 the PFC status bar service stopped
> working. Is this a known problem??
>
> TIA
> Josh
> [EMAIL PROTECTED] HOSTED BY IIGG, INC. FOR HELP WITH LIST SERVE COMMANDS, ADDRESS
> A MESSAGE TO [EMAIL PROTECTED] WITH THE FOLLOWING MESSAGE: help pfcsig
> SEND ALL OTHER INQUIRES TO [EMAIL PROTECTED]
