FUNCTION HTML_WM_DESTROY (hWndForm AS DWORD) AS LONG is being declared as FUNCTION HTML_WM_DESTROY (hWndForm AS DWORD,) AS LONG when selected and generating a compile error.
This is now fixed. It also affected the WM_PAINT message. The problem arose when I added support for "block style" function prototypes.
Fix will be in 1.06.
Quote from: TechSupportFix will be in 1.06.
Have I missed a release? I have 1.04 here.....
Andrew
1.05 was uploaded a couple of days ago. Check the FireFly web page.
I'm now on 1.05, and I just hit this WM_DESTROY problem. About to report it when I saw someone else had got there before me.
Can I manually add the parameters for WM_DESTROY? If so, what would they be to keep FireFly happy?
Andrew
There are no parameters other than the form handle. You simply need to manually remove the trailing comma.
No wonder the wMsg, wParam and lParam that I added didn't work.... ;)
Andrew
Yeah, I only noticed it when I compiled and it told me %WM_USER wasn't defined. I posted a message here which I deleted a few minutes later saying there was a problem with InClean or something, but when I added the value to my code and compiled it kept giving me more errors till finally it came to a value was missing for the function and I saw the comma...once I fixed that all the problems went away and I guess they were only there because it wasn't compiling that included file or something.
P.S. What is a Block Style Prototype???
Quote from: Roger GarstangP.S. What is a Block Style Prototype???
Block Style
Function FORM1_WM_COMMAND ( _
hWndForm As Dword, _ ' handle of Form
hWndControl As Dword, _ ' handle of Control
wNotifyCode As Long, _ ' notification code
wID As Long _ ' item, control, or accelerator identifer
) As Long
End Function
Regular Style
Function FORM1_WM_COMMAND (hWndForm As Dword, hWndControl As Dword, wNotifyCode As Long, _
wID As Long) As Long
End Function
Oh, neat...I like that. Must have taken some time to make up all the comment lines though.
Just one comment about this subject.....
When FireFly adds the new event name with a longish list of parameters it always automatically wraps the parameter list - and the first thing I always do is to remove the line wrapping. If the function list heads out to the wild west and off screen I just don't care.
I'd be real happy if FireFly grew an extra option to prevent this automatic wrapping. I know other people will say the functionality is fine, but it isn't for me.
Andrew
Yeah, I hate wrapping too. I only wrap at like 256 or 255 characters whatever the default line length is for a lot of editors. As long as it doesn't wrap with my length when I print I'm good. Usually the first time I print I look to see what lines wrapped and where and use the continuation characters on lines that length and beyond.
Maybe a line length option would be good, kinda like email apps have.
Quote from: kazmaxI'd be real happy if FireFly grew an extra option to prevent this automatic wrapping. I know other people will say the functionality is fine, but it isn't for me.
Changed it so that the wrapping now occurs at or about 250 characters instead of 80.
Sounds ideal :)
Andrew