I have not filed a bug yet because i dont really think im good enough to
technically describe the issue. When i went to help > new bug i just got a
page saying the module is missing or deactive on jira.

The best way i can describe it in both FB3 and FB4 is that the actionscript
editor does not notify FB that a change in the editor has been made.

I dont know if i can attach images to this mailing list but the attached
screenshot shows the issue. Joint2 is invalid so i got a runtime error in
red. I then commented out the offending line and resaved it but still the
problem persists. The screenshot shows the offending line of code along with
its error AFTER i have hit save.

Note that this is a completely seperate project to my first email.

Running FB2 and FB3 under 32x never gave me any problems, and if it did, not
with enough frequency to be noticible in the 2 years i used them.
Running FB3 under VISTA Home 64x AMD 64  has this issue
Running FB4 under 7 Ultimate 64x Intel i7, i5 has this issue

It seems there is an inherited bug somewhere which effects 64x OS Windows or
architecture..

When googling this i found little so if you do experience this issue and can
let describe it well, please reply with details.

As far as im concerned even an option to tick to force a clean on save would
save alot of hassle.

Also is there any keyboard shortcut to clean?

Cheers.









On 5 February 2010 03:24, Lee Jenkins <l...@datatrakpos.com> wrote:

>
>
> Clark Stevenson wrote:
> >
> >
> >
> > Ugh i can totally appreciate your email.
> >
> > I have struggled pretty much constantly over the last 2 years with all
> > kinds of problems.
> >
>
> The more I work with this product, the more I'm convinced that it is a very
>
> buggy piece product in very core areas. All kinds of mysterious compiler
> issues
> with fragments of code not getting linked in all the time, having to
> perform a
> clean every few changes of code ,which itself takes forever if there is
> more
> than one project involved.
>
> --
> Warm Regards,
>
> Lee
>
>  
>

Reply via email to