[Feature Request] [Equilab Omaha] gap in range and double suited high cards

Hi CallWithAir,
Welcome to PokerStrategy.com!
I fixed your links for you.
I can see you already found the dialogue I was going to suggest.
Here is what I came up with which appears to be a 4-card J-high double-suited rundown with 3 gaps.

When you click on the little blue "i" next to the # of combos you see:

I'm pretty sure you can tweak it from there to get what you need.

The second link was "access denied", but I think that you can do similar in the same dialogue.
Otherwise, just pick the range you want, then put /ds at the end in the main window.

My version appears different when compared to what you showed in the first link.
I'm using 1.1.4.0
What version are you using?

Note that I'm not a developer, just a user.

Hey,
Thank you

I'm using the same version - 1.1.4.0

I will try to explain myself better -
1 - I am looking to be able write rundown gap in a range of numbers.
If this is my range -
6+6+6+6+/r000, 6+6+6+6+/r001, 6+6+6+6+/r002
All three card rundowns, down to 6 - with gap between second and third card below 2
I am looking for a syntax shorter syntax to conclude all this 3 different ranges.. It will make the range construction easier in my opinion..
something like 6+6+6+6+/r00[0-2]

2 - I fixed the access problem to the second link.
I meant that I want to be able to add a restriction to double suited hands by the value of the higher card of each suit.
Since if I'm using ****/ds
I'll get so much trash - but if I want to conclude only double suited hands that each suit contains atleast broadway card this is a much better range..
Do you have a solution for creating such constraint easily using their syntax?

Thanks !

Originally posted by CallWithAir
Do you have a solution for creating such constraint easily using their syntax?

Easily?
No -- and in fact anything I tried looked really awkward.
I did try one thing though -- I ticked the "suited Ace" box, and that eliminated a lot of the garbage, but still not what you want.

I'll bring this thread to the attention of the office staff to see if anyone there knows if development is continuing on this tool.

Cheers,
VS