Jump to content

Celso Henrique

Members
  • Content Count

    25
  • Joined

  • Last visited

Posts posted by Celso Henrique


  1. 2 hours ago, Fred Ahrens said:

    For me it's the lack of communication. Errors happen, but at a certain stage they should start to communicate about the error and give some advice about expected timeframe for fixing the problem, possible workarounds and so on. I really don't care (that much) how long this takes - but it would be nice to get some regular updates about the progress made.

     

    We are now in a situation where we have to review our development environment and make it as independent as possible from the availability of Embarcadero servers. In result we have to stop using GetIt, and other services may follow.

    Hello everyone,

     

    What disappoints me is that the individuals responsible for creating and maintaining these services are not juniors. They are experienced professionals who often give lectures on developing excellent software. I've mentioned this before: the Embarcadero team needs to take some time specifically to address these issues. It's tiresome to witness so many flaws coming from professionals who should set an example. As a friend pointed out, mistakes happen, that's normal, but not with such frequency.

     

    It's truly disheartening.

    • Like 2

  2. Hi people,

     

    I need a help to do something that in my mind is very easy: edit a dataset results.

     

    I work with a layers pattern where I have in my form just a ClientDataSet. I have a class function that return a OleVariant object. And I have a FDQuery in a DataModule with my SQL Query.

     

    To make my work easy, I have a fuction that creates a DataSetProvider just to take de resultset from FDQuery.

     

    Example:

     

    In Form:

    cdsList.Close;
    cdsList.Data := TMyClass.getList;

     

    In Class:

    dmMyDM.qryGetList.Close;
    dmMyDM.qryGetList.Open;
    
    Result := getData(dmMyDM.qryGetList); 

     

    In getData method:

    LDataSetProvider         := TDataSetProvider.Create(nil);
    LDataSetProvider.DataSet := AQuery;
    
    Result := LDataSetProvider.Data;
    
    FreeAndNil(LDataSetProvider);

     

    Problem:

    Manytimes I can't change the data on ClientDataSet because the field come from FDQuery with property ReadOnly set. I tried a lot of settings to change this and nothing worked.

     

    I don't want to send back this data to use update, insert or delete database rules. I just want to edit the data and send it forward.

     

    Is there a way to disable all this feature and keep the resultset completely editable?

     

    Thanks in advance! 


  3. Hi David,

     

    Sorry for the late. Too many things to do.

    On 12/19/2021 at 10:10 PM, corneliusdavid said:

    I don't see any of the Object Inspector or Structure Pane problems you mention

    1736098723_ERROIDE.thumb.png.d1520cc35ffe2b3580944524a42d72dd.png

     

    Another one. The search also stop to work.

     

    60576947_ERROIDE2-2.png.9a1c5084bd8602512d6710c4069772f3.png

     

    High processor consuming with no specific task. I was coding then the IDE stop to respond.

     

    255302688_ERROIDE3.thumb.png.866d50c5cdda989681936647eff7e6fe.png

     

    Now, the newest and the best one. The compiler is not accepting the value 452 for a smallint property.

     

    1265378119_ERROIDE4.thumb.png.805ecace0e123876805dcee7a78259ff.png

     

     


  4. Hi David,

     

    First of all, thanks for your reply and help.

     

    Follow:

    • Windows OS Version: Windows 10 Home Single Language, 21H2, 64bits
    • Processor: Intel Core i7-7500U 2.9GHz
    • Memory: 6GB
    • Hard disk space free: 12,5GB
    • Monitor resolution: Full HD (1920x1080)
    • Project size: attached 
    • Platform: VMWare

    The project is VCL.

     

    The behavior is: it starts working fine, but after a while these issues appear. Sometimes it backs to work again, but only after a long time. Looks like there is something running very slow.

     

    Code completion: A long time ago (I think Delphi 2007 or 2009) it was not necessary hit Ctrl+Space to call the code completion. You just typed and it came.

    Parentheses: If you use the code completion to call a method with parameters, the completion will put the parentheses even they are already there. See attached.

     

    I'm using almost standard settings of Code Completion (attached). Unhappily we don't have "Classic" option any more, only LSP.

    project size.png

    parenthesis.png

    code infight options.png


  5. What do you have in your minds to change something that was working extremely fine? Why are you destroying the productivity given by IDE?

     

    In the new version (11), the panels Structure and Object Inspector stopped to work properly.

     

    • I click on component in Form Designer and the respective component is nos selected on Structure panel;
    • I click on component in Form Designer and on Object Inspector the component's properties are showed up, but caption with the component's name does not change;
    • If I select a component on Structure, sometimes, nothing happens! It gets frozen on the last component selected;
    • If I click on component's name in Object Inspector and try to use the mouse wheel, it rolls up the names, but selects the next component from the last selected, thus the list rolls back;
    • If I try to compile after click on Save All, I have to pray to not frozen the entire IDE. In this cases I have to kill the application by Task Manager;
    • Before, I just had to type to call the code completion, but now it's mandatory to use the Ctrl+Space to call it;
    • Until the last version (Sydney), the editor knew when to add or not the parentheses, now, with the parameter "auto parenthesis" checked, it puts parenthesis even they already existing;

     

    I work with Delhi since version 5, it's being 21 years seeing you creating greats things to destroy them shortly thereafter. I have no more energy to see this @#$@$ and stay calm and quiet!


  6. On 1/4/2021 at 6:15 AM, mvanrijnen said:

    Reasonable pricing 🙂 And reasonable discounts for longtime customers (subscriptors)

     

    We also created some tickets about the new LSP, and i really really wonder how the tested the new LSP,  so many bugs in it what makes it unusable, and then if you switch back to thel old code insight, all the bugs are still there.

    it's a shame. 

    It looks like to me that they didn't any test. We are the Embarcadero testers, for free.


  7. Thanks Remy and sorry to bother you.

     

    At first moment, when we were working with the Tokyo version, we had port exhaustion. Because that, we increased the number of user ports and reduced the time wait on Windows. One problem was solved, but a new problem appeared. Working with the Sydney version we stopped to have port exhaustion, but continue have connection problems. I am giving up to work with App Tethering. I will probably create my own communication structure using just TCPServer and TCPClient components. I think that will be less stressfull

     

    Thanks again.


  8. 2 hours ago, Darian Miller said:

     

    CodeInsight was radically changed with the implemention of a Language Server Protocol host as the default Code Insight provider.

    You can change this in:  Tools->Options->User Interface->Editor->Source->Code Insight

    You are able to switch back to "Delphi (Classic Code Insight)"  

     

    I assume you are on an early version of 10.4 Sydney.  The latest version 10.4 Sydney Update 1 and Patch #1 provide major improvements to Code Insight.  You can see a list of recent updates here: https://github.com/ideasawakened/DelphiKB/wiki/Delphi-Master-Release-List

     

    I suggest you update to 10.4.1 and then apply latest patches as Code Insight is much better.

     

     

     

    I am using version 10.4.1 and I am using the "Classic Code Insight".

     

    I tried a lot of different settings before post the message. 

     

     

    code.PNG


  9. Hello people,

     

    I figured out that the problem is not the time, but incomplete connections. My application has a timer that runs indefinitely until get the connection with the Server. Some machines start the connection negotiation but it never ends because of local firewall rules. When this happens, the Manager stops to respond other connections (new or old) just trying to make this connection.

     

    Look the Wiresharck log attached. The IP 10.106.1.8 is the Server and the IP 10.106.22.95 is the Client.

     

    I would like to know how I can avoid this. Is there a way to identify these machines without use Wireshark? Is there a way to make Manager not stop to respond other machines?

     

    Thanks!

     

    BR.

     

    Capturar.PNG


  10. Hello people,

     

    I developed an application to work in a critical environment. My application has 4 modules:

     

    1. Server
    2. Manager
    3. Terminal
    4. Handheld

     

    All modules connect to the Server module by Tethering. All modules have only 1 Manager and 1 Profile. The modules Manager and Terminal are executed on remote machines, while the Handheld module is executed inside the same machine where the Server module is executed.

     

    The problem I am having is that the Server module starts executing very well and for a while it communicates with the other modules without any problem, but after some time, it starts to refuse connections. Looking through WireShark, I found the message: Destination Unreachable (port unreachable).

     

    To work around this problem, I changed the Windows registry to increase the number of available ports (65535) and to decrease the wait time (30s). Even so, I continued to have problems. My last attempt was to increase the range of ports used by the component. I'm working with 2020-2119 for ManagerPort and 2120-2250 for AvPort. This also did not resolve.

     

    Whenever the Server starts to refuse connection, I am obliged to restart the machine.

     

    I really need your help.

×