The SquadronUI.cs so far is just a draft for your review. I published this to learn from you whether the API structure as shown would be helpful and sufficient for what you are planning.
With rat targeted all we need to do is to click artillery button in EVE - the question is how we can click that button ?
Ok, with the sample I have so far I can read all buttons for all squadrons. But I do not have a solution yet for the classification as “artillery”. I would try hovering the mouse over each of the buttons and storing the tooltip for each of them, making the connection between tooltip and button with the highlight that appears on the button when it is hovered. Then we could look for the string ‘artillery’ in the saved tooltip. When I have a eve online client process sample with the button tooltip while the button itself is highlighted, I can look into reading this too.
public interface SquadronUI
{
int? SquadronNumber { get; }
SquadronHealth Health { get; }
IEnumerable<SquadronAbility> SetAbility { get; }
}
It depends on your feedback. For clicking the button you marked in your screenshot, the SetAbility property would be used to obtain references to the three buttons. The element from the collection could then used to click on. That is the plan so far.
I adopted the name ‘Ability’ from the eve online memory to refer to the button, but I do not know if the eve online UI uses other symbols for this entity.
I see you uploaded two samples. Does the last one contain everything we need? I do not want to store multiple samples for stuff that can be covered in one.
Unless there is a good reason to do otherwise, I’d prefer to use one sample as reference for both selection and hint to keep the storage requirements low.
Hello Terpla,
I did not forget about your request. At the moment, I have no time to search through process samples for the additional properties you described.
Maybe we could speed up the development process by having multiple people take on the part of searching for memory reading paths. What do you think?
I will upload a tool which extracts from the UI from a eve client process sample and exporrts the info in an easy to read format. This will follow the algorithm I explained at Advanced Do It Yourself Memory Reading In EVE Online
It will be a tool to persist what you can aleady read with the mentioned algorithm today.