The layout is inconsistent

I have a question where does the interface code of the dicom module be in the project and why can’t I find it?Also why is the layout of the retrieval form in the compiled 4.13 version dicom module be different from that in the release and how should I debug the code.See the picture.
001
002

Slicer uses commontk for much of the dicom infrastructure: Commontk

Thanks for the answer.Although I know if dicom is a module from ctk it cannot explain why the interface layout of my compiled version is not consistent with the official release version

The DICOM interface can not be found directly in the Slicer source, but in the Commontk sources. You probably need to create a fresh Slicer fork and build that to receive the latest DICOM interface, which indeed improved in important detail: being able to receive selected series from studies.

If that does not answer your question please describe what you want to achieve.

I mean, why is the interface of the software I compiled inconsistent with the interface of the officially released version? Is it because of the version problem or where I have a problem

Slicer Preview Releases are built from the latest version on the master branch every night. If you build the same version then you will get exactly the same user interface.


It’s not my problem, it’s the version

Can you copy/paste here the application log (menu: Help → Report a bug)?

[DEBUG][Qt] 21.11.2021 00:05:12 [] (unknown:0) - Session start time …: 2021-11-21 00:05:12
[DEBUG][Qt] 21.11.2021 00:05:12 [] (unknown:0) - Slicer version …: 4.13.0-2021-11-19 (revision 30421 / 9f03a47) win-amd64 - installed release
[DEBUG][Qt] 21.11.2021 00:05:12 [] (unknown:0) - Operating system …: Windows / Professional / (Build 17763, Code Page 936) - 64-bit
[DEBUG][Qt] 21.11.2021 00:05:12 [] (unknown:0) - Memory …: 24410 MB physical, 33626 MB virtual
[DEBUG][Qt] 21.11.2021 00:05:12 [] (unknown:0) - CPU …: GenuineIntel , 12 cores, 12 logical processors
[DEBUG][Qt] 21.11.2021 00:05:12 [] (unknown:0) - VTK configuration …: OpenGL2 rendering, TBB threading
[DEBUG][Qt] 21.11.2021 00:05:12 [] (unknown:0) - Qt configuration …: version 5.15.2, with SSL, requested OpenGL 3.2 (compatibility profile)
[DEBUG][Qt] 21.11.2021 00:05:12 [] (unknown:0) - Developer mode enabled …: no
[DEBUG][Qt] 21.11.2021 00:05:12 [] (unknown:0) - Application path …: C:/ProgramData/NA-MIC/Slicer 4.13.0-2021-11-19/bin
[DEBUG][Qt] 21.11.2021 00:05:12 [] (unknown:0) - Additional module paths …: (none)
[DEBUG][Python] 21.11.2021 00:05:13 [Python] (C:\ProgramData\NA-MIC\Slicer 4.13.0-2021-11-19\lib\Slicer-4.13\qt-scripted-modules\SubjectHierarchyPlugins\AbstractScriptedSubjectHierarchyPlugin.py:36) - Scripted subject hierarchy plugin registered: Annotations
[DEBUG][Python] 21.11.2021 00:05:14 [Python] (C:\ProgramData\NA-MIC\Slicer 4.13.0-2021-11-19\lib\Slicer-4.13\qt-scripted-modules\SubjectHierarchyPlugins\AbstractScriptedSubjectHierarchyPlugin.py:36) - Scripted subject hierarchy plugin registered: SegmentEditor
[DEBUG][Python] 21.11.2021 00:05:14 [Python] (C:\ProgramData\NA-MIC\Slicer 4.13.0-2021-11-19\lib\Slicer-4.13\qt-scripted-modules\SubjectHierarchyPlugins\AbstractScriptedSubjectHierarchyPlugin.py:36) - Scripted subject hierarchy plugin registered: SegmentStatistics
[DEBUG][Qt] 21.11.2021 00:05:14 [] (unknown:0) - Switch to module: “Welcome”
[DEBUG][Qt] 21.11.2021 00:05:27 [] (unknown:0) - Switch to module: “DICOM”
[CRITICAL][Stream] 21.11.2021 00:05:27 [] (unknown:0) - Database folder does not contain ctkDICOM.sql file: C:/Users/Administrator/Documents/SlicerDICOMDatabase

This indicates you need to pick a different database directory (this one may not be writable).

The problem with this database directory will not affect the layout of the UI interface

I would like to ask, where can I modify this interface? I want to translate the interface into Chinese

CTK contains DICOM components. What is the relationship between this and DCMTK

The layout difference are because the current code reflects a fairly recent redesign that happened since the latest release was made.

You can read about this at the commontk.org site.

Did you see the response when you asked before?

Commit 9f03a47ed9a6c8cae1b242bf45259b6925f2a75b is a very recent master version. That version uses this CTK hash, which renders the Query/Retrieve dialog like this:

image

If your Query/Retrieve dialog looks like the old version that you showed above it means that your CTK version is older. You either have not rebuilt CTK since you updated it or you specified an older CTK version manually.

Appearance of the DICOM database tables (displayed columns, order of columns, column width, format, sorting, etc.) are stored in the database itself, so the database content actually affects the layout of the UI interface - but only inside the Patient/Study/Series table. The difference you see is due to using an older CTK version.