Thiago, I'll describe what happens when our typical exception is thrown,
since conditions are very different from what you describe.
Before any method uses a pointer, it first does a sanity check. If nullptr
it shows a dialog with file/line number and what failed, then throws an
exception to
o it is more specific
> than "Re: Contents of Interest digest..."
> Today's Topics:
>
>1. Re: Exceptions (Turtle Creek Software)
>2. Re: Exceptions (Thiago Macieira)
>3. Undefined symbols when porting from Qt5 to Qt6
> (Corentin Bacqu?-cazenave)
&
*Qt 6.7 > Best Practice Guides > Exception Safety* as currently written
seems very reasonable. We'd much rather see that extended to ARM rather
than abandoned.
This link states that ARM fully supports C++ exception handling:
Our code has thousands of sanity checks, which give an error message with
file & line #, then throw an exception. The event loop swallows the
non-fatal ones so users can continue work.
To do that in Qt we wrap QApplication::notify in a try/catch. It works
fine in Qt 5, and also in Qt 6 built
Yes, that is correct: it's a closed-source app. The plan was to have an
initial free beta period using open-source Qt, then switch to a commercial
Qt license when the paid version is ready. Getting bug reports is worth
the loss of a few possible sales.
However, if Qt Group wants to back-charge
We are ready to release a free alpha version of our accounting app for Mac
& Windows. The plan is to use LGPL while still in beta, then switch to a
commercial license and static Qt when it's ready to sell.
Will the switch cause licensing problems?
How do people usually distribute QT for dynamic
n 2023-11-29 18:05, Turtle Creek Software wrote:
> > We deleted build folder, fiddled with settings, and deleted Qt
> > completely a couple times with fresh installs of Qt 6.6.1 for MacOS.
> > None of that was successful. The fresh installs had problems
> > auto-de
cD
On Tue, Nov 28, 2023 at 2:43 PM David M. Cotter wrote:
> Also try copying your build settings from the old kit to the new kit
>
> > On Nov 28, 2023, at 11:43 AM, David M. Cotter wrote:
> >
> > Try deleting your build folder
> >
> >> On Nov 28,
After updating to Qt 6.6.x, we are getting a "No rule to make target .
Stop." error.
Are there instructions somewhere for how to update/fix it? Google didn't
produce anything.
Thanks, Casey McD
___
Interest mailing list
Interest@qt-project.org
What's the best way to remove all auto-formatting in the latest QT
Creator? It really seems to like spaces not tabs.
Preferences--Text Editor-- Behavior tab policy seems to be ignored.
Preferences--C++ -- Code Style-- Formatting Mode: Disable uses tabs, but it
autoformats on save even if
...
Thanks, Casey McD
On Tue, Jul 4, 2023 at 12:01 PM Sze Howe Koh wrote:
> On Mon, 3 Jul 2023 at 20:49, Turtle Creek Software
> wrote:
> >
> > To diagnose a recent problem, we needed to install Qt on several
> different computers with different Qt and OS setups.
> >
> &
To diagnose a recent problem, we needed to install Qt on several different
computers with different Qt and OS setups.
The open source installer has about a 33% success rate. It gives several
hash and socket time-out errors along the way, then often aborts
completely. At that point it deletes all
n replying, please edit your Subject line so it is more specific
> than "Re: Contents of Interest digest..."
> Today's Topics:
>
>1. QDateTime::fromString does not work with Qt::RFC2822Date
> (Alexander Dyagilev)
>2. Re: Void pointers for Mac ARM (Turtle
compiler handle #pragma pack (2) ?
Thanks,
Casey McDermott
TurtleSoft.com
On Mon, Jun 19, 2023 at 2:50 AM coroberti wrote:
> On Sat, Jun 17, 2023 at 8:12 PM Turtle Creek Software
> wrote:
> >
> > Our app contains some old C-ish C++ code from an early 90's database
> calle
Our app contains some old C-ish C++ code from an early 90's database called
NeoAccess. It often uses function pointers with void pointers as
parameters. Their code works OK for Mac & Windows, when built with the
latest Qt5 on Intel.
The code also builds OK with the latest Qt6, but running it on
pports x86 releases)
>
>
>
> Apple started using Arm64 in 2020….
>
>
>
> So not really a “jolt every 3 years”. You have had 3 _*total*_ jolts over
> the course of 30 years.
>
>
>
> --
>
> Mike Jackson
>
>
>
> *From: *Interest on behalf of Turtle
&g
We sell to construction companies. They are not computer geeks, and often
run the original OS until the machine dies. Given the flakiness of some
Mac OS upgrades, that may be ideal policy.
Apple moves far too fast with chip, OS and language changes. It's hard for
small developers to keep up. We
a lot to be said for
consistency between development apps also.
Casey McD
On Sat, Dec 3, 2022 at 3:56 PM A. Pönitz wrote:
> On Fri, Dec 02, 2022 at 07:24:56PM -0500, Turtle Creek Software wrote:
> > The last few updates to QT Creator have made small changes to the user
> > interf
The last few updates to QT Creator have made small changes to the user
interface, annoyingly.
Using the latest, I weirdly kept seeing preprocessor output. Huh? Turns
out Follow Symbol Under Cursor moved from #2 to #3 in the right-click
menu. When using a command 50 times a day, one clicks by
It appears that the problem may be caused by GitHub. Its default is to
change line endings to suit the platform. The behavior can be modified with
a .gitattributes file so we are fiddling with that now.
We switched to it last week because BitBucket/SourceTree became unusable on
Windows. They
We just started moving a Mac project to Windows.
When reading text resources into a QString, the Win version automatically
replaces all /n line endings with /r/n. That screws up our line parsing.
The code creates a QString from QFile:readAll(), and the change happens
somewhere in that
I tried putting the button inside a QFrame, but it has the same problem.
Casey McD
On Fri, Jun 11, 2021 at 10:05 AM Volker Hilsheimer
wrote:
> > On 11 Jun 2021, at 13:52, Turtle Creek Software
> wrote:
> >
> > Here's more info on the weird QTableWidget problem we're seein
we can put the button into, that will
act as a click barrier. Something less extreme than a dialog.
Casey McD
On Fri, Jun 11, 2021 at 10:05 AM Volker Hilsheimer
wrote:
> > On 11 Jun 2021, at 13:52, Turtle Creek Software
> wrote:
> >
> > Here's more info on the weird QTabl
Here's more info on the weird QTableWidget problem we're seeing.
One of our data entry fields uses combination of widgets: a QLineEdit
subclass with a linked QToolButton subclass next to it, and a QListWidget
subclass that drops down underneath. It acts kinda like a combo box, but
better for
We have a QTableWidget with cells containing our QWidget subclasses. One
of them adds a temporary popup menu button and a scrolling list when
clicked.
They display OK, but clicking on them falls through to the cell widget
behind them. raise() didn't help.
We can intercept all clicks and figure
>> Hi Casey, welcome to the ML. I'd like to respond to some of your
comments. I hope you don't mind me addressing them out-of-order.
Thanks, that is very helpful. I guess after a few years one gets to know
the personalities!
My definition of stability would be a platform that lets existing
In general, I agree with Roland about the need for stability. The past 20
years we've spent most of our programming time just keeping up with Mac OS
changes. Meanwhile the Windows competition has been adding features.
We want a platform that lets our C++ code be a cash cow, without all the
Re: willy-nilly
I find this discussion interesting, because we ranted on the Cocoa-dev list
for a while and probably sounded a lot like Roland. That was after we
spent 3 years porting our C++ desktop app from Mac Carbon to Cocoa, and
barely got half done. With huge effort we might have finished
28 matches
Mail list logo
