Thread: Ux branding 3d for luna nextgen

All versions of iGO are designed by human beings thinking according to their own logic, which will never make it a perfect program. The processing of KMLs is borrowed from theoretically proven methods of analysis, but when they are added to particular needs the risk factor increases, it may therefore happen that it is considered that the syntax of a KML is not rigorous to the theoretical definition and that iGo accommodates it either by ignoring it case of a closing tag that is missing but not vital that even a human eye will not see. On the other hand in more severe cases igo will not process the KML that I until the location of the error and will ignore the rest of the file.

If it is proven that the conversion program used to transform the CSV into KML introduces syntactical errors in the layout of the tags that does not make it a bad program, it does the job for which it was designed and theoretically it should do it perfectly wrong otherwise the fault lies with the designer who must either revise his copy by reconsidering his programming or re-check the validity of the parts of programming borrowed elsewhere, this in order to avoid the conversion bugs which are reported and which igo might not be able to overcome

Nobody is to blame, neither the user of the program in whom he fully trusts, nor the person who would notice a discordant event likely to lead to a malfunction for iGO, this should not prevent from being able to report the patches that the can be done manually without having to offend the sharer

Be