On Wed, 22 Nov 2006 17:22:06 -0800
Jon Foster <[EMAIL PROTECTED]> wrote:
> Mattias Gaertner wrote:
> > The "invalid floating point operation" are raised at several places,
> > where the codetools check for inconsistency. This prevents further
> > chaos and normally helps to create a useful backtrace.
> >
> > I fixed such a bug on monday.
> > For another I have a vague idea, what it can be.
> >
> > Mattias
> >
> >
> >>> Recently as I was coding with Lazarus I started receiving "invalid
> >>> floating point operation" messages at seemingly random times. Now
> >>> I think its related to code that is trying to figure out the
> >>> structure of my program.
> I updated from SVN and things are improved. I still haven't turned on
> the tool tip stuff but shortly after I wrote this I ran into a
> similar but different problem. I had been unable to set events
> anymore (click drop down and "invalid floating point" message
> popped). I finally resorted to overriding the form constructor and
> manually setting the events with code. This worked and helped me get
> a project done.
>
> After I updated from SVN I no longer receive the message but the
> event dropdown wasn't showing any candidates. I noticed an error in
> the message window that tells me it can't find the source for one of
> my units. I remmed out the unit name in my uses clause to temporarily
> work around this issue.
>
> As I have a library of non-visual Pascal objects that I've been using
> for years I usually need them in every project I create.
Then create a package for it and add it to your projects.
Creating a package is easy.
And adding it to several projects as well:
1. Open the package.
2. Open a project.
3. The package editor is still open, so just click on More -> Add to
project.
4. go to step 2
Eventually you can define the start set of packages for new projects.
> I looked for
> a place to define a source search path in my environment but haven't
> found such. But it would seem that if Lazarus is going to compete
> with Delphi / Kylix that distribution of units without source would
> be a normal thing. In which case how do the tools deal with this?
A global directory, where all packages/units are compiled into has the
following disadvantages:
- you can only have one version of a package
- The IDE has trouble to find name conflicts and missing files
- a global source path might work on your machine with your set of
packages, but when distributing one of your packages, this might fail
> Anyhow, is there anyway I can point it to my various different
> directories in my source tree so that it will continue to function
> normally?
>
> THX - Jon
>
> PS: This is the first project I've been able to complete in Lazarus.
> Keep up the good work guys!!!
Mattias
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
