Status bar issue

[J P Eskdale]

Hi
I thought I would give Firefly a try with a new program I was writing. But I was/am trying to  use a Statusbar.  I couldn't find any examples.  I added the status bar to the form OK - However according to the Handles and ID's window shows that the handle is Form1.StatusBar.hWnd but this fails to compile.
If you type Form1.  the codetips gives StatusCtrl as an option but a "." after the StatusCtrl does not give any options.

I entered Form1.StatusCtrl.hWnd and it seems to work - Is this a bug or is there something I don't understand
Thanks
Jon

[David Kenny]

Jon,

Try here: http://www.planetsquires.com/protect/forum/index.php?board=28.0

It's in the Tutorials & Step-by-steps section.  Easier to follow the link above, but there are other tutorials that you might be interest in.

David

[J P Eskdale]

Thanks David,

I watched the video which created the Statusbar.  Although that bit I had done previously.  The problem appears when I need to access the Statusbar and I need its handle.  The sample never accesses the Statusbar. Using my program and looking at the "Handles and ID's" window it tells me that the handle of the Status bar is "Form1.StatusBar.hWnd" but that does not compile.  Interestingly in the sample you pointed me to the "Handles and ID's" window gives the handle there as "HWND_FRMMAIN_STATUSBAR" which does compile.  So now I think I'm more confused.  Is this different naming convention of handles something between earlier versions of Firefly?
Thanks
Jon

[Paul Squires]

Hi
I thought I would give Firefly a try with a new program I was writing. But I was/am trying to  use a Statusbar.  I couldn't find any examples.  I added the status bar to the form OK - However according to the Handles and ID's window shows that the handle is Form1.StatusBar.hWnd but this fails to compile.
If you type Form1.  the codetips gives StatusCtrl as an option but a "." after the StatusCtrl does not give any options.

I entered Form1.StatusCtrl.hWnd and it seems to work - Is this a bug or is there something I don't understand
Thanks
Jon

Are you using the Object Framework Beta? Do you get a beta warning when FireFly starts? If you are using the beta then be warned that it time out soon so you are better off not using it.

[Paul Squires]

I believe an early upload of the FireFly 3.70 package had the Framework enabled for new projects even though the Framework was not included in the package. That would cause the Handles and ID's window to display those "." values.

Better off re-downloading and installing again. You will probably need to edit your project's *.ffp file to remove the UseObjectFramework=1 line.

Sorry about that.

[J P Eskdale]

Hi Paul,
Thanks - It isn't displaying a Beta warning so I guess its the later issue in that it was one of the early 3.70 downloads.  Being the first program I'd tried FireFly on I didn't realise the difference.  The dot syntax certainly looks much more logical.  It is 1:50am now so I think I'll try tomorrow.  Being curious do you have an idea of when the dot syntax will be released

Thanks
Jon

[Paul Squires]

Thanks Jon - any trouble with it tomorrow then just let me know. Dot syntax will be in FireFly 4.

[David Kenny]

Jon,

I think I spotted your current problem.

Using my program and looking at the "Handles and ID's" window it tells me that the handle of the Status bar is "Form1.StatusBar.hWnd" but that does not compile.

Notice your Form name is "Form1".

Interestingly in the sample you pointed me to the "Handles and ID's" window gives the handle there as "HWND_FRMMAIN_STATUSBAR" which does compile.

Notice that the Form name in the tutorial is "FrmMain".

To get your program to compile now should be as simple as changing "FrmMain" in the example code to "Form1" as such:
HWND_Form1_STATUSBAR  (also note that the case of any text in the whole name doesn't matter)

Hope that helps,

David

[J P Eskdale]

Hi Paul,
I've download the install again.  This install has exactly the same version number 3.7.0.0 and is the same size although my original one has a modify date of 11/10/13 and the one just installed of 14/10/13.  I did a file compare (fc /b) and they are very similar but there are two small blocks which differ.  - Very confusing have the same file and version number but being different versions!
Jon