Program crash when using dirread
When you use dirread, the program exits with an OS error window. PixTudio version ¡TRES!, Windows7 x64
program test_error;
//crea una lista de procesos con los nombres de los ficheros
private
int dir_abierto;
string dir_actual;
string fich_temp;
begin
dir_actual = cd();
say(dir_actual);
dir_abierto = diropen(dir_actual + "/*");
say("DirOpen: " + dir_abierto);
fich_temp= dirread(dir_abierto);
say("Dirread: " + fich_temp);
dirclose(dir_abierto);
END
Comments (5)
-
repo owner -
repo owner -
assigned issue to
-
assigned issue to
-
repo owner I cannot seem to replicate the issue in Windows 10, 64 bits with either the latest version of PixTudio from Git nor with the win32 version downloaded from here: http://forum.bennugd.org/index.php?topic=4108.msg65416#msg65416 I have, however, modified the example you've posted to explicitly include the list of imports, as follows:
program test_error; import "mod_say" import "mod_dir" //crea una lista de procesos con los nombres de los ficheros private int dir_abierto; string dir_actual; string fich_temp; begin dir_actual = cd(); say(dir_actual); dir_abierto = diropen(dir_actual + "/*"); say("DirOpen: " + dir_abierto); fich_temp= dirread(dir_abierto); say("Dirread: " + fich_temp); dirclose(dir_abierto); END
Could you please give some more info on how you get the error? Which files do you have in the folder? which imports are you using?
-
reporter OK, it seems I was working on an old version (10-01-2016). I have no issue with "26-01-2016" version, I can read all files on the directory. But, for the record, I have this on pxtb.import file:
mod_dir mod_draw mod_file mod_grproc mod_joy mod_key mod_map mod_math mod_mem mod_proc mod_sound mod_string mod_screen mod_text mod_video mod_say mod_debug
And the files on this directory are "errorDirread.prg", "errorDirread.dcb", "pxtb.import", "compil_tst.bat" and "compil.bat" (the two last are files to compile and compile&run, because binaries are on diferent location).
-
repo owner - changed status to resolved
Thanks for reporting, anyway.
Closing the bug, then.
- Log in to comment
Thanks for reporting.
I'll have a look at this ASAP.