Hi,

We appreciate your feedback. The reason for that was due to implementation details and that maybe changed. However that should not matter to you at all because once you use the final file list, you would almost certainly want to remove the temp file list as nobody want to see two file lists (we should probably change our sample to avoid further confusion as well).

If you do not use the final file list (neither set FinalFileLocation nor use AJAXPostedFileList), the temp file list would be kept and you will be able to delete it.

So basically there are the temp list and the final list. The first thing you do is to choose which list you want to work with. Once you pick a list, regardless which one you pick, that list will work for you. I understand that you may feel confused about having two lists. But you should only look at one.

To sum it up, what you need to do is:
1. Use LayoutTemplate to remove the temp file list;
2. Implement your own UI to work with AJAXPostedFileList control to display/modify the final list;

If you are not sure about how to use LayoutTemplate, you can find a sample at here:

http://demo.essentialobjects.com/Demos/AJAX%20Uploader/Advanced%20UI%20Customizations/Demo.aspx

The previous sample we provided already contains code about how to use AJAXPostedFileList.

We believe the file list issue has been thoroughly discussed through this post and your previous thread. So this concludes our last reply about the file list issue. We will no longer answer any questions or making any further comments on this topic to you.

Thanks

Hi,

Which term doesn’t really matter much to you or to us. We are definitely not saying that we will never change/improve the product, but this additional implementation details is just some extra information we disclosed to you while explaining the product to you. As we have already explained, this “implementation detail”, or “bug” as you would prefer to call it, does not affect what you are trying to do at all. So we do not believe this should matter to you, even though we do think it might deserve a further review to see if anything can be done at all --- for example, certainly changing the sample would avoid further confusion. However the key point is whatever we do on the temp file list has no practical impact on you at all since you are using the final file list --- and it would also work fine as well should you choose to use the temp file list. Either way it would work just fine. You pick left or right either way it would work. You pick to go to left but still keep looking at the right you might stumble on something unexpectedly. There are always rooms to improve this but we do not see this as anything significant so it does not warrant a change or a “fix” as you may prefer to call it. Furthermore, if we do “fix” it, there is no guarantee that we will “fix” it the way you wanted.

We do not have a refund policy on this. We encourage you to fully evaluate the product and try competing products before making the purchase. However you can't just buy it, get the license key, use it for a number of months and then find something that is does not go the way you liked and request a refund. In fact we generally do not issue refund once the license key is disclosed. This is necessary to prevent users who place fraudulent orders, get the license key and then request a refund. A disclaimer about this policy is clearly displayed to you before you access the license key. You have to click “I agree” before you can access the license key.

We always try our best to deliver the best product and service. I believe we are being quite reasonable and thorough with you on this one. We thoroughly explained to you how the product works. We clearly told you what you need to do to accomplish your task and pointed you to the necessary sample code. Those together should be more than sufficient for you to move forward on your project with little to no effort.

We appreciate your feedback but we would certainly disagree with accusations such as “do not properly handle post back”. We will work with you as reasonable as we can, but a healthy relationship goes both ways, so we would ask you to be reasonable as well.

You must understand that while we try to accommodate you as much as we can, there is still a clear boundary about what we will do and what we will not do. Once you go beyond the reasonable boundary, you will be pretty much on your own. Our priority, which probably is the same as yours, is to do our best to help your project to move forward by getting as much as you can from our product. We will work with you as best as we can to that regard as long as you are reasonable to us, which is a goal we believe we have achieved during our conversation with you as we have clearly explained the product, pointed you to the right direction and all necessary sample code.

As we have already stated, we believe we have been quite exhaustive and now have gone significantly extra miles to explain how file list works to you. So please take this as our final answer on this issue. Once again, we appreciate your feedback and we may review the issue internally. However once a question is answered it is answered and we won’t go on forever. Our last resort would be suspending your account --- we can do that regardless whether you are an active customer or not. Certainly we would not wish to go there unless completely necessary.

Thanks

Hi,

We will work with you as long as you are willing to work with us and follow us. We cannot work with you when we gave you a solution, you ignore it and keep pointing at something else.

We were not clear about your intention at first when you reported “empty file list”. It became clear to us that you wish to work with the final file list, for which we provided sample code and we believed that’s all you needed. However with no apparent reason, you did not like the solution we provided to you and started to pick on a number of other things. For example, you started to state “Ajaxupload should contain all uploaded files in the temp file location until we (the programmer) decides to empty it, not just because a simple post back has occurred”. I understand where this comes from, but those do not appear reasonable to us. As such we have explained to you that we disagree along with our reasons. After that you would point back to the temp file list, for which we still do not feel it is relevant to you because the solution we pointed you to will just work fine for you. In your last post you finally mentioned that you do not like LayoutTemplate because you believe it would involve a lot of code (it actually would not, the code is quite minimum). That would clear up the picture a bit.

We are not trying to close a ticket. But if you just insisting us to change the software in a certain way you would like with no clear reason (at least not clear to us), then you are picking a hard route for yourself from the begining. The reason is we have a lot of users and we simply cannot afford to change the software for a single user just because he/she particularly likes it that way. This does not matter it’s a bug, or a feature, or whatever way you call it. Obviously a “bug” would imply a higher priority to be “fixed”, but that’s not always the case. For example, if we were naïve enough to put out a facial recognition feature which immediately to be found very unreliable, then our only choice is probably to remove that feature instead of “fixing” it since it’s not realistic for us to implement such a feature correctly anyway. The point is, we cannot act just because you claim there is a bug, or requesting a refund, or demand us to change. We must fully understand the issue at hand, evaluate different options and then draw a logical conclusion based on that. We would expect and appreciate you to work with us during this process to provide as much information as possible for us to understand your situation, but we cannot guarantee that we will always move in the direction you wanted.

Go back to your original issue, we still believe with the current version using LayoutTemplate is the most feasible option for now. If you have problem with LayoutTemplate, let us know and we will help you. Please try to be specific with your question. As stated early, we cannot guarantee that we will change the product the way you wanted, but we will make our best effort to help you using our product as long as your question is reasonable and clear.

Going further I do see completely clearing out the temp file list during postback MAY be a more elegant solution to you. However we have not fully evaluated the implications on this yet, so I cannot give you a definite answer now. Also because that is not there for you to verify whether it indeed works for you anyway, our final implementation might be different than what you expected. In any case, the point is the LayoutTemplate is immediately available to you while this change is still in the air. However if you wish to wait for this, we will be happy to update this thread again when it becomes available.

Hope this helps.

Thanks