I'm not sure where to ask this, so here goes... thanks in advance for any ideas of how to handle this problem.

I have a number (in a portal, if it matters) that is displayed to the user. I'd like the user to be able to do various things to that number (but NOT to be able to simply edit it). So what I'd like to have happen is the following:

When the user clicks on the number, a drop-down menu appears (out of thin air; there was no drop-down item there before) and provides the user a few choices. The user then chooses something from the menu (and I blast them over to another part of the layout to do that), or they decide not to and mouse off and release.

Is this possible to do? I think there might be a plug-in for it, but unfortunately I am not able to use the plug-in for financial reasons.

The "easy" solution of just making the field be a pop-up list or a drop-down menu has a couple of flaws:

- the formatting is determined by the formatting of the field

- selecting something seems to jump the user to the next portal row

Edited September 24, 201015 yr by Guest

Perhaps...

Create a pop-up menu field, with a value list of actions. Don't allow entry in browse or find (scripts bypass this). Make it really small and format it so it has no background, border, etc. Add an OnObjectModify script trigger that sorts out what to do with what they picked. Put this field behind your number. If necessary, put a fill color on your number field so that you can't see the actions field behind it.

Make the number field a button that clears the actions field and navigates to the actions field (remember to have your script check that you're in browse mode).

Might this do what you want?

HTH

Yep, have tried that. Made it 1x1, blah blah blah.

The drop-down itself works great. But unfortunately, the two problems are:

- It creates strange visual artifacts (a very thin line as it tries to display things actually IN the confines of the field.

- There is some goofy auto-selection stuff that happens in the next portal row, perhaps because you aren't confined to the boundaries of the portal row in question?

I think I can probably solve the second one - it's the first one that I haven't figured out yet, and that one rears its ugly head whether its in a portal or not. :

Nonetheless, I thank you for the suggestion!