Activity for pc
-
pc committed [410a9a] on Code
correctif de prepa_parc.ted
-
refonte prepa_parc.ted pour messages detaillés
-
-decouverte et correction bug dans script prepa_parc.ted
-
Modification pour contourner un bug devenu tres genant de la version 9 de wine
-
version 6.3.5.1 :
-
I am not talking about a bug in the software in question but rather a bug in the sourceforge web server which presents text coming from a file correctly when read and incorrectly with diff option
-
undefined behaviour af character set
-
decouverte et correction d'un bug de presentation de listing de points
-
ajout script pour faciliter le renumerotage pour confection de DA numerique
-
modif mineures et versioning
-
Post Scriptum : I send you the file removed from its sensitive fields which had several deleted records including only one which had been recreated with the same IDU (main key) (record that is deleted and not deleted is 378PC1710027)
-
hi gary, I found the time to look in more detail at the anomaly in question by diving back into the code that I debugged more than 12 years ago. I saw in passing that you removed the "RealDelete" option and that's a good thing: it was buggy. From memory I had also deleted the locking system which was also buggy (but perhaps you have cleaned it up since) and which I did not need. I was able to reproduce and found the system flaw: 1) you take a DBF table that you index on a unique index 2) you position...
-
Hi, Unfortunately, this file contains sensitive data that I do not have the right to distribute. But I can rid it of these and do more in-depth tests. The NDX comes from version 3 of xdb. The versions of dBase are also capricious (DBF is recognized with version 5 but not with version 3, NDX is recognized neither with version 3 nor version 5 - NB: by providing the short names of the files obviously) . The reconstruction of the index under dBase is also imperfect: I thought that the reconstruction...
-
hello garry, And thank you for this response which indicates that the project is in good hands :) I would like to take this opportunity to thank you for your past work: many years ago, I was looking for a way (quickly) to manage dBase files and their indexes for basic and single-user functionality and found your project ( version 3) which I integrated into my project by simplifying it and correcting a few bugs found here and there (without going into the depth of the project). I am attaching what...
-
Good morning, I am a former user of version 3 and was happy to see that the project was not dead. Out of curiosity, I loaded version 4.1.5, compiled it on win64 and linux64(debian) and tested some basic functions with xb_dbfutil. Under Linux or Windows, it is impossible to read an existing NDX index or one created from scratch (reindex), the first and last index also gives anything Under Linux, the output ends with a worrying “Segmentation fault” below the whole session panel@panel-UM350:~$ '/home/panel/Bureau/xbase64-4.1.5/build/debian/bin/xb_dbfutil'...
-
A little feedback after doing some tests with Windows 11, Visual studio 2022 and OWL7: first with OWL6.44-3: -VS2022 still allows you to compile for XP: it is necessary to install the VS2017 tools "BEFORE" loading a project to convert. In this case the project is automatically converted and appears as v141_xp. -small quirk probably in order to avoid potential errors, the /Zp1 option allowing structures to be compressed to the limit of 1 byte, formerly useful at the time when memory was limited, is...
-
We're becoming old farts most of us here Yes sure ! :D If you do move to OWLNext 7, let us know how it goes. I will not miss it. PS: Note that I have already compiled my project with VS2022 using the OWL6.44 libraries (and headers) previously compiled with VS2015. And It seems to go well.
-
We're becoming old farts most of us here Yes sure ! :D If you do move to OWLNext 7, let us know how it goes. I will not miss it.
-
thanks vidar, you're always on top, and bye bye XP :D Perhaps I will try to compile my project with OWL 7 later. I have now been retired for 3 years but the winter evenings are long ;)
-
Hi vidar, Thank you for this quick response, I later saw this option and understood. On VS2022, is it still possible to compile for WinXp? I installed the 2017 SDK on it because it seems to me that it is the last one which still allows me to compile for XP, but I still have an error "Windows 8.1 SDK not found" and it is not offered to me in the installation ...(?) And was VS2017 already compatible with C++17? probably not because OWL version 7 seems to ask for VS2019 in WIKI on the other hand, XP...
-
Hi vidar, Thank you for this quick response, I later saw this option and understood. On VS2022, is it still possible to compile for WinXp? I installed the 2017 SDK on it because it seems to me that it is the last one which still allows me to compile for XP, but I still have an error "Windows 8.1 SDK not found" and it is not offered to me in the installation ...(?) And was VS2017 already compatible with C++17? probably not because because OWL version 7 seems to ask for VS2019 in WIKI on the other...
-
Hi vidar, Thank you for this quick response, I later saw this option and understood. On VS2022, is it still possible to compile for WinXp? I installed the 2017 SDK on it because it seems to me that it is the last one which still allows me to compile for XP, but I still have an error "Windows 8.1 SDK not found" and it is not offered to me in the installation ...(?) And was VS2017 already compatible with C++17? on the other hand, XP is starting to get old (like me ;) ) ...
-
Just a question : I saw vc.mak file and it seems that only version 15 to 17 of C++ are accepted, is'nt it ? Is there some reason ?
-
simplification fichier INI suite à version 6.35
-
correction 2 coquilles
-
Changement de comportement dans la lecture des fichiers de configuration
-
VERSION 6.350:
-
version 6.350 : modification des trois dernieres valeurs du fichier
-
-Amelioration de la detection des signes de mitoyennete dans l'import
-
-Amelioration de la detection des deports d'ecriture (fleches numeros de parcelle)
-
correction defauts mineurs
-
mise à jour des numero de version pour version 6.35
-
Modification appels google http en https (les premiers ne sont plus acceptes)
-
ajout de script pour l'import de fichiers d'adresses locales.
-
modif pour interroger google en https au lieu de http qui n'est plus accepté
-
correction de la procedure 'selection_voie_par_rivoli.ted'afin qu'elle ne prenne pas seulement les numeros de voirie en compte mais aussi les autres types de voies (voies pub, voies privées, ens. imm.)
-
-
osmand changes
-
version 6.3.4.4
-
Home
-
Home
-
version 6.3.4.3:
-
modification dans la fonction TED FileOpenSaveDlg afin de faire
-
version 6.3.4.2
-
-
Well my test results are negative :( The same key seems to work on a computer (with rewriting GPT) and do not on the other. :( it is not a guarantee of trust :(
-
it's more twisted : The USB key is GPT formatted and cannot work properly on MBR systems : during the boot, I have messages that see GPT tables differences and correct them... here is what I have after writing the key by fdisk -l /dev/sdf GPT PMBR size mismatch (2245151 != 60555263) will be corrected by write. The backup GPT table is not on the end of the device. This problem will be corrected by write. Disque /dev/sdf : 28,9 GiB, 31004295168 octets, 60555264 secteurs Disk model: DT Elite G2 Unités...
-
it's more twisted : The USB key is GPT formatted and cannot work properly on MBR systems : during the boot, I have messages that see GPT tables differences and correct them...
-
Hi, I just discover Rescuezilla and tested it for a friend who need this type of tool. First of all congratulations for this work. I just want to report a bug that can be annoying for a novice: The USB key launched on a system containing only this one (we may want to make a USB key clone in complete safety) causes a crash (frozen screen). Hoping this can be of use to you. Best Regards PS: key written with rescuezilla-2.4.1-64bit.jammy.iso
-
Hi, I just discover Rescuezilla and tested it for a friend who need this type of tool. First of all congratulations for this work. I just want to report a bug that can be annoying for a novice: The USB key launched on a system containing only this one (we may want to make a USB key clone in complete safety) causes a crash (frozen screen). Hoping this can be of use to you. Best Regards
-
ajouts de commentaires utiles dans import edigeo/PCI
-
ajout commentaire utile dans un programme TED
-
ajout script pour geoportail et suppression lecture par défaut des fichiers QAl edigeo
-
ajout icones pour geoportail
-
Merge branch 'master' of ssh://git.code.sf.net/p/topographie-cadastrale/code into master
-
version 6.3.4.2
-
Merge branch 'master' of ssh://git.code.sf.net/p/topocad-france/code into master
-
version 6.3.4.2
-
Home
-
Home
-
amélioartion procédure pour correction d'un bug pouvant intervenir en cas de points permis non référencé ayant une etiquette de plus de 30 car (erreur: field is too small)
-
version 6.3.4.1
-
Corrections et simplifications (l'import SHP considere les faces à trous comme faces multiples)
-
-extension de l'import SHP afin d'accepter les types de shapes avec Z ou parametre M
-
apporte une précision lors de l'installation sur la racine d'un disque
-
Home
-
ajout script de sélection d'objet en fonction de la date de mise à jour
-
version 6.340
-
version 6.3.4.0
-
Home
-
Home
-
Home
-
Home
-
Home
-
Home
-
Home
-
Home
-
Home
-
Home
-
Home
-
Home
-
Home
-
Home
-
Home
-
Home
-
Initial Commit
-
pc posted a comment on discussion Open Discussion
Is it still serious, Borland ? (embarcadero) I've tested the free command line compiler BC101 and the IDE : both provide bcc32c that works differently : there are options undocumented and that work with one and not to the other. With the same command line to compile an "hello world" one provide a COFF format and the other an OMF format :( And I don't talk about the documentation that is incomplete and ununderstandable : just an example : the -o option says object file path, but for output by the...
-
Post Scriptum: During compilation I managed to hang the C++ Lang compiler (or make ???) twice and I managed to reproduce the bug : I compile on Win10 : to reproduce the bug, just clic on the window elevator during the compilation (the console window that compiles)
-
Post Scriptum: During compilation I managed to hang the C++ Lang compiler (or make ???) twice and I managed to reproduce the bug : I compile on Win10 : to reproduce the bug, just clic on the window elevator during the compilation
-
Hi Jogy and Vidar, and thanks for your answers. I just took a look at this, and learned some things : 1) bcc32c do not use (needs not) boost library to compile OWL 2) CodeGuard seems to be only for bcc32 (and not for bcc32c) With the job made by Vidar, the correction in borlandc.h shown by jogy, I managed to compile OWL, except this was extremely slow (perhaps because precompiled headers were not set up entirely) and after I corrected a bug that I present to you : hlpmanag.cpp : line 45 : #if defined(__BORLANDC__)...
1 >