Hi,

I had the same problem as the OP of this thread. This is what I did, it is fairly simple.

First, I created a stack and put the following script into the card script:

on suspendStack
    xBrowser_Unfocus
end suspendStack

on openField
    xBrowser_Unfocus
end openField

on resizeStack
  put the rect of this cd into myRect
  add 24 to item 2 of myRect
  subtract 14 from item 4 of myRect
  xbrowser_Set "Rect",myRect
end resizeStack

Then I created a field on top of the card and called this field "Url". I also added a button next to that field, with the following script:

on mouseUp
  xBrowser_Init "user","password"
  xBrowser_Open the windowID of this stack,fld "Url"
  resizeStack   
end mouseUp

You could add one more button with the following script:

on mouseUp
  XBrowser_Close
end mouseUp

Each time when you click the first button, a new browser element will be created. There are no checks for availability of browser elements, hence the try control structures. Although it is very rudimentary, it should be sufficient as a starting point.

Note that I use the xBrowser_Init. The reason is that the browser plugin included with Rev 2.8.1-dp-2 doesn't work. I am using an older version, which works fine.

(Now off to QaC to post a few bugs...)

Best regards,

Mark

--

Economy-x-Talk
Consultancy and Software Engineering
http://economy-x-talk.com
http://www.salery.biz

Get your store on-line within minutes with Salery Web Store software. Download at http://www.salery.biz

Op 13-apr-2007, om 20:24 heeft Scott Rossi het volgende geschreven:


What I did:

1) Established a rect to display the browser object (I used a graphic).

2) Copied the scripts of the demo browser stack into the script of my stack,
referencing the above graphic, commenting out handlers I didn't need.

3) Duplicated the custom properties of the demo browser stack in my stack.
This is necessary if you use the altBrowser scripts without any
modification.

4) Make sure the altBrowserState of your stack (one of the custom properties mentioned above) is true. Again, you need to do this if you use the demo scripts word-for-word. You can modify the scripts so this property setting
is unnecessary.

Good luck.

Regards,

Scott Rossi
Creative Director
Tactile Media, Multimedia & Design



_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution

Reply via email to