Hi aarlauskas,
I am sorry that I did not see your request for support earlier. I must have missed it somehow.
(1)
... collapsed or expanded? At the moment its so random ...
The status is saved in the so-called
localStorage. It is not random. This means it is bound to the browser and current user. Also the selection of visible/hidden tabs of default AppGini table views is stored there. More about localStorage:
https://developer.mozilla.org/en-US/doc ... calStorage
I really would like some sort of control about this, I need this to be always collapsed
I will check if I can implement such an option. But that new function must be compatible to earlier versions.
(2)
Setup tabs, save the record, fields goes random out of tabs
I know from conversations with many other customers that the tabs basically work. I myself also use them every day in my projects. I can not reproduce the described behaviour.
There was a bug (reported in April or May 2020 (?)) about certain field-types which were not moved into tabs if user had no edit permission. This bug has already been fixed in the past. Are you using the latest version? Check console output of dev-tools, please.
In General:
If a certain function of the AppGiniHelper library is not executed, it is usually because the source code before it is buggy. You can see this by the (red) error messages that appear in the console tab of your development tools. If a part of your code contains errors, usually the rest of your code will not be executed. I would recommend to always keep an eye on the console output. And don't forget to clear browser cache after changing CSS or JS.
(3)
Data picker works depends on user permission
Can you please explain what you mean. What is "data picker"?
(4)
... its beta, unsupported function ...
There are dozenz of functions included in the library and fully supported. In addition to the purchased functions, we provide functions that can help one or the other of you - free of charge. You may use them "as is" if they help you. It's a free bonus. Many of these functions make it into the next version. Until then they are a free gift. As in so many other software, you are
not obliged to use these BETA features.
A few thoughts
Is it better not to provide new functions? I personally think it is good to provide additional features (for free), because I myself and a few power-users can test these features over several months and provide helpful feedback until they are mature enough for a release. But of course, if this is not seen as a bonus, but I am raising your expectations for more and more free, 100% bulletproof features for any constellation in the world, then I should consider to stop providing BETA features in the future.
--
I am very sorry that you are dissatisfied. I can guarantee that the functions you complained about basically work, otherwise almost all customers would complain about them. Almost always when an actual
bug was reported, I provided a workaround the same day and fixed the bug in the next version. From my experience with the support requests I receive, more than 90% of the problems lie in the self-written source code and lack of experience with javascript or PHP syntax. Often the mixing of PHP (server side) and javascript (client side) is also a problem.
It is very important that syntax errors in the code are eliminated. As long as the code is not error-free, certain functions of our lib cannot be executed.
Recommendations:
Once again, I'm really sorry that I did not see your support request. Usually I immediately react to bugreports. And in addition I help many people here promptly, if they have problems with programming or problems of understanding - if I see a solution and if I find the time for helping. Unfortunately I cannot answer every question here in the forum immediately. But there are many experts who can help and who contribute many many helpful articles almost every day.