Reply to thread

Message: [QUOTE="GroupReader, post: 1974698"] I've never actually done anything like this, but I've been developing in ASP.Net for several years. Here's some feedback for what it's worth. 1. I assume the IFrame will be filled with content from the same website and server. Otherwise, there might be security issues. 2. You'll have to work out a way to pass data back & forth between the containing page and the IFrame. Popping up the IFrame with the correct list is the easy part, but how will your containing page know which items you selected in the IFrame? Be careful using Session state to store this information... you'll need to make sure everything works even if you have multiple custom-dropdowns on one page. 3. How will your containing page know when you are "done" selecting items in the IFRAME? This may be a stupid question, but I just can't picture how it will work. 4. It can sometimes be a pain trying to get the drop-down to work in a way that doesn't seem "clunky" to your users... click the image, you get the dropdown. When does the drop-down go away? Under exactly what circumstances, and can you get it to work in a non-clunky fashion? 5. You mentioned the Atlas stuff. This is actually surprisingly simple to do. I'm not sure it's in beta any more. 6. Another option is to use "ASP 2.0 Client Callbacks" 7. Another option is to just use the XMLHttpRequest javascript object (ActiveX Object for IE) yourself, which is what Atlas and Client Callbacks do behind the scenes. 8. An advantage of what you are proposing is that you could create a "multi-select" dropdown, which is not available using standard controls (as far as I know). 9. One more option is to do it the "old school way." Download all data needed to the client and manipulate everything using javascript and javascript arrays. This still works really well with smaller data sets since it eliminates the round-trip all together. [/QUOTE]

Verification