another goofy "feature "
-
This post is deleted!
-
Yup, this happens from time to time. Usually it is enough to undo and try again and then it works fine.
-
@AnneRanch let me quote myself here:
@J-Hilk said in Yet another questions about "go to slot" - #1 need an example adding / using signal parameters:
@AnneRanch said in Yet another questions about "go to slot" - #1 need an example adding / using signal parameters:
I like to further improve my "connect" skill using "go to slot ".
let me stop you right here.
If you wan't to improve your "connect" skill than never ever use the connect by name feature -aka go to slot, when using Designer plugin.
These types of connections are very brittle, as a simple object rename would break your code -
@J-Hilk Yes, but...
my BIGGEST problem is trusting Qt examples...
in this case I am using "basic serial / terminal " and adding Bluetooth code to it.
So I successfully added another "action" to existing menu and needed to add "clear all windows"...
YES = my mistake = should have done it using code since I am now "an expert " in "connect" including
lambda ( but do not spread it around..,.) -
@AnneRanch said in another goofy "feature ":
@J-Hilk Yes, but...
my BIGGEST problem is trusting Qt examples...Don't, (nearly)everyone who had the "pleasure" of trying to use examples from other c++ libraries, agrees that the ones from Qt are exceptionally good! You can trust them 100%
in this case I am using "basic serial / terminal " and adding Bluetooth code to it.
in that case it stops being "basic" rather quickly, I'm sure you have noticed :)
YES = my mistake = should have done it using code since I am now "an expert " in "connect" including
lambdaWell, the quote is from 20 Jul 2021. Closing up on 3 years. "Expert" is debatable because everyone is unique, but more than enough time to get familiar with the core principle/mechanics of Qt, if you use it on a semi regular basis. I would say
( but do not spread it around..,.)
My lips are sealed!🤫
-
@AnneRanch said in another goofy "feature ":
For unbelievers - the function is in greyed area which is #ifdef - #endif block !
This doesn't mean the function isn't called anywhere, on the contrary it's exactly what this linker error is all about - you have a function declaration that has no definition, which function is called. You broke your promise to the linker (intentionally or not), so it rightfully complains.
-
@kshegunov 150% of my posts in lounge are posted as in-between friends light "beer talk" style ... It is readers option to take them seriously or not...
By same token - it is my option to further engage in "discussion" or move to another table.... -
@kshegunov Yes - it must be hard for linker to find the function in #ifdef BYPASS ...#endif block.
That is UNUSED code block...
Even if it was used code block - how did it get placed there ? -
If this is "just beer talk", then I truly wonder why I get summoned ...
@AnneRanch said in another goofy "feature ":
@kshegunov Yes - it must be hard for linker to find the function in #ifdef BYPASS ...#endif block.
That is UNUSED code block...Indeed it must be hard for the linker, since the linker has no notion of source code, nor of
#ifdefand alike preprocessor tokens. I think I've mentioned before, that it's truly beneficial to know C++ before claiming to use it, or a library for it.In any case, the linker sees the prototype of the function (which is its name, also called a symbol) and it has the singular task of linking all calls to that function to the place that symbol is defined (at low level). There's no source at this point, no preprocessor, no compiler or w/e. The linker is the same machinery for all languages on a platform.
Even if it was used code block - how did it get placed there ?
This question is for you to answer. I'm certainly not going to ask my crystal ball.
