Aチームへの確認ありがとうございます。
最後に1点確認させて下さい。
今回の私のリクエストは仕様上不可能であることは理解できましたが,それは私の用途や現状の設定が特殊であって
通常であれば問題ないということでしょうか?もし私の環境が特殊であることが原因である場合には,具体的にどこが
問題であるか教えて下さい。
また,今後のアップデートにて本問題が改善されるとのことですが,いつ頃になりそうか目安だけでも教えていただけると幸いです。この回答を頂いて本問い合わせをクローズしたいと思います。
I would like to check one point at the last.
I understand that my request is impossible on the specification.
Does it mean that the reason is my purpose of use and current situation are set by unusually way, and if it is set by usual way, there is no problem?
If the cause is that my environment is unusual, please let me know what is a problem in detail.
I heard that this problem is going to be improved by update in the future. Would you tell me when it will be improved approximately? After you answer it, I will stop this question.
I would like the last check.
Although I understood this time(s my request is specifically impossible, that is because of my usage and current setting are special, but usually, it is no problem? If my circumstances are special which is the reason, please tell me what is wrong with me in details.
Also, in the future updating, this issue will be proved, please tell me when it is to be so. If you answer to this question, I would like to close with this isse.
Lastly, could I make sure one more thing?
I understand that my request at this time could be impossible for its specification, but do you mean it is affirmative for normal cases other than my ways are so special for my purpose or current setting?
If my environment is so special for that reason, could you tell me where the problem is specifically?
Also, I knew the following update would improve the problem, when would it be completed roughly? I will close this issue if I receive a reply soon.
I would like to make one last point.
I understand that my request is not possible due to the specifications, but does that mean that my application or current configuration is special and would not be a problem under normal circumstances? If the problem is due to my special environment, please tell me what exactly is the problem.
Also, I was told that this problem will be fixed in a future update, but I would appreciate it if you could give me an idea of when it might be. I would like to close this inquiry after receiving this answer.