Strangled with a new Royale wrapper component

Hi, I'm strangled with an issue. I'm developing a wrapper for office.js (office web add-In). I have this file OfficeAddIn.as in src root folder with the following content: package { import org.apache.royale.events.EventDispatcher; /** * @externs */ COMPILE::JS public class OfficeAddIn extends

Re: Query url variable from a Apache Royale Application

Thank you. Harbs escreveu no dia segunda, 18/10/2021 à(s) 12:20: > Yes. That bead can help to deal with parameters, but routing is very > powerful. > > Check out this demo: https://unhurdle.github.io/spectrum-royale/ > > The code is here: https://github.com/unhurdle/spectrum-royale < >

Re: Query url variable from a Apache Royale Application

Yes. That bead can help to deal with parameters, but routing is very powerful. Check out this demo: https://unhurdle.github.io/spectrum-royale/ The code is here: https://github.com/unhurdle/spectrum-royale The hash is automatically routed to the

Re: Container.icon in MXRoyale

I didn't realize you could just instantiate an embedded image and get a Bitmap object, so I assumed titleIcon was a custom 'factory' class, sort of the way item renderers are used. My mistake, and you can safely ignore my previous message. On 2021/10/18 09:41:17, Greg Dove wrote: > What I

Re: Query url variable from a Apache Royale Application

Thank you Piotr, I have solved my problem with ApplicationParametersCaseInsensitive bead. It works pretty well. Piotr Zarzycki escreveu no dia segunda, 18/10/2021 à(s) 10:07: > Hi Hugo, > > Try to look into bead -> > > > > > > > > You can extend RouteToParameters and

Re: Container.icon in MXRoyale

What I meant was that it is populated from embedded assets. titleIcon="@Embed(etc... That approach, or 'binding' to an embedded Class const. So I don't understand the difference you expressed for titleIcon, because this is exactly the scenario I was meaning where class typing would typically be

Re: Query url variable from a Apache Royale Application

Hi Hugo, Try to look into bead -> You can extend RouteToParameters and override method stateChanged - to grab params from url. I have above code placed in main application file. Thanks, Piotr niedz., 17 paź 2021 o 22:27 Hugo Ferreira napisał(a): > I found the

Re: Get the browser address

Thank you very much. Edward Stangler escreveu no dia segunda, 18/10/2021 à(s) 02:44: > > MXRoyale and SparkRoyale use document.URL (for JS; loaderInfo.url for > SWF) to set their Application.url properties. > > document.URL is a read-only version of window.location.href. > > > > On 10/17/2021

Re: Get the browser address

A lot of months without using Royale and I forgot that it's a layer above JS. Thank you. Maria Jose Esteve escreveu no dia domingo, 17/10/2021 à(s) 23:45: > Hi Hugo, have you tried "window.location.href"? > Hiedra > > -Mensaje original- > De: Hugo Ferreira > Enviado el: lunes, 18 de

Re: Container.icon in MXRoyale

I'm convinced there's no point in allowing a mismatch. I just looked at the flex source for Panel.titleIcon and it looks like it's more a factory class than an embedded asset class. It's used like this if (_titleIcon) { titleIconObject = new _titleIcon();