This is Interesting: Free Magazines for Graphics designers and webmasters  


Home > Archive > Macromedia Flash > November 2003 > its a real problem





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author its a real problem
cable8 webforumsuser@macromedia.com

2003-11-27, 5:58 pm

nobody out there having any clue???

Its not only a little inconvenient. Greater Projects will often reside on network shares, particularly
samba shares, to maintain heterogenic environments.

The Flash-IDE seems to cache the class documents, when compiled first.
Then it seems that changes to these documents won't reported immediatly.
May be this is caused by an incorrect behavior of the samba server ...

But there has to be a workaround - including documents via #include works like expected!
Is there any way to prevent FlashMX2004 from caching AS2.0 Class documents???
Any way to force a reload???

thanks,
cable.



cfulk webforumsuser@macromedia.com

2003-11-27, 6:02 pm

Did you ever find a resolution to this?


cable8 webforumsuser@macromedia.com

2003-11-27, 6:02 pm

No, not really.

I've tried to work on local windows HD. To test the whole projects, i had to update using CVS or simple rsync. -
But after all, its pretty laboriously.
Now i have mounted the local windows directories containing the flash documents on the linux box containing the other project files. Then i've created symbolic links of these 'Flash'-directories in the project dir.
It's at least a workaround.

If there's any other solution, please let me know.

cable




cfulk webforumsuser@macromedia.com

2003-11-30, 12:41 pm

I ended up creating a sub dir under the classes sub dir in the localsettings for flash 2004. Not exactly what I wanted to do but it works for now.



Sponsored Links


Copyright 2003 - 2009 forum4designers.com  Software forum  Computer Hardware reviews