For some time we are able to declare behaviour callback using -callback attribute instead of behaviour_info/1 (which in my opinion is more convenient). But, the edoc application seems to be unable to discover such attribute. Still, release notes suggested, that this issue was already fixed in version 0.7.10 (http://www.erlang.org/doc/apps/edoc/notes.html). Did anyone encounter similar problem and was able to overcome it?
I think the open issue 3211 is talking about a similar issue.
There is a comment mentioning that commit 715bb80 enables edocs to identify callbacks, but I am also seeing this functionality in the brod project -- hexdocs.
Related
I cannot get the cordova-whitelist plugin into the staging map of Xcode via Ionic. I have tried removing the whitelist plugin, tried adding it back (by installing), yet still nothing at all. ionic prepare ios normally solves these issues for me, but the whitelist plugin is still not being added.
What is the best way to fix this problem?
Quick answer for all those out there facing the same problems because of the lack of proper documentation: the cordova-whitelist-plugin is not meant to be for iOS, which is the reason why it's not going into staging. Thus: this is not a problem at all, as it's just the way it should work.
Source: https://forum.ionicframework.com/t/how-to-get-the-cordova-whitelist-plugin-into-staging-in-xcode-via-ionic/97058/2?u=1bjk903
I am currently working on an old iOS app. I don't have much idea about cordova.
I am stuck at one place, where code uses window.requestFileSytem . There is some code in success callback of this function.
When I debug, I found that success callback is not triggered. I am not able to find any thing about this function in latest cordova document however there is some thing in older document.
So I am worrying about is window. requestFilesystem method is deprecated. If so then how can I achieve same thing in latest cordova.
window.requestFileSystem(LocalFileSystem.PERSISTENT, 0, onReqFileSystemSuccess, null);
Any help would be appreciated.
Reviewing #iammilinds answer I have to correct my initial statement:
The window.requestFileSystem method is non-standard and should not be used. See the linked MDN docs.
Yet there are code examples containing the window.requestFileSystem method in the documentation for the cordova file plugin here or here (searching for window.requestFileSystem might help as the dcos are pretty large).
So regarding your initial problem: I'm afraid you'll have to debug it. Maybe checking the browser's console might give you a hint what's wrong. Or try to add an error handler to window.requestFileSystem as the last parameter like so:
window.requestFileSystem(LocalFileSystem.PERSISTENT, 0, onReqFileSystemSuccess, onErrorLoadFs);
Yes, it's deprecated.
It's implemented only by Chrome as of today.
This is what Mozilla page for Window.requestFileSystem() for this API says:
Non-standard
This feature is non-standard and is not on a standards track. Do not use it on production sites facing the Web: it will not work for every user. There may also be large incompatibilities between implementations and the behavior may change in the future.
Above notice can be seen for several other "Files & Directories" APIs. However, below notice is significant and is read only for this particular API.
Even compared to the rest of the File and Directory Entries API, requestFileSystem() is especially non-standard; only Chrome implements it, and all other browser makers have decided that they will not implement it. It has even been removed from the proposed specification. Do not use this method!
The correct usage is as discussed in this post: How to use window.requestFileSystem of FileSystem API?
window.requestFileSystem = window.requestFileSystem || // Chrome
window.webkitRequestFileSystem; // Others
Recently I got the error "automation server can't create object", for which I know the solution is to add your website to trusted sites and enable the setting: "Initialize and script ActiveX controls not marked as safe for scripting". But since this is a security issue, I searched for an alternative workaround but came up with nothing.
So, I am wondering if there is any other work around for this?
Please look at this SO question. Check if you did everything that was discussed there.
The first thing is to implement IObjectSafety interface. Then sign the activex and installer and CAB. You might also want to look at this example how to implement an activex.
i update ZF from 2.0.6 to 2.1.1, Zend\Authentication\Storage\Session does not work.
this is my project code, 2 project in 2 vesion, 2.0.6 work, but 2.1.1 hasn't
thanks for help
Make sure that you have restarted your browser after updating. Perhaps it sounds silly, but it is something that is easy to forget. I ran into a problem until doing so myself and have heard of several others encountering problems. Also, check the changelog for the past few updates; I believe it was in 2.0.7 (possibly) that there was an update that would break session management in some situation. I cannot seem to find a reference anymore, but if I remember correctly, it was related to using properties directly on the storage object, e.g. like below.
$storage->something = 'some_value';
If I remember correctly, this is no longer possible and you should use offsetGet and offsetSet instead if you are using the Storage class directly like that. If you are doing like this, it is worth researching this a bit and trying to see if you still get the error with the other approach. Alternatively, you can use the Zend\Session\Container class like below (or more detailed).
$user_session = new \Zend\Session\Container('user');
$user_session->username = 'Andy0708'; // Write to session
$username = $user_session->username; // Read from session
You really have to provide more information in your question so that people can answer it properly. Until then, we can only really guess.
I am trying to use the file:open(....) function in erlang but it doesn't seem to work. I keep getting an {error, eio} exception.
Ive looked into it in the erlang documentation and all i have found is that it is the posix error for input/output... go figure.
The file name im outputting in is in the formation of "C:/directory/file.txt"
Im not sure if this has something to do with it.
Is there anyway i can make erlang give me a more specific explanation to what is wrong?
Thanks,
Jack
Unfortunately I do not know of a way to find out more without peeking inside the Erlang/VM.
If you look in the windows erlang source code there are a bunch of different errors which could cause en eio error. You can find a list of them here. In order to figure out which specific one it is, I would attach with windbg and step through the code as instrumenting and recompiling it on windows is a pain.
You might also be able to use something like Process Monitor to find out which system calls are being made and what they return.