Conversation
|
Great PR! Please pay attention to the following items before merging: Files matching
This is an automatically generated QA checklist based on modified files. |
10110111
left a comment
There was a problem hiding this comment.
So this doesn't seem to "fix" anything, just tweaks logging and the docs. Am I missing something?
|
|
||
| initResult = OleInit(COINIT_APARTMENTTHREADED); | ||
| hResult = OleCreateInstance(L"ASCOM.Utilities.Util", &utilDispatch); | ||
| hResult = OleCreateInstance(L"ASCOM.Utilities.Util", &utilDispatch); |
There was a problem hiding this comment.
Why this change to spaces?
There was a problem hiding this comment.
I have loaded the .clang-format file now. When I select a region and right-click "Auto-Indent Selection", there are tabs at the head of lines. As soon as I store the file, there are space characters. Same nonsense on every new system, and doing this only once per year I have forgotten the switches. :-( Will find out.
BTW, is .clang-format or still the older xml file the right? Why are there both? Could we delete one?
There was a problem hiding this comment.
BTW, is .clang-format or still the older xml file the right? Why are there both? Could we delete one?
In Ubuntu 22.04 the qtcreator package is still v6.0.2, which needs an XML file. Modern QtCreator (that I built from sources) wants a clang-format file. So we need both. (And ideally, also update the Coding Style docs to include the clang-format file, in addition to the XML.)
There was a problem hiding this comment.
OK, then we need both, yes, and I hope they are equal in rules. (My 2012 laptop must stay on U22.04LTS until 2032 or until nouveau supports a Geforce 580...)
Just the auto-conversion from tab to space on store is annoying, I must find the relevant switch.
If you have access to the actual hardware, could it be better to switch to Alpaca and drop the COM-based ASCOM? This would bring support for these devices to Linux (and possibly macOS). |
|
Please ignore this PR for now. It is a draft, mostly used for exchanging between two systems. Yes, spacing is off, I had not installed the style file on the new system. Yes, Alpaca would be nice, but see other PR, need deeper insight into Stellarium's underdocumented TelescopeControl plugin. In just these days it may even be an issue between MS and ASCOM with some problems in .NET3.5. |
The ARM64 is the first system where I need scaling !=1. On startup the main window is shrinking. This fix prevents the shrinking. If it breaks elsewhere, enclose in WIN32.
|
Of course, if anyone has time/knowledge to go into Alpaca (which works on all platforms), the relevant branch #4148 is rebased and open for continuation. |
|
With some help from the ASCOM developers we found that we need a sidecar file Where should this go in the repo (inside ASCOM sources?), and how do I ensure it is being copied to the install folder? In addition, apparently this use of ASCOM based on .NET requires a signed program to run without interference of 'Smart App Control'. I am in the process of upgrading qDebug() etc into qCDebug(Telescopes) and decide what's debug and what's a warning, but this should go into all parts of the plugin, will take a few days longer. We can then finetune also this plugin, with qCWarning as default. |
|
@gzotti it’s an easy - please see similar files in |
|
Now I am back at the coding style issue. Using the .clang-format, indentation works with tabs. When I store the file, tabs are replaced by 8 spaces. Where is the switch to fix that nonsense? EDIT: Bah, found it. Preferences/Text Editor/Cleanups Upon Saving. Disable "Clean indentation". |
- logging categories - separate debug from warnings - More diagnostics.
Hmm… Should be xmi file updated too? |
|
@gzotti I fear patch for |
What do you mean? The XML is short and to the point. "Cleaning" is a separate config option (rather stupid in that it doesn't follow the coding style configuration). |
|
How can we refer to the |
I know. The file is where we said, but the copying to destination is not there yet. |
Do we need to actually show its contents? Else, a link to Github should suffice. But a notice esp. also in the BUILDING instructions for newcomers that in addition to this file being used by QtCreator, developers must also disable the switch mentioned above. This is more a QtCreator issue, but we have to live with it. When the last LTS version that depends on the old XML style file is EOL, we can at least remove that one. |
|
Thanks. But IMHO it should be behind "if ENABLE_PLUGIN TelescopeControl and ASCOM" (or something similar that works :-). |
|
I think the AppVeyor for Windows (all flavours) could be upgraded to Qt6.10 if possible. On Windows the libraries are packed with the program, so we can take the latest. |
Yes, we can do it, but I'm not sure that we need overengineering here... |
I mean should we update |
You can try it P.S. You want to drop support 32-bit (Qt5) packages? |
No, it's completely correct. I've updated the relevant docs (see 1035111). |
I thought we had dropped 32bit Windows with the new star catalog? At least there is no download for it, right? Actually, the ARM-related changes should not affect Qt5 builds. (Maybe the config file is useful also here.) I meant, all Appveyors now running Qt6.8 (or lower?) could be updated to 6.10 if possible. I'll try... |
No, we still publish win32 packages. The current branch can’t be compiled with Qt5 (type conversion issues). P.S. Maybe it’s time to drop support win32 packages (W7+), but we should resolve issues for compilation with Qt5. P.P.S. Qt 6.8+ requires Windows 10+. |
Description
This shall include fixes identified during testing work on Arm64 hardware donated by Microsoft.
Apart from the tests listed in #4772, getting ASCOM to play nice seems the largest issue. :-(
Fixes #4772 (issue)
Screenshots (if appropriate):
Type of change
How Has This Been Tested?
Test Configuration:
Checklist: