Alandor

I see. Thanx very much to all you helping to create such an amazing and useful tool. I am glad to help in anything I can. Greetings, - Alandor -

Well BodoWitcha, I always already indent all the structure and use the right capitalization so actually no need for tidy function. Besides I discover it changes completely the way I use comments which I don't want. And about the 0.45.00 I tried it and this time instead of just a little comment about paths creates an error window related to the program not be able to load the include files probably due to some problem with paths. When the path appears it mixes relative and absolute paths (ex. c:\scripts\script1\.\includes\include1). I lately have no much time so I just use the 0.44.2 when needed the debugger. What I don't understand is why is only me getting this error. Greetings

BodoWitcha, sorry for the late answer, I have some medical issues that prevent me of using the computer. The truth is I don't know what exactly is the "Tidy" function and for what is used for. Actually my problem was just the debug doesn't seem to work with paths the same way since 0.44.3 version. It is not a problem related to anything written on the very own script as the same script can be debugged perfectly with 0.44.2 or previous. I will try with the latest version and post the result. Thanx very much.

Stumpii, sorry for the late answer I couldn't check it out sooner. I get the same error, this time with a bit more information. The exact error is: "The debug file could not be created. (The path is not of a legal form.)". It is weird as 0.44.2 or previous work perfectly. Hope this helps, and if you need more information just ask. Thanx

Hi, Stumpii I keep getting an error since version 0.44.3 saying "The debug file could not be created". It is strange as with previous versions I don't get that error and I can use the debug perfectly. Thanx.

I see. Thanx again for the advices. Kylomas, actually I think your idea would work perfectly too in my case, although using IsNumber() easier this time but I will keep the tip for other possible scenarios. Thanx. Greetings.

Well, about one hundred more or less. Not really large, just tend to call large array an array with more than 10 elements.

Glad to help. And actually I am the one who should give thanx to you as you are the one making the hard (and good) work here. Greetings.

czardas, yes, actually is a trick I use sometimes too. This time It was a problem as I needed to work with the empty slots directly. jhcd, you are right, I didn't thought on initialize the array to a non use value when declaring because most of the arrays I was using were large and I don't know how many elements will have in declare time so It didn't came to my mind, but I am afraid I will have to create a very large array and initialize this way sometimes. MHZ, yeah, actually It is really "funny" how sometimes things that seems complicated at user level can be very simple at programming level and the same time simpler ones can be really complicated. Thanx very much to all of you for your responses and help. Greetings.

FastFrench, I have looked into it. I used this "code": #include <FastFind.au3> #include <ScreenCapture.au3> Local $dir = "c:\nm5\temp\" _ScreenCapture_Capture($dir & "prueba_udf.jpg", 0, 0, 40, 40) _ScreenCapture_Capture($dir & "prueba_udf.bmp", 0, 0, 40, 40) FFSaveBMP($dir & "prueba_FF", True, 0, 0, 40, 40) FFSaveJPG($dir & "prueba_FF", 100, True, 0, 0, 40, 40) The only difference is when using FFSaveBMP the result bitmap has 3 more horizontal pixels and a vertical black line at right. The other files are the same so the problem is only using FFSaveBMP. I attached the FFSaveBMP and the FFSaveJPG images (the FFSaveJPG is just the same the _ScreenCapture_Capture ones). prueba_FF.bmp

Thanx very much for the help. I think the VarGetType() function will do the trick, thanx MHZ. I would like to ask just one more question, is it possible to know if an "empty" row on an array hasn't been assigned ? I mean an empty arrow and and arrow assigned to "" will not differentiate so, is there a way to know which case is ?? P.D.: Actually my problem was with a numeric only array (not a mixed one) but with empty "slots" in the middle so when comparing I was getting the number 0 treated the same way the empty slots were. I didn't think on use the "Is" functions, I forgot completely them but I have seen now using "IsNumber" possibly is the best way for this case P.D.2: MHZ thanx too for pointing the "Is" functions. I didn't think on use them just because I forgot completely. So my fault, I have seen now using "IsNumber" possibly is the best way for this exact case. I am afraid I was really tired when I wrote my last post and my mind was not working correctly. Thanx again. Greetings.

Hello, I need some help with arrays and the use of zero as a value on them. I would like to know which is the best way to work with as I found pretty annoying to use them on any logical compare operation as it seems to consider an empty string (""), the number zero (0) and a non initialized index exactly the same which is a problem when comparing. How do you work around this issue when working with arrays ? Thanx very much in advance. Greetings.

I will look into it. Actually this is similar to the case I commented to you some posts ago about looking from a bitmap file.

It happened to me using FFSnapShot(0, 0, 0, 0, 1) or giving coordinates. Same exact coordinates used on the _ScreenCapture AutoIT built-in UDFs fit perfectly the screen capture region. I always notice this after use FFSaveBMP but really didn't checked if this happens on memory too.

FastFrench, I would like to notice a bug when taking snapshots. There is always a one pixel vertical line (black most times but I have seen white too) added to the right side of the snapshot. Greetings.