I not use custom motherboard with cheaper cpu .... so not see that problem (malloc and other ...) probabily because smart pointer c++14 not needed ...modern QT interface required QtQuick programming script ... the "old" method (preferred until 2015, unique until 2012) c++ is stil valid and in major part i prefer that .... but if you use a dinamic screen like QGraphicView controls QLM is more helpful and smart ... nothing to do with memory consimpion concept programming (C like) obviusly ... really memory compsumpion is not my problem from some time .... more or less from 2012 when study OpenCV2 and matrix usage. For sure in 1994 (in scool period) I study assembler on 8080 cpu so there was some memory leack problem .... after newest Intel i series ... i see memory leak only if not reset or delete some matrix memory for image capture part.
bkt Il giorno dom 9 dic 2018 alle ore 21:46 Nicklas Karlsson < nicklas.karlsso...@gmail.com> ha scritto: > On Sun, 9 Dec 2018 17:17:43 +0100 > theman whosoldtheworld <bleachk...@gmail.com> wrote: > > > most part of my gui is over dynamic memory obviusly. Istead shared_prt i > > prefer use array, vector or smart pointer .... using thread or qthread > and > > my preferred container for share data group around my app is vector > declare > > in these manner : > > static std::vector<SendCoord> VectorCoord; > > > > for example for shared x,y,z coord to graphical OpenGl QgraphicaView > (that > > show my robot model, moove equal to real robot), or modify these coor > based > > a targhet position of my visionsistem (based on OpenCV3 C/c++ language > > mixed). > > > > I undertand well you question? > > Yes I think so. My prefer order of memory allocation is: > 1. Local variable, this is in sort of dynamic but deterministic most > probably from stack. > 2. Memory allocated for program life time, may be local or global. > 3. Dynamic memory allocation. > (1.) and (2.) I think work well in real time while (3.) most likely have > problem with determinism at least in the case a heap is used. > > Your method of memory allocation seems good. I have often seen examples > with malloc and typecast which does not feels good although there may be > cases it is needed because of limited amount of stack. > > > QTpyton is not very intersesting for my. Actually work a lot over > QtQuick & > > QML. But I use normally c++ for shred data around gui and thread so java > > part is only for the graphical part of gui. In addiction i'am not a good > > programmer and with java i also bad. I study java for only 1 mounth 2 > hours > > a day ... and my ability is only on connect button and other graphcal obj > > to main part of app. > > As I remember in the development environment for QT it is no problem to > use C++ for graphics and there is graphical editor to build GUI. I tried QT > only and once and this case used C++. > > > _______________________________________________ > Emc-developers mailing list > Emc-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-developers > _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
