Jump to content

Clément

Members
  • Content Count

    357
  • Joined

  • Last visited

  • Days Won

    4

Clément last won the day on December 31 2023

Clément had the most liked content!

Community Reputation

143 Excellent

Technical Information

  • Delphi-Version
    Delphi 12 Athens

Recent Profile Visitors

4006 profile views
  1. Clément

    Hunting a unit reference

    The unit I'm tracking does not appear in the graph. If I remove the path or rename the unit the project doesn't compile. I deleted all dcus from the library root to be sure only valid ".pas" files are compiled.
  2. Clément

    Hunting a unit reference

    I will instead create a new DPR project in the "root" , forcing a scan of all sub-folder, including the one I know this library is. My problem is tracking down which unit is dragging "this unwanted unit" in the project. Once I find the "unit responsible for dragging it in the project", I have to assess the best way to remove it from the project. Hopefully removing it from a "uses" clause will be enough, but I don't feel that lucky
  3. Clément

    Hunting a unit reference

    This is driving me nuts... I renamed the unit, the project stopped compiling as expected, but I can track that unit down. I can see it there, still unable to figure out which unit brings it in. I even removed the folder from the IDE environment. The project also stop compiling, but with this time with units it really needs. I am adding those one by one. As I thought it would be simpler to track it down ( stupid me ), I was working in the production .DPR, I had to undo everything, to be able to release a patch to a customer... 🤪 This project uses a very old in-house library (pre-2000) that migrated from Delphi 4 up to XE.
  4. Clément

    Hunting a unit reference

    Very nice tool! But it didn't display the unit I'm looking for. The unit is not directly linked in the project file, instead it is in a folder defined in the IDE environment. I would have to add folders to a list of folders to look for. Is it possible with the latest version you made available?
  5. Clément

    Hunting a unit reference

    I'm using a map file. the unit is there, but I cannot track how it ended up in this project. I wasn't able to install MMX under XE.
  6. Clément

    Hunting a unit reference

    I installed the free edition, ran it, but could'nt figure out how to check the units... I need to spend some more time to figure out if it can help
  7. Hi, I'm compiling a project (Delphi XE) with several millions lines and hundreds of units. Somehow a specific unit got called in that project, and I must discover which unit is dragging it in. It might be a direct reference or indirect reference (Since I'm a very lucky guy, it must be a deep indirect reference). In any case, I have to deal with it. Is there any tool that can help me track a specific unit linkage into a project? TIA, Clément
  8. Clément

    Toolbar + ToolButton + TitleBar flicking

    I'm a lot closer to what I want using VCL Styles. The form is a lot cleaner. I will have to implement a "Style ON / Style Off" for PITA customers. I took 2 screen shots to show you the difference between them. Without styles I would have to handle a lot more "design issues"
  9. Clément

    Toolbar + ToolButton + TitleBar flicking

    Hi.. I added those lines to the main form constructor: constructor TfrmMain.Create(AOwner: TComponent); begin inherited; fLogEngine := TdhsLogViewerEngine.Create; fLogEngine.OnRefreshLines := event_refreshlines; fLogEngine.OnEngineStatus := event_engineStatus; fShowLongField := false; Caption := Application.Title+' v'+strBuildInfoEx+' Beta '; fSearchTextCount := 0; fUpdate := TApplicationUpdate.Create; fEncodingList[1] := TEncoding.ANSI; fEncodingList[2] := TEncoding.UTF8; fEncodingList[3] := TEncoding.ASCII; fEncodingList[4] := TEncoding.Unicode; fEncodingList[5] := TEncoding.BigEndianUnicode; fCurrentEncodingIndex := 2; DoShowStatusBarSearchCount; DoConfigProgressBar; // Bug fixing attempts DoubleBufferedMode := dbmRequested; DoubleBuffered := true; ToolBar1.Transparent := false; Toolbar1.Flat := true; ToolBar1.DoubleBufferedMode := dbmRequested; Toolbar1.DoubleBuffered := true; end; I manually checked that every property is assigned properly. Still no joy
  10. Clément

    Toolbar + ToolButton + TitleBar flicking

    Thanks for your suggestion. Unfortunately toggling properties "Transparent", "Flat", "Ctl3D", "HideClippedBUttons" lead to the same behavior. Even tried "StyleELements := []; " with no luck. I set Toolbar.Stylename := 'Windows' to use both styles, but sill no joy. Under Windows 11 the only way is 100% native.
  11. Clément

    Toolbar + ToolButton + TitleBar flicking

    "In the realm of coding, a tempest shall brew a buggy IDE, causing much ado. Programmers´ patience tested, their sanity tried, as they navigate errors, with nowhere to hide." -- NostraGPTamus
  12. Clément

    Toolbar + ToolButton + TitleBar flicking

    Is there a way to file a Bug report so Embo can take a look at it? This bug is duplicated and might solve other problems with VCL Styles in windows 11.
  13. Clément

    Toolbar + ToolButton + TitleBar flicking

    yes. I'm windows 11
  14. Clément

    Toolbar + ToolButton + TitleBar flicking

    I'm using the VCL Style in this sample. As is, you click the open folder button (first one) to see the blink. If you change the VCL Style to "Windows" and recompile, the button will no longer blink, only the Titlebar. If you remove VCL Styles and titlebar, it behaves as expected. Blink_Sample.zip
  15. Clément

    Toolbar + ToolButton + TitleBar flicking

    I tested once more removing VCL Styles with the new code ( using postmessage) and the flick stopped completely. Going native!
×