Digital Workshop

Hi

I have a variety of issues with a Flex pub using V7. Some may be me being a donk.

1. String.number
I can't convert a string to a number. e.g. the code below produces a NaN error:

var V1 = String.number("1");
var V2 = String.number("2");
V3 = V1 + V2;

I've tried String.integer too. Same result.


2. There is an error in IE after publishing to flex and running the html file. Seems to want a tag at the end of the code, but I can’t work out what. This doesn't prevent it working, but looks bad. It just shows the page error warning symbol in the bottom-left of IE.

Message: Invalid character
Line: 654


3. The download meter doesn’t work. Just stays at zero until the page is ready.


Anyone any ideas? The first one is halting my progress, so it would be good to know if it is something I have done.

Many thanks
Dan

ParseInt

Mack

Thanks again Mack
I take it that's a bug?

Another issue (?) for DW: if you have an object off the side of a page, then it still shows up when viewing in IE (in the black section). I presume this is only a prob when using scaling rather than fixed window size. I have images that fly in and out of the screen. The thing is, they don't actually fly off the screen; they fly in to the black section, stop then disappear.


Cheers
Dan

No. OpusScript functions don't necessary translate to Flex. It does state this in the instructions and is the reason why pass through was introduced.

Mack

String.number and String.integer are listed as being supported by Flex but don't appear to work. parseInt doesn't turn up in the help search at all, but works. parseFloat is mentioned, but only in passing. All very strange indeed. A bit of a lottery really.

Thanks
Dan

Something you can try as a workaround. Create a Frame object approx the same size as the page. Put those IFOs (identified flying objects) in the Frame which might exert more specific control over the boundaries.

You should send a message to DW Support (from the Opus app Help menu). Be sure to give them good info about your Chapter/Page sizes, scaling settings etc, or offer to send them the Pub.

Thanks Lar. I took your idea then simplified it to just adding some black masking blocks round the edge.
Cheers
Dan

Sorry Dan, assumed that you'd been trying an unlisted function. Have just read through the flex list and they're there! Wondered whether it was an out of date list, so fired up Opus 5 and Flash 6. This also lists the String.number function and is also doesn't work.

At least good old parse works!

Think I'm going to buy a lotto ticket

Mack

In flex, you can drop an object onto a hidden target (see attached). I have targets that appear in one place at different times. Dropping on to the visible target triggers all of them. Disabling them makes no difference.

Morning Dan,

Not sure what you mean by this latter part. From your demonstration, it's certainly appears that drag-n-drop don't function as expected with either hidden or disabled objects. I tried images as well as your vectors.

Flex just isn't suitable for anything we create, but somebody might have a more workable solution, however, the only method I can think of that would appear to work is to remove the object from the screen.

Mack

Evening Mack

I have a number of objects that should each be dropped onto the correct one of four targets. Rather than all four targets being visible at once, they appear one at a time in the same position on the screen. Because of the fault, dropping an object on to the visible target triggers all four sets of actions at once. It also means that all objects can be dropped at any time, instead of only the applicable ones for the visible target. It took me a while to work out what was happening.

I'll try moving them off screen if it sounds like DW will not fix this soon.

Cheers
Dan

That worked well thanks Mack, and saved me time over the more complex solution I was settling for. Fantastic. The only issue was that you don't appear to be able to move or animate hidden objects in Flex or Opus, but this was easy to work around.
Cheers
Dan

Glad it worked.

There is a solution to moving hidden objects and that is to use transparency instead. Only problem is there seems to be a problem with vectors but frames / images work.

Mack

I just discovered that myself. On one hand, it's nice to know I'm not alone in having these Flex issues, but on the other hand, I'm sorry that it's not just me - I don't wish everyone else to be frustrated, as well.