On Friday 29 May 2015 16:27:59 Denis Shienkov wrote:
> I don't know as how will look the CanDevice (derived from QIODevice),
> because QIODevice::read/write methods has not sense. Because, what is
> happens in case I want to write half (or part) of CAN message?
>
> IMHO, this is non-trivial issue
On Friday 29 May 2015 13:19:36 Al-Khanji Louai wrote:
> > I guess I was expecting something higher-level... :)
>
> One step at a time. :)
I'm all for it, but I think one should *first* implement the buses/protocols
before trying to put an abstraction on it. The latter requires insight that
only
On 05/29/2015 04:27 PM, Denis Shienkov wrote:
>
> So, any payload of data is in 8 bytes.. and all of input/output is
> carried out by messages, but not separate bytes (as in
> sockets/pipes/serialport).
>
> I don't know as how will look the CanDevice (derived from QIODevice),
> because QIODevice::r
Hello dev list:
Qt 5.4.1.
At the top of qqmlimport_p.h, it discusses how it is NOT part of the QT API
and subject to change.
In qqmlengine.h, there is addImportPath( ) to allow qqmlimport to resolve
types using a module/qmldir file.
But ByteArray derived components have no equivalent treatment:
On Friday 29 May 2015 10:55:40 Soraya Santana de la Fe wrote:
> xx.obj : error LNK2019: unresolved external symbol
> __imp__q_atomic_increment referenced in function ...
> yy.obj : error LNK2001: unresolved external symbol __imp__q_atomic_increment
> xx.obj : error LNK2019: unresolved external symb
Hi All,
> Actually, reading the Wikipedia entry on the CAN bus diagonally, CAN only
defines the frame format, addressing, arbitration and the physical layer.
I don't know what is in Wiki, but on real world (from the user point of
view), to communicate between the CAN devices are used the usual CA
I wonder if you also need hot-plug detection?
> On 29 May 2015, at 11:43, Viironen Kalle
> wrote:
>
>
>
> On 28/05/15 09:22, "Knoll Lars" wrote:
>
>> On 26/05/15 20:14, "Thiago Macieira" wrote:
>>
>>> On Tuesday 26 May 2015 17:40:05 Viironen Kalle wrote:
On 26/05/15 19:42, "Thiago Ma
> I guess I was expecting something higher-level... :)
One step at a time. :)
Louai
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
On Thursday 28 May 2015 18:19:32 Rutledge Shawn wrote:
> On 28 May 2015, at 13:35, Marc Mutz wrote:
> > Please don't overengineer this. If this is about CAN, call it QtCanBus.
> > If it's about i2c, call it QtI2cBus. These are separate libraries. You
> > get the idea. This is not like the web (ftp
Another experiment. I've added separate classes for CubeTexture and
VolumeTexture
https://github.com/ABBAPOH/imagedocument/blob/textures/src/lib/cubetexture.h
https://github.com/ABBAPOH/imagedocument/blob/textures/src/lib/volumetexture.h
The idea for Cube texture is an ablitity to create from/conv
On 28/05/15 09:22, "Knoll Lars" wrote:
>On 26/05/15 20:14, "Thiago Macieira" wrote:
>
>>On Tuesday 26 May 2015 17:40:05 Viironen Kalle wrote:
>>> On 26/05/15 19:42, "Thiago Macieira" wrote:
>>>
>>>
>>> >On Tuesday 26 May 2015 15:19:26 Hausmann Simon wrote:
>>> >
>>> >>Good point :)
>>> >>I
Hello everyone!
I have been experimenting some problems after compiling Qt 4.8.6 with
win32-msvc2008 platform . Using this configuration:
*configure -debug-and-release -prefix
C:/libs/3rdparty/qtfw_4_8_6_1/lib/windows/x86 -opensource -platform
win32-msvc2008 -qt-sql-mysql -plugin-sql-mysql -I
C:/
Online repository updated! Meet CMake 3.2.20150529 :-)
Online installers for Linux and Windows are available at the links below.
> On 29.04.2015, 16:57, "Konstantin Podsvirov" :
>> Two installer collected in Debian 8:
>>
>> http://ifw.podsvirov.pro/cmake/cmake-master-i386-online.run
>>
>> http://
13 matches
Mail list logo
