- Katılım
- 17 Eki 2016
- Konular
- 129
- Mesajlar
- 2,409
- Çözüm
- 86
- Online süresi
- 2mo 11d
- Reaksiyon Skoru
- 1,290
- Altın Konu
- 1
- Başarım Puanı
- 258
- MmoLira
- 1,851
- DevLira
- 12
ROHAN2 WORLD 1-120 TR TİPİ OFFICIAL YOHARA, BALATHOR VE AMON! 80. GÜNÜNDE! +10.000 ONLİNE! HİLE VE BOT %100 ENGELLİ HEMEN TIKLA!
Whats the difference between searching the define macro in the whole project vs this?Hello everyone,
I want to introduce my small but very practical tool that helps you work with C++ source files and Python client files. It is designed to identify define blocks in source files and optionally scan Python client files for defines.
![]()
Core Features
- Define Scanner (C++ Source)
- Scans all .cpp and .h files in a selected folder.
- Finds complete #ifdef blocks for the provided defines.
- Option to copy or delete the blocks.
- Output is stored in structured folders under DefineScan_System with all files and block info.
- Client Scanner (Python)
- Optional scan of .py files in the client folder.
- Searches for if app. defines.
- Detects complete Python if-blocks, including nested blocks, elif and else.
- Output is stored in structured folders under DefineScan_Client.
- Flexible Define Input
- Multiple defines can be separated by comma, semicolon, or space.
How to use the tool
- Select Folder
- Choose the folder for system scan (.cpp / .h files).
- Optional: Enable “Scan Client” and select the client folder (.py files).
- Enter Defines
- Example: ENABLE_TEST, ENABLE_RENDER.
- Separate multiple defines with, , ; or space.
- Choose Action
- #ifdef copy -> blocks are saved in new folders.
- #ifdef delete -> blocks are removed from files (backup is created).
- Start Scan
- Click “Start Scan”.
- Progress bar shows current progress.
- Hits are counted and files are saved in output folders.
Actually in German and Englisch version , Turkish will be added today.
NEU!!! Tutorial-Bereich hinzugefügt!
Linkleri görebilmek için Turkmmo Forumuna ÜYE olmanız gerekmektedir.
- Katılım
- 3 Mar 2021
- Konular
- 2
- Mesajlar
- 17
- Online süresi
- 1d 9h
- Reaksiyon Skoru
- 18
- Altın Konu
- 0
- TM Yaşı
- 5 Yıl 3 Ay 3 Gün
- Başarım Puanı
- 42
- MmoLira
- 723
- DevLira
- 3
The difference is mainly the workflow and convenience.Whats the difference between searching the define macro in the whole project vs this?
When you search for macros directly in Visual Studio, you have to:
- Manually search through all files
- Make sure VS isn’t only searching the current project
- Deal with slow search speeds, especially in large sources
My Define Scanner does it automatically and smarter:
- It scans all files, even the ones Visual Studio doesn’t have loaded in the project
- It filters only real defines instead of every occurrence of “#define”, including comments
- It shows the results neatly sorted by file, name, or value
- It saves time because you don’t need to configure anything or search manually
- It also finds macros in libraries, server/client mixes, and folders outside the solution
- You can further process the results (export, analysis, integrator, etc.)
In short:
VS can search, but my scanner can analyze and handle the Whole System with 1 Click e.g Copy , delete or Integrate
- Katılım
- 26 Mar 2024
- Konular
- 1,281
- Mesajlar
- 4,829
- Çözüm
- 91
- Online süresi
- 3mo 26d
- Reaksiyon Skoru
- 4,056
- Altın Konu
- 566
- Başarım Puanı
- 274
- Yaş
- 29
- MmoLira
- 136,792
- DevLira
- 450
Paylaşım için teşekkürler.
Şu an konuyu görüntüleyenler (Toplam : 0, Üye: 0, Misafir: 0)
Benzer konular
- Cevaplar
- 9
- Görüntüleme
- 489
- Cevaplar
- 49
- Görüntüleme
- 1K
- Cevaplar
- 7
- Görüntüleme
- 3K
- Cevaplar
- 9
- Görüntüleme
- 743
- Cevaplar
- 1
- Görüntüleme
- 114















