Expand my Community achievements bar.

SOLVED

Components not viewable in design mode

Avatar

Level 1
Hi all and Happy New Year,



I just started to install and use Cocomo on my current
version of FB3.

The examples are correctly executing, however there is no way
to edit the contents using design mode of FB3.

The graphic displays shows only a red-crossed blank
placeholders.



Is there any restrictions regarding design mode that I missed
in the doc or did I miss a step or made something wrong during the
installation?



Thanks in advance,

Lionel
1 Accepted Solution

Avatar

Correct answer by
Former Community Member
Hi,

When you add the cocomo.swc in the Library path, it always
shows up in the design mode. However, when you use the source path
, it tries to get the API's directly linked from the source code in
source path and may overwrite the customized design.xml and
manifest.xml features like the components panel classes in design
view and code hinting in mxml files for namespaces declared in the
manifest.xml.



I have come across this problem in flex always while making
swc's with customized manifest and design.xml features.

So the best way is to keep the swc in the library path and in
case you want to link the source path for debugging, add the source
path to source-attachment under the added swc in your library path.

Thanks

Hironmay Basu

View solution in original post

5 Replies

Avatar

Former Community Member


Hi Lionel,



To my knowledge, we did have design mode working. We're
going to run some tests with the examples and get back to you.



thanks

nigel

Avatar

Level 1
Thanks Nigel



The result I obtain in design mode for the
MultipleGroups.mxml example can be seen


here



As well, when I bring in components, they don't display
correctly and appear as empty rectangles.

In source mode code auto-completion for rtc components
doesn't work either...



I suspect an installation problem...

I'll continue to investigate from my side as well and will
post the results



Lionel

Avatar

Level 1
After having removed the source directory from the source
path tab in the Flex build path of the project properties, it
worked like a charm...



Avatar

Correct answer by
Former Community Member
Hi,

When you add the cocomo.swc in the Library path, it always
shows up in the design mode. However, when you use the source path
, it tries to get the API's directly linked from the source code in
source path and may overwrite the customized design.xml and
manifest.xml features like the components panel classes in design
view and code hinting in mxml files for namespaces declared in the
manifest.xml.



I have come across this problem in flex always while making
swc's with customized manifest and design.xml features.

So the best way is to keep the swc in the library path and in
case you want to link the source path for debugging, add the source
path to source-attachment under the added swc in your library path.

Thanks

Hironmay Basu

Avatar

Level 1
Everything is OK now!

Thanks a lot!

Lionel
The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----