Thanks for your tips, Tony. I'm going to try them.
The model will be storing QStrings but I still need to figure out which
class to use: a table widget or a table view, or maybe even a list widget
(view).
On Sat, Oct 12, 2013 at 12:48 PM, Tony Rietwyk t...@rightsoft.com.auwrote:
Hi Alexei,
Hello all,
here is part of my code:
int Parser::SomeFunction(const QString line, int start, int fieldStart,
int fieldLength ) const
{
int end;
..
if (0 == m_pRegExp)
{
..
}
else
{
#ifdef KNOWN_PATTERN
end = 19;
#else
QRegularExpressionMatch match =
On sábado, 12 de outubro de 2013 12:28:01, Michael Videlgauz wrote:
So it seems to me that QRegularExpressionMatch creates a copies of each
line and does not release it. What am I missing here? Thanks!
Why do you think it doesn't release it? Your QRegularExpressionMatch object
goes out of
Well, in general I would consider working with this approach and
automatically adding those transitions between the start state and all other
states. QTransition could be derived to QRecoveryTransition that throws only
if a QRecoveryEvent is posted.
But then we would need to keep some
