Hi all,
Last week i developed some menu items for the context menu in a flex
application.
When i compile it with FB 4.7 every option is show without any problem but when
i compile with maven the context menu is always the default one?
I am using SDK 4.10.flash version 10.0.45
4.10
Hi Miguel,
well Flexmojos 3.6.1 is about 1000 Years old :-) It's not at all capable of
compiling with Apache Flex versions. If you want to use Apache Flex releases
you have to upgrade to Flexmojos 7.0.0 and currently you have to create the
Mavenized version of the Flex SDK by using our cool Mav
Hi Chris,
I was waiting for your response!
I enter in this project and a lot of libraries and etc are 1000 years old
because i did not know Maven i let it be quiet there but in this moment i was
already reading and trying to update this historical version to a update one :)
Thanks for the links i
i,
I have AdvancedDataGrid with multi level GroupingCollection2 which shows
1000s of rows.
I am using displayItemsExpanded="true".
Is there a way not to expand it not all the way up, but to the particular
level of grouping,
lets say to level 1 programmatically ?
So in that case user will s
Hi Miguel,
You can have a look at my confluence ... here I documented a lot of stuff back
in the days where I didn't have write Access to the Flexmojos Wiki:
https://dev.c-ware.de/confluence/display/PUBLIC/Flexmojos+Section
Especially this article should be a good starting point:
https://dev.c-wa
displayItemsExpanded calls ADG. expandAll() method, for which the source code
is available
I have checked that all the variables involved in that method are either
protect or mx_internal,
So you could probably subclass ADG and write a variant (eg. expandUpToLevel())
to do what you expect.
(hi
I am thinking of another solution:
Make displayItemsExpanded and
somehow expand it, which would make it expanded to 1st level folders,
since my ADG is 2 groups deep.
Is there a way to expand the ADG group programmatically?
On May 5, 2014 8:15 AM, "Maurice Amsellem"
wrote:
> displayItemsExpanded
We've struggled with this issue *a lot*. Here is our final solution that seems
to have resolved the issue in a satisfactory way:
1. Our build environment renames the SWF to myapp_1_2_3_4.swf where 1.2.3.4 is
the current version number.
2. We define a variable at compile time that specifies the
Thanks Jesse! I will give a try to your solution too!
Angelo
2014-05-05 21:34 GMT+02:00 Jesse Ward-Karet :
> We've struggled with this issue *a lot*. Here is our final solution that
> seems to have resolved the issue in a satisfactory way:
>
> 1. Our build environment renames the SWF to myapp_1
This issue has also worried me (a lot). My approach:
I also change the swf file name as you do. Then I manually update the Main.html
file to refer to the new swf file name. The Main.html file name doesn't change.
I place the files on the server.
I change my .htaccess file as follows:
#
-
Setting the cache control in the .htaccess (or its equivalent) is the best
approach in my opinion.
This is what I do when I want avoid caching of certain files, i.e. the
browser should always load this directly from the server:
Header Set Cache-Control "no-store, no-cache"
Thanks,
Om
On Mon, Ma
11 matches
Mail list logo
