Jump to content

Didier Cabalé

Members
 View Profile  See their activity

  • Content Count

    19

  • Joined

  • Last visited

Posts posted by Didier Cabalé

  1. Posted

    15 hours ago, Uwe Raabe said:

    Adding a layer of action to achieve a goal is probably not well accepted by long time MMX users as it would break their work flow.

    I totally agree.

     

    15 hours ago, Uwe Raabe said:

    Even if such functionality would exist, which class should the method be added when DoIt is not declared in TMyObject, but in TMyBaseObject, which TMyObject is derived from?

    The same question does exist when you propose to add a method to TForm1. And in that case, you simply add it to TForm1, not to TForm, the TForm1 ancestor.
     

    15 hours ago, Uwe Raabe said:

    Instead of asking for the target object each time, it is much simpler to Ctrl-Click on the TMyObject reference or even the DoIt reference in the code, which immediately selects the requested object on which the Add Method action then can be executed on.

    1. Ctrl-Click on the TMyObject, that selects TMyObject, makes you loose the fluidity of the change (helped with bookmark #7 and bookmark #9 when method added to TForm1)
    2. Ctrl-Click on DoIt does not do anything, because it is not created yet.

  4. Posted · Edited by Didier Cabalé

    Here are the basic steps that show the problem

    1. create a VCL project

    2. on the TForm's TButton OnClick event, type the following: 

    procedure TForm1.Button1Click(Sender: TObject);
var
  lMyObject: TMyObject;
begin
  lMyObject := TMyObject.Create;
  lMyObject.DoIt;
end;

    3. select the 'DoIt', and type Ctrl+Alt+M to invoke  adding a method for (obviously) TMyObject

    4. state that the Add method form proposes a method adding for the TForm1, instead of for TMyObject2118096750_2021-04-0910_58_57-ClonedeW7Delphi1Running-OracleVMVirtualBox_1.thumb.png.4e2ebf7bd4599dbc3522d8dba3f34dd3.png

    I actually wanted to get some other's feedbacks, before sending this to MMX support

     

  7. Posted · Edited by Didier Cabalé

    [Delphi 10.4.2; MMX 15.0.30.2400]

    Hi there,

    I wondered what was the purpose of the "Enable Key Bindings" checkbox.

    1646678307_2021-02-2611_41_16-MMXCodeExplorerproperties.thumb.png.665b9431795cc8c85ebf8898920d2192.png

    If it is, as I understand, for disabling the registered "Key Bindings" defined in the list above, then it does not work for me.

    Eg: although disabled ("Enable Key Bindings" unchecked), I can open Uses search form by typing ctrl+U.

    This is quite annoying, because newer Delphi IDE plugins (like Parnassus Bookmarks) conflicts with MMX key shortcuts - or "key bindings" (eg: ctrl+shift+B), and it would be useful to temporary disable MMX key bindings, and watch how the other is behaving. Other solution would be to change the shortcut value, but must be considered as an unfair workaround.

    Thanks for your help.

  9. Posted

    Indeed, the thing does what he says.. -> it's not a bug.
    But please consider this point: entering in the "Member Search bar" edit box currently deselects the filtering done by the object top pane selection.

    1. this is not logical, unless you select first the Module in the top pane.

    2. it would be nice to be able to "member search" the members within a selected object.

    I hope you understand this point.

  10. Posted · Edited by Didier Cabalé
    add tag

    Hi there,

    please follow these steps:

    1. in MMX code explorer, select one of your object

    2. state that the members of this object are listed in the pane below. Ok.

    3. click on the "Member Search bar" edit control

    4. state that the search will be applied to all the current module, whereas I would have expect it applies only to the object selected in 1.

    Wouldn't you have expect the same as me?

    search.png

  12. Posted

    On 1/7/2021 at 5:24 PM, Didier Cabalé said:

    I probably should follow This link, but it's what I already did..

    I finally get it work, without any changes in the GetIt http ServiceURL (remains https://getit-104.embarcadero.com), following what is told in the above link, and probably also by doing what told at chapter "Enable TLS 1.1 and 1.2 on Windows 7 at the SChannel component level" from Update to enable TLS 1.1 and TLS 1.2 as default secure protocols in WinHTTP in Windows (microsoft.com).

    ..and here is the result

    1857980719_TheEmbarcaderoGetItservercouldnotbereached11.thumb.png.0e54dac2243cd9a22ecf23a86e2b4ec9.png

    When one want to stay with Windows7, one need to fight:classic_dry:

    • Thanks 1

  18. Posted

    [using Delphi 10.4 update1 + Windows7 on VirtualBox]

    Preamble: I know that Windows7 is not officially supported by Delphi 10.4. Though, the below problem was not existing in the same environment (Delphi +Windows7), some months ago.

     

    Steps to reproduce:

    1. open Delphi 10.4 update1

    2. from the IDE, open GetIt package Manager

    3. state that "the Embarcadero GetIt server could not be reached", "Error on loading data from the server getit-104.embarcadero.com"

    1933057976_TheEmbarcaderoGetItservercouldnotbereached0.thumb.png.6c77da78e1483c9e286c62943f928c44.png

     

    Note that:

    1. the Embarcadero GetIt server could currently be pinged.

    912382489_TheEmbarcaderoGetItservercouldnotbereached3.thumb.png.5ad83b4c9c8ed413216887745a9c2a11.png

    2. the Embarcadero GetIt server could be accessible previously (some months ago)

    1519310511_TheEmbarcaderoGetItservercouldnotbereached5.thumb.png.2f739b545ac3fb73e10b3d1654dbb14f.png

     

    My questions are:

    1. Has something been changed on the Embarcadero server side?

    2. Can someone state the same issue, in the same conditions?

     

    The Embarcadero GetIt server could not be reached#4.png

×