Digital Workshop

Hi

I have an Opus Pro pub where a frame containing text input boxes is displayed, upon button click, on top of a large text box, which is below. During runtime, when entering text in any of the frames many text input boxes, and then dragging the frame (it can be dragged to allow the user to view the text box below), the I-beam cursor that starts to flash once a text input box is selected for text entry, continues to flash in the text box below, when the frame is dragged away.

I've tried checking "stop mouse clicks passing through" on the frame and its component text input boxes, with no success. The flashing I-beam continues until the frame is hidden via a hide action. The text box below is not set up to accept text entry. Of necessity, it is 'ordered' to the bottom in the organizer, below the frame and all else. Since numerous objects are dropped into the underlying text box (though, the frame is not intended to be one of these; it's simply draggable), it is set up as a drop zone.

Interestingly, if you try to enter text where the I-beam cursor is left flashing in the text box below the frame, text continues to be entered in the now-moved text input box/frame, and the I-beam resets back to that selected input box.

If anyone has any ideas for remedies, I would be appreciative, since the flashing I-beam reduces the professional look of the pub. My only solution to date is to not allow the frame to be dragged, covering up the flashing I-beam underneath.

Kind Regards,

If the "text box below" is not set up to accept text entry, try this:

1. Go to the TEXT INPUT menu of the "text box below" and disable using the current variable as a TEXT INPUT by unchecking the box in the TEXT INPUT menu. And then click APPLY or OK.

2. Right-click on the "text box below" and choose INSERT VARIABLE from the pop-up menu. And select the variable that was in the TEXT INPUT menu.

The name of the variable will appear on the Button object surrounded by < > brackets. When the publication is previewed or published, the contents of the variable will be displayed on the button and not the variable’s name.

Hi

Thank you for your reply.

The large text box, covering most of the screen and serving as a drop zone for the labels, I'm afraid has never had a check for text input, nor a variable in this empty box on the text input tab. So, unfortunately, what you suggest cannot be done.

Interestingly, I also tried to add an opaque text box with white background to the frame as the bottom layer to see if it could "absorb" the click on the multiple text input boxes above. The click is passed through to the underlying text box-drop zone anyway.

So far, my best alternative is to not make the frame draggable. The cursor will continue to flash unseen below, until the close button moves the frame off screen and hides it as well.

Any additional ideas are welcome.

Thanks again for your help.

Kind Regards,

You might want to try this, just to see if it works:

1. Put the text into a varible.

2. Delete the text from the bottom text box.

3. Right click on the bottom text box and choose INSERT VARIBLE, choosing the varible that you just created.

The text box should now have the varible name in brackets but when you run the publication it should show the text without any blinking I-cursor.

Hi

Thanks for your your reply. While the large, underlying text box, being used soly as a drop zone, has no text, your reply suggested another possibility: to change the this text box to a vector of the same size, background, enabling it to accept dropped objects.

I tried this, believing that a flashing I-beam cursor would have no place in a vector object, since these can't accept text. Unfortunately, the flashing cursor appeared in this vector as well. So, I think this persistent flashing cursor has nothing to do with the box below, and simply "bleeds through" no matter what.

I hope DW can remedy this for the next version of Opus.

Kind Regards,