@jsulm Thankyou so much

@J-Hilk
add_executable(client
client_main.cpp
client_main_window.cpp
client_manager.cpp
client_chat_window.cpp
chat_protocol.cpp
chat_line.cpp
)
target_link_libraries(client PRIVATE database_library)

qt_add_resources(client "images"
PREFIX "/images"
FILES send_icon.png
)

set(MACOSX_BUNDLE_INFO_PLIST ${CMAKE_CURRENT_SOURCE_DIR}/Info.plist)

set_target_properties(client PROPERTIES MACOSX_BUNDLE ON)

This is the CMake file related to the executable I am having prob ton have access to the Microphone. I did setup the Info.plist file.

@__d4ve__ Further to @jsulm's question, you may find it useful to add this at the top of the TrayIconApp constructor/destructor

qDebug() << "Construct" << this; qDebug() << "Destruct" << this;

and this in the slot:

qDebug() << this << "onSyncChanged called with:" << sync;

Then you will see which TrayIconApp object gets created and which object, if any, receives sent signals.

What is the life span of client? In your connect(), client appears to be a stack-based instance of the Client class.

Hello
Thanks for your answer.
I already find this link but I m talking about offline installer. Online installer requires email / password. I have license name + key and I can t us eonline installer because no internet access.
I tried /? and /help and -help and -h but no one is helping for V 4. They all just execute the setup.
It s working for v5.

So, is there a way to install v4 with CLI ?
I will try with same parameters just to test it...

@fontcolorhelp For Ubuntu, try to find qt deb files and download them to install. Ubuntu 22.04 has Qt 5.15.3.

Hello, the new Forum UI and the core was upgraded today by Qt.

You can check the these 2 topics in Announcement here

https://forum.qt.io/topic/155774/forum-update-may-2nd/33 https://forum.qt.io/topic/156456/forum-updated-to-nodebb-3-7-4/2

If you find any issue, feel free to comment on the topic.

@mzimmers said in avoiding the use of hard-coded strings:

I'm trying to determine how best to put all of my labels (using the term generically) into a single location that can be easily modified by a non-programmer. The goal would be to have no hard-coded strings in my code; they'd all reside in some file that could be altered by a technical writer or someone else.

Even if your original labels are written down in English you can still have an English translation. (We do use English translations just for plurals. There is a command to just extract entries containing %n.) Translatable strings can also have an additional comment/description. This can help to clarify (and disambiguate) what you actually meant. Maybe use something to make it clear that a string needs still translation, e.g. instead of using the string My label use something like >>>MY LABEL<<< instead. This makes it easy to spot string not yet translated to English. Or use the variable name as the string to be translated (camelCase or snake_case would be easy to spot as well). Your English "translation" would be the single file for your technical writer.

I would recommend to no longer use Q_FOREACH it is deprecated for a reason! Use the ranged based for loop the c++ standard offers
for (auto &item : container)

less error prone, less conflict with other libraries, faster compile times.

@Sadok_J

Do you use the Online Installer?

i'm not sure what boxes should i check in the personalized installation for me to work with thoses modules and functions

If you are not sure what to pick and just start to use Qt for Qt Widget applications, go for the pre-configured installation.
Don't know what the latest version in Online Installer currently shows, but it says something like
Qt 6.7 for Desktop Development.
Can't do wrong with this. There is QtCreator (the IDE with QtDesigner), the Qt Framework itself and every tool you need to start writing your first app, included

Hi, if you're using the online installer (Maintain Qt) you can select it here:
Screenshot 2024-05-02 at 16.59.44.png

Hi @TyChapin,

Upon connection, the MTU is set to the default value of 23.

That's only a "we don't know yet" default, which is, frankly, pretty meaningless. As per the docs:

Before the connection setup and MTU negotiation, the default value of 23 will be returned.

@TyChapin said in BLE MTU Exchange:

Then once I connect to a service, the MTU is 256 which is what the BLE device wants it to be at.

Yep, that (256) would be the real, negotiated, MTU.

@TyChapin said in BLE MTU Exchange:

When I go to read the characteristic value that has 64 bytes, only 24 bytes come over.
Does anyone have any advice on how to exchange the MTU size properly?

I suspect the problem is not MTU related. In most cases, the MTU should not affect the characteristic data size (just performance), because the BLE stack will use as many MTU's as needed to transfer the characteristic's data.

How are you checking the characteristic value's length? ie how do you know that the "value has 64 bytes", and "only 24 bytes come over"?

(Also, if its a publicly documented characteristic, and you're able to share the UUID, that might help, but no worries if not).

Cheers.

@SGaist said in How do I freeze the first row in a QTableWidget?:

use the answer arrows rather than the quick answer box.

Thanks, I discovered that after the first time I used it... :)