Ingo,
> If you really want a list of the bugs please take a look at this ng
> - AnsiToOem()
> - Preview
> - TReport
> - TLabel
> - Xailer.res
> - TIni:GetSection
> - TDbfDataSet
> - TDBBrowse
Sorry, but you are certenly unfair with your critics. I am sure almost none
of your bugs reported were critic and some of them are just cosmetic issues.
It seems you have forgot that you boughht a PRE-RELEASE version and BTW any
of your questions has been asnwered and corrected in record time.
> Sorry, without the sourcecode of Xailer I can not see how the mm to pixel
> conversion works. I can only tell you what happened. Maybe I can separate
> this part of my application when I finished it but now I have a lot of
> work
> in front of me.
Up to you. Other guys have no problem making a small sample that we can
reproduce to fix our bugs. I hope you find the bug yourself, if you haven't
do it yet.
> I'm yearning for the new (and fixed) release maybe it will be looking
> better.
I really expect so, but if it does not, be free to ask for a refund.
Best regards,
"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
news:440d98ba$[email=
1@ozsrvnegro.ozlan.local...]
1@ozsrvnegro.ozlan.local...[/email]
>
> Ignacio,
>
> you're asking for a list of the bugs I found?
>
> I informed you about them here and in the public ng. Remember sometimes I
> had to write again and again to convince you that there was a bug in
> Xailer
> and not a mistake by myself.
>
> I decided me on Xailer because I'm still the meaning that it is the best
> developing environment for all the xBase-developers especially the one
> coming
> from FiveWin. But beside the time I need to learn the new dev.-environment
> I must spend much time to find out if it is a bug in Xailer or a bug in my
> code when something was going wrong here even though it is working in the
> 16-bit application.
>
> If you really want a list of the bugs please take a look at this ng
> - AnsiToOem()
> - Preview
> - TReport
> - TLabel
> - Xailer.res
> - TIni:GetSection
> - TDbfDataSet
> - TDBBrowse
>
> for example, but I hope it was only a rhetoric question of you.
>
> The printer problem I could only locate in the line of the conversion
> call.
> Sorry, without the sourcecode of Xailer I can not see how the mm to pixel
> conversion works. I can only tell you what happened. Maybe I can separate
> this part of my application when I finished it but now I have a lot of
> work
> in front of me.
>
> I'm yearning for the new (and fixed) release maybe it will be looking
> better.
>
> Regards
>
> Ingo
>
> "Ignacio Ortiz de Zúñiga" <
NoName@xailer.com> wrote:
>>Ingo,
>>
>>> now I have more problems with the bugs in Xailer than with transfering
> my
>>> sourcecode.
>>
>>Please, would you mind to give a list of those bugs. I will highly
>>appreciate your feedback. We know that moving to a new developing
>>environment is not easy, but please be patient and give your self the time
>
>>to learn Xailer
>>
>>> The error must be caused in the line of converting cm to pixel and as
> I
>>> found
>>> out now it occurs if Canon Pixma iP 4000 is selected. The difficulty
> is
>>> that it happens not every time.
>>
>>I guess you are wrong, the routine for converting cm to pixels DOES NOT
>
>>CALL ABSOLUTELY any API function, IS JUST A BUNCH OF ARITHMETICAL
>>CALCULATIONS. So I guess the problem is not there. BTW, if you are able
> to
>>reproduce your bug on a simply application we will be glad to do some
>>research.
>>
>>Regards,
>>
>>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
>
>>news:440d647a$[email=
1@ozsrvnegro.ozlan.local...]
1@ozsrvnegro.ozlan.local...[/email]
>>>
>>> Ignacio,
>>>
>>> the lines with ProcessMessages() are one try to workaround. I deleted
>
>>> them.
>>> Mwin.exe is the project I'm building with Xailer and it was running from
>>> the IDE when the error occured. It is not a 'malicious' software. It is
>
>>> the
>>> 16-bit software I'm trying to convert from FW16 to 32 bit by Xailer.
>>> Till
>>> now I have more problems with the bugs in Xailer than with transfering
> my
>>> sourcecode.
>>>
>>> The error must be caused in the line of converting cm to pixel and as
> I
>>> found
>>> out now it occurs if Canon Pixma iP 4000 is selected. The difficulty
> is
>>> that it happens not every time.
>>>
>>> I had hoped the problem is known by otherones but nevertheless thanks
> for
>>> answering.
>>>
>>> Ingo
>>>
>>> "Ignacio Ortiz de Zúñiga" <
NoName@xailer.com> wrote:
>>>>Ingo,
>>>>
>>>>I highly recommend to take off those ProcessMessages(), but I do not
>>>>think
>>>
>>>>that are the cause of those LogDebug lines.
>>>>
>>>>Be aware that the LogDebug() mechanism built in Xailer is just a
>>>>connection
>>>
>>>>with the standart OutputDebugString() API function that is internally
> used
>>>
>>>>by a lot of software, and even Windows itself. In your case, I almost
> sure
>>>
>>>>that those lines are not generated by Xailer, but by a 'mwin.exe'
>>>>program
>>>
>>>>that it seems to be malicous software.
>>>>
>>>>
http://www.bleepingcomputer.com/startup ... -7941.html
>>>>
>>>>Best regards,
>>>>
>>>>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el
>>>>mensaje
>>>
>>>>news:440d4d7d$[email=
1@ozsrvnegro.ozlan.local...]
1@ozsrvnegro.ozlan.local...[/email]
>>>>>
>>>>> Hi,
>>>>>
>>>>> after selecting the printer I'm converting the array with the print
>>>>> positions
>>>>> from cm to pixels with the following code
>>>>>
>>>>> WITH OBJECT Printer:oCanvas
>>>>> :oFont:=oFont
>>>>> :nMapMode:=mmHIMETRICS
>>>>> ProcessMessages()
>>>>> For nX:=1 TO LEN(aPos)
>>>>>
>>>>> aPix[nX]:=:PointToPixels((aPos[nX,2]*100)+nLeft,(aPos[nX,1]* 100)+nTop)
>>>>> ProcessMessages()
>>>>> next
>>>>> :nMapMode:=mmPIXELS
>>>>> END WITH
>>>>>
>>>>> aPos is STATIC
>>>>> aPix is LOCAL
>>>>> Sometimes - not always - I got the GPF as shown in the picture and the
>>>
>>>>> following
>>>>> LogDebug lines
>>>>>
>>>>> #1: HEAP[mwin.exe]:
>>>>> #2: Heap block at 0019F0B0 modified at 0019F194 past requested size
> of
>>> dc
>>>>>
>>>>> #3: HEAP[mwin.exe]:
>>>>> #4: Invalid Address specified to RtlFreeHeap( 00150000, 0019F0B8 )
>>>>>
>>>>> #5: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #6: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #7: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #8: HEAP[mwin.exe]:
>>>>> #9: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>>
>>>>> #10: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #11: HEAP[mwin.exe]:
>>>>> #12: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #13: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #14: HEAP[mwin.exe]:
>>>>> #15: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #16: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #17: HEAP[mwin.exe]:
>>>>> #18: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #19: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #20: HEAP[mwin.exe]:
>>>>> #21: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #22: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #23: HEAP[mwin.exe]:
>>>>> #24: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #25: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #26: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #27: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #28: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #29: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #30: HEAP[mwin.exe]:
>>>>> #31: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #32: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #33: HEAP[mwin.exe]:
>>>>> #34: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #35: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #36: HEAP[mwin.exe]:
>>>>> #37: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> Any idea what's wrong with my code?
>>>>>
>>>>> Thanks in advance
>>>>>
>>>>> Ingo
>>>>
>>>>
>>>
>>
>>
>