Hi all,
Moving to list because it became something more than issue comment.
Nearly two year - starting with emulating classes - I am trying to make
my flex application running with royale emulation.
But more than my application, I am trying to be the part of the project
that I believe doing very good things mostly the help of Alex and help
to remove issues related with emulation components
The way I go :
1. Running my app discovering the non-functioning parts.
2. Trying to isolate the case from application - sometimes really time
consuming issue because it is client-server app.
3. Preparing a case than can be compiled and executed without server and
simplify as possible
4. Creating the issue and attaching the case to the issue
5. Additionally porting the java script files to a server to make online
testing available.
And let me go step by step.
/*If you have an issue with locale change, then create a test case I can
run locally that uses a bundle I have (like one from Flex) that exposes
the issue. If it is notifications, it should not be necessary to involve
MenuBar or XML. Maybe a string in a Label.*
/If every text in the application is changing with the locale change
except the menubar which is populated with xml, is staying with the
initial locale how can I create the case ?//I do not know any other to
express myself/. /I am open to advises.
/*
Almost all of the past examples you've sent that involve resources have
been simplified by using string substitution. So that's what I did to
this example, and sure enough, the MenuBar did not update, so I proposed
a workaround.*/
All the cases I am attaching the issues are the isolated sources from
the application sometimes does not have any similarity with app except
the bug. I value your propositions.
/*I don't recall asking you to host live examples of these scenarios. I
would only look at live examples if I could not reproduce a problem
locally because locally I have all of the source so I know there aren't
any side-effects from other modules and can re-compile with a change if
needed.*/
I am trying to make it easier for you to view the issue with less effort
but I can see it is going to the opposite direction.
/*For your TitleWindow issue, I just looked at the call stack and could
see that it was another case of s:TextArea.*/
TitleWindow is the case that we have discussed couple of months ago.
Replacing s:TextArea with mx:TextArea need some additional investigation
because the component creation call hierarchy is working different and I
am going to let you know after my investigation.
/*
I'm not going to first try remote debugging. It just isn't efficient for
me. I'm sorry you don't like the way I work. */
My aim for preparing the live demo is not the alternative for the
attached case but the identical working one in case you need to see it
alive.
I am not trying teach anyone or you Alex which way to work, because I do
not want anyone to try to do the same to me, I am just trying to help
you to get case as soon as possible but unfortunately it did not worked.
Do not have any comments on the way you work - like or dislike.
/*
You are welcome to tell me not to help you anymore and get someone else
to help you.
*/Nearly 99% of the time only you are interested and involved in
emulation components and the bugs./**/How can this be possible or
realistic ?
At least why I should think that way ? Of course not. Just want to
express my self.
But if you think this is not helping Royale for improving the emulation
components you just tell me to drop.
/*
*/Thanks,
Serkan
-------- İletilmiş İleti --------
Konu: Re: [apache/royale-asjs] Can not change locale for menubar
constructed via XMLList within declarations (#824)
Tarih: Sat, 16 May 2020 09:00:15 -0700
Kimden: aharui <[email protected]>
Reply-To: apache/royale-asjs
<reply+abnu4sqwu5ue3vgvqfxd6v54zpxq7evbnhhcjgj...@reply.github.com>
Kime: apache/royale-asjs <[email protected]>
CC: Serkan Taş <[email protected]>, Author
<[email protected]>
If you have an issue with locale change, then create a test case I can
run locally that uses a bundle I have (like one from Flex) that exposes
the issue. If it is notifications, it should not be necessary to involve
MenuBar or XML. Maybe a string in a Label.
Almost all of the past examples you've sent that involve resources have
been simplified by using string substitution. So that's what I did to
this example, and sure enough, the MenuBar did not update, so I proposed
a workaround.
I don't recall asking you to host live examples of these scenarios. I
would only look at live examples if I could not reproduce a problem
locally because locally I have all of the source so I know there aren't
any side-effects from other modules and can re-compile with a change if
needed.
For your TitleWindow issue, I just looked at the call stack and could
see that it was another case of s:TextArea. I'm not going to first try
remote debugging. It just isn't efficient for me. I'm sorry you don't
like the way I work. You are welcome to tell me not to help you anymore
and get someone else to help you.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/apache/royale-asjs/issues/824#issuecomment-629667547>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABNU4SVCTHKCFSOIGOD6GGDRR22A7ANCNFSM4M3I4SIQ>.
