Is there anyway we can send out fix string messages directly without load it to the quickfix.Message first.
The reason we would like to do that sometimes there are some custom tags that will be gone missing after we parse the string to the object without having proper DataDictionary
Thanks
No, there just isn't a way to do this.
You need to have an accurate DataDictionary. Editing the DD is not difficult.
Often the hardest part is just getting the right info from your counterparty. Sometimes you start with whatever you can get from them and then make adjustments based on what you see in reality.
Related
I try to append HTML in js file. It was OK for SPA mode.
But when I change to universal mode, the HTML can't be appended.
Then I try to set the timeout for append function and it's Ok. The HTML is appended successfully.
I don't understand the reason why?
I just a new member in nuxt, so please help me explain the reason why, and how can I append HTML without set timeout?
Thanks so much!
Without seeing the code you are using to try and implement appending html I can't be certain, but I suspect the process where the appending is to happen is taking place on the server, before it is rendered to the client.
To get around this you could implement the use of process.client to delay the appending.
if (process.client) {
//do what needs to be done
}
The other option would be to use the mounted hook to call to append the html.
As I say, if you post the code you are trying to use it would be possible to show a more detailed answer.
I get SOAP_EMPTY using gsoap, I have searched for a long time and had no answer,SOAP_EMPTY is newly added to gsoap,and it seems I'm the unlucky guy to meet this problem.
Here is where my code come from:https://github.com/miibotree/ONVIF/blob/master/main.c
Now soap_call___tds__GetCapabilities will return code SOAP_EMPTY,I'm now using gdb to track this problem it seems that I need to set a valid soap->id to avoid this problem,but I'm a fresh guy with onvif and don't know how to set a valid soap->id,and now I'm reading various docs about onvif and trying to solve it.
Hope any guys could help me, sinch searching so many docs makes my eyes pain and I still haven't found the answer,thanks.
SOAP_EMPTY is a validation failure. This error indicates than an element/attribute is empty but is supposed to have content. For example an integer value should not be an empty string. The old error generated by older gSOAP releases in this case was SOAP_TYPE which was less informative. In either case, validation fails. The best way to find out is to use soap_print_fault() and soap_print_fault_location()` where the latter call shows the location in XML where the problem is. Our ONVIF testing with gSOAP did not reveal such an issue.
Anyone aware of a FIX utility available online to verify fix messages? ie: accept a fix message and check things like body length length and checksum.
thanks
There is a fix log decoder on https://fixspec.com. When you enter a message it is parsed and items such as checksum and body length are also checked. You need to register to access it, but registration is free.
https://drewnoakes.com/fix-decoder/ is a nice online FIX decoder that supports Checksum(9) and BodyLength(8) tags validation.
No registration required.
One that I know of is ValidFix. There was a link to it on the QuickFix website, but it seems to be missing.
There's a licensed tool called VeriFIX http://www.greenlinetech.com/products/verifix.php.
Pasting it incase if it's useful to you or others.
I'm working on a MVVM application, using MVVM Light and on the whole I'm finding it very nice to work with. I have a nagging issue however and hope someone can help.
I'm using sending instances of DialogMessage from VM to the View to display dialogs. The result is sent back to my VM via a callback, all good so far.
However the result of the dialog (OK, Yes, No, Cancel etc) is sent back as a member of the enum System.Windows.MessageBoxResult. This seems to go against the View/ViewModel separation to me, MessageBoxResult is clearly a type from the UI and so the VM shouldn't be dependent upon this or anything from the System.Windows namespace.
What I'm looking for is someway of using DialogMessage with an alternative callback eg Action<UserResult>; rather than Action<System.Windows.MessageBoxResult>;, where UserResult is a type defined by me to represent the users choice without dependency on MessageBoxResult.
Is this possible or am I being too strict in me desire to keep UI concepts out of the VM?
In regards to the second part of your question, when I started working with MVVM Light I too felt that receiving a MessageBoxResult back in the VM seems a little to UI-oriented.
On the other hand, if only the name was different - such as UserResult as you suggested - would that be sufficient for you?
If only the nameing of the class is a problem, I think you can let it slip. The result Ok, Yes, No, Cancel do not give an indication of whether a MessageBox was shown with buttons or whether it was some other kind of UI implementation (lets say a form with a combo box).
If it still bothers you, you can always create a wrapper for the DialogMessage which will raise the Dialog, get the MessageBoxResult and return a UserResult which can be an enum with the same values (think of it as a simple converter).
But as I said, I think it might be an overkill...
Does anyone know any details on the underlying eclipse builder that sends jobs to the compiler and get its report? and how to tap to it? The level of abstraction that the builder extension offers is too high and the information insufficient. So I implemented an IResourceChangeListener and played with the ResourceDelta in order to get the messages from an IMarker. It works perfectly, however I realized the message is just returning a string. So my question is, how do I do in order to get the type/reference of the object where the error is, what type of error, what class it should belongs to and all available info.
Thanks.
Have you looked at the builder documentation?
And there is also This article by John.
I think between those two and looking at the code you will find everything you need to know.