forms in wrong directory after adding OCX control

[Paul D. Elliott]

Paul,

This may be something to watch out for in the new FF.

I added 6 controls of MS masked edit to a form. On the first, when it asked where I wanted to
save the .inc file, it was pointing to the FF installation directory and not my project's directory.
So I changed the dir at that time & saved the file. the next .incs got saved in the right place.
after this I close FF for a while. when I restarted, I noticed that a couple of the forms didn't
have the latest changes. so I went looking for them and found them in the FF directory. my
project directory had the forms dated yesterday. so I copied over the newer forms to my
directory & deleted them from the FF directory. it compiled fine & has the latest changes to the
forms now.

so you might want to watch out for default directory changes made by those DLLs when it comes
time to save forms & such.

[Paul D. Elliott]

How about adding a default directory to a project? Useful when adding forms & module & resources.
I know you have an output directory for compiling & exe but that's all it's used for.

[TechSupport]

Sorry I haven't been around lately.... I started a new position at work this week so programming had to take a back seat.

In FireFly3, the directory structure for a project is fixed: Modules, Forms, Images, Release. It makes life soooooo much easier for me and you (trust me, I have tried fixed and non-fixed directory structures and the fixed structure is much cleaner and less problematic).

[Paul D. Elliott]

Ok, so I take it that there will be a "home" directory for a project. Right?
Hopefully that will cure my little problem of files popping into the FF install directory.

So, how soon will FF3 be born?     Can't you explain to your bosses at work that they are
interfering with the important stuff? A new position ( and hopefully more pay ) and more responsibilities
are good and it does take care of the need to pay to pesky creditors. 

I'll wait.

[TechSupport]

Yes, there is a "home" directory. When you create a project you specify the directory where the project will reside. FireFly automatically creates the other subdirectories off of the main project directory. I believe that this is the approach that the newer Visual Studio programs use as well.

FireFly 3 has been creeping along for over a year now. I have made a couple of design changes along the way that certainly slowed down the release. I am now at the point where I am using FireFly 3 to build FireFly 3. I figure that if I can develop a project as diverse and complex as FireFly using FireFly, then everyone else should be able to create pretty involved applications as well. Fellow PB'ers Marty and Mark have a huge pharmacy program that will certainly test FireFly's capabilities. As an aisde, the new FireFly 3 compiled the FireFly code to about 300K less than the existing FireFly 2 did - and it compiles MUCH faster. Not bad at all. I have learned many lessons since the FireFly 2.

On top of it all, I am developing a new code editor as part of FireFly based on EDM32 and it has code folding. Just about every internal part of FireFly is new... However, the interface will be familiar for most people and it sports many new features that makes searching, organizing, and dealing with your project much easier.

I really thought that I would be fully into beta testing by now but sadly I still behind schedule. I am going as fast as I can but I really don't want to push out some half hearted code just for the sake of completing it.

[Paul D. Elliott]

No problem.  I too would prefer a "fully functional - no shortcuts taken - unrushed release" program
that you are truly pleased with. It makes for a much more pleasant experience for all.

Take your time. I just had the slight hiccup with files going to the wrong directory but that only
happened a couple times after adding MS MaskedEdit fields. I'm looking forward to your version
of MaskedEdit.

[Paul D. Elliott]

    Argh!

it did it again. only this time, all I did was add a new form, added a bunch of controls then told it
to compile. it saved 2 other forms in the FF directory before it asked where to save the new form.
I noticed the 2 forms where they shouldn't be at that point. not sure why those 2 got saved as I
had not changed them. and why did they get saved in a different directory than the one from
which they were read?

if it helps to understand, I keep all projects/source on a different drive than where FF & PB are
installed.

[TechSupport]

Thanks Paul - I will look into this directory issue today to see if I can spot anywhere where the default save directory is being changed. I have an idea where this may occur but I need to get into the source code to be sure. Leave it with me and I'll report back later today.

[TechSupport]

I couldn't see anything immediate in the source that would cause the problem. Tomorrow I will test using a set up like you are running (project on a different drive than FireFly).