Re: [Lazarus] Qt doesn't return proper DC Device Size

2015-05-16 Thread Giuliano Colla
Il 16/05/2015 14:27, zeljko ha scritto: On 05/16/2015 02:15 PM, Giuliano Colla wrote: While trying to obtain programmatically the snapshot of a window, I stumbled into a Qt bug. It turned out that TQtDeviceContext.getDeviceSize always returns a size of 10x10 for any widget I tried. It returns

Re: [Lazarus] Qt doesn't return proper DC Device Size

2015-05-16 Thread vfclists .
On 16 May 2015 at 13:27, zeljko wrote: > On 05/16/2015 02:15 PM, Giuliano Colla wrote: > >> >> While trying to obtain programmatically the snapshot of a window, I >> stumbled into a Qt bug. >> >> It turned out that TQtDeviceContext.getDeviceSize always returns a size >> of 10x10 for any widget I

Re: [Lazarus] Qt doesn't return proper DC Device Size

2015-05-16 Thread zeljko
On 05/16/2015 02:15 PM, Giuliano Colla wrote: While trying to obtain programmatically the snapshot of a window, I stumbled into a Qt bug. It turned out that TQtDeviceContext.getDeviceSize always returns a size of 10x10 for any widget I tried. It returns the proper size only for the full screen

Re: [Lazarus] Qt doesn't return proper DC Device Size

2015-05-16 Thread zeljko
On 05/16/2015 02:15 PM, Giuliano Colla wrote: While trying to obtain programmatically the snapshot of a window, I stumbled into a Qt bug. It turned out that TQtDeviceContext.getDeviceSize always returns a size of 10x10 for any widget I tried. It returns the proper size only for the full screen

[Lazarus] Qt doesn't return proper DC Device Size

2015-05-16 Thread Giuliano Colla
While trying to obtain programmatically the snapshot of a window, I stumbled into a Qt bug. It turned out that TQtDeviceContext.getDeviceSize always returns a size of 10x10 for any widget I tried. It returns the proper size only for the full screen (i.e. if DC=0). For sake of completeness,

Re: [Lazarus] IDE unable to load form due to missing property

2015-05-16 Thread Giuliano Colla
Il 15/05/2015 15:24, Tony Whyman ha scritto: Another thought - at run time an unknown property error might be better reported as a warning rather than as an error. This would be a very welcome enhancement. If the unknown property is actually used in code, it's flagged as an error at compile

[Lazarus] Google APIs - update

2015-05-16 Thread Michael Van Canneyt
Hello, There seems to be a problem with RTTI and dynamic arrays when using the i386 compiler (using register calling conventions). This affects the (JSON) serialization used in the Google APIs. This problem is definitely present in the 2.6.4 compiler. Since that is the compiler used by curr