You can find it here: https://github.com/SolidSoft-Lda/Royale-OfficeAddIn
Cross fingers to see if it's easy to publish on the Office Store.
But for now, I still have many features to implement.
Greg Dove escreveu no dia domingo, 7/11/2021 à(s)
21:07:
> Hi Hugo,
>
> Thanks, I must have missed
Hi Hugo,
Thanks, I must have missed that information in the past. I will take a look
at your github project next weekend. And the powerpoint presentation will
be interesting for many, I am sure.
Best of luck with the launch on the Office Store!
Cheers,
Greg
On Mon, Nov 8, 2021 at 9:39 AM
Hi Greg,
Yes, there seems to be a specific issue with the Add-In environment (I
debuged very deeply) and it seems that the Royale it's not responsible for
this issue (that was resolved for standard web applications).
Anyway, yes, this reduction, fixed the problem anyway and it's always a
Hi Hugo,
Pleased to hear it helped.
For the Add-in issue, I don't know what that was, but making the change for
the remote service to send less data (avoid the unnecessary fields) seems
like it would be a natural improvement to your application anyway, even if
it was in a 'swf' implementation.
Hi,
Just to let any one know.
This new flag solved the problem on the "normal" browser.
However the problem persists on Office Web Add-In for macOS (seems an issue
more deeply - problem in Add-In himself).
I solved my problem with a specific remote service for this case (using
only the properties
Yes, you can simply do that:
AMFBinaryData.verboseLogging = false;
Which is only an option for JS.
How are you registering your class aliases? I assume you are coding that
manually with registerClassAlias?
If not, the ClassAliasBead (and AMFClassAliasBead) do that for you as
application-level
How to access this ?
AMFBinaryData.verboseLogging = false;
Hugo Ferreira escreveu no dia segunda, 1/11/2021
à(s) 10:28:
> Hi Greg,
>
> Thank you.
>
> I'm not using js:AMFClassAliasBead
>
> I call the services by AS code, using SimpleRemoteObject:
>
> private var remoteObject:SimpleRemoteObject
Hi Greg,
Thank you.
I'm not using js:AMFClassAliasBead
I call the services by AS code, using SimpleRemoteObject:
private var remoteObject:SimpleRemoteObject = null;
remoteObject = new SimpleRemoteObject();
remoteObject.send(service, arguments);
Of course, I don't type this all the time. I
With the latest code, you should be able to control it easily by swapping
your class alias bead:
It is true by default (same as it was before), but only in debug build. If
you set it to false (like above) it should be quiet.
Please let me know if you see any issues or anything to be improved.
Thank you very much.
Greg Dove escreveu no dia domingo, 31/10/2021 à(s)
07:12:
> Hi Hugo,
>
> I did some work on this tonight.
> I realise it's not a substantial change, but plan to test it along with a
> couple of other changes, and push it to the asjs repo first thing tomorrow
> before I
Hi Hugo,
I did some work on this tonight.
I realise it's not a substantial change, but plan to test it along with a
couple of other changes, and push it to the asjs repo first thing tomorrow
before I start regular work (about 12 hours from the time of this email).
Hope that will make things
Hi Greg,
Having a switch option is great for a specific project that the developer
knows that will not consume all properties from the server (it's not a bug
on the project but a feature :D).
In this case, what happens is that the case warning is printed many times.
With 200 records and more
Ok Hugo, you already answered my question from the other thread, I will
look at this today and give you an option to switch that off.
Thanks,
Greg
On Sun, 31 Oct 2021, 6:57 am Hugo Ferreira, wrote:
> Hi,
>
> Today I mentioned about ignoring the warning: ReferenceError: Error #1056:
> Cannot
13 matches
Mail list logo
