--0000000000006b24410576b7da71
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Hi,
I just peeked at the relevant MC4D code
to
see what is saved out, and unfortunately, there is not an easy way to map
what is in the macro file to stickers on the screen. There is a section in
parenthesis that starts with g (for "grip") that has the reference clicks,
e.g.
(g 4 5 7)
The integers that follow are the internal IDs of the grips (not exactly
one-to-one with stickers). Those IDs
ava#L1152>
are a number dependent on how the slicer carved up the particular puzzle
and not easily decipherable to a human.
If you tend to use the same reference stickers for your macros, you could
write out some test macro files with what you suspect you used and compare
indices. That's the best option I could think of here.
Roice
On Tue, Sep 25, 2018 at 10:00 AM act@energeticeinsteins.com [4D_Cubing] <
4D_Cubing@yahoogroups.com> wrote:
>
>
> Hey all, haven't done a solve in quite a little while and I don't remembe=
r
> the reference stickers for about half of my macros. Does anyone know if
> there is a way to look into the macro file to determine what my reference
> stickers are? Thanks
>
>
>=20
>
--0000000000006b24410576b7da71
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Hey all, haven't done a solve in quite a little while and I do=
n't remember the reference stickers for about half of my macros.=C2=A0 =
Does anyone know if there is a way to look into the macro file to determine=
what my reference stickers are? Thanks
Hey all, haven't done a solve in quite a little while and I do=
--0000000000008762db0576b996c2
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
I had the thought that it would be easy to have MC4D support highlighting
the original reference stickers, so I added a feature request for that.
https://github.com/cutelyaware/magiccube4d/issues/132
Roice
On Tue, Sep 25, 2018 at 3:21 PM Roice Nelson
> Hi,
>
> I just peeked at the relevant MC4D code
>
> see what is saved out, and unfortunately, there is not an easy way to map
> what is in the macro file to stickers on the screen. There is a section i=
n
> parenthesis that starts with g (for "grip") that has the reference clicks=
,
> e.g.
>
> (g 4 5 7)
>
> The integers that follow are the internal IDs of the grips (not exactly
> one-to-one with stickers). Those IDs
>
.java#L1152>
> are a number dependent on how the slicer carved up the particular puzzle
> and not easily decipherable to a human.
>
> If you tend to use the same reference stickers for your macros, you could
> write out some test macro files with what you suspect you used and compar=
e
> indices. That's the best option I could think of here.
>
> Roice
>
>
> On Tue, Sep 25, 2018 at 10:00 AM act@energeticeinsteins.com [4D_Cubing] <
> 4D_Cubing@yahoogroups.com> wrote:
>
>>
>>
>> Hey all, haven't done a solve in quite a little while and I don't
>> remember the reference stickers for about half of my macros. Does anyon=
e
>> know if there is a way to look into the macro file to determine what my
>> reference stickers are? Thanks
>>
>>
>>=20
>>
>
--0000000000008762db0576b996c2
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
o have MC4D support highlighting the original reference stickers, so I adde=
d a feature request for that.
1 PM Roice Nelson <roice3@gmail.com<=
/a>> wrote: 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
2d96395/src/com/superliminal/magiccube4d/Macro.java#L165" target=3D"_blank"=
>relevant MC4D code=C2=A0to see what is saved out, and unfortunately, t=
here is not an easy way to map what is in the macro file to stickers on the=
screen. There is a section in parenthesis that starts with g (for "gr=
ip") that has the reference clicks, e.g.
(g 4 5 7)
t=C2=A0exactly one-to-one with stickers). elyaware/magiccube4d/blob/188d2e45ef62bacdd2f0c991b2d2a329a2d96395/src/com/=
superliminal/magiccube4d/PolytopePuzzleDescription.java#L1152" target=3D"_b=
lank">Those IDs are a number dependent on how the slicer carved up the =
particular puzzle and not easily decipherable to a human.
iv>
, you could write out some test macro files with what you suspect you used =
and compare indices. That's the best option I could think of here.
eins.com [4D_Cubing] <arget=3D"_blank">4D_Cubing@yahoogroups.com> wrote:
olid;padding-left:1ex">
=20=20=20=20=20=20=20=20
n't remember the reference stickers for about half of my macros.=C2=A0 =
Does anyone know if there is a way to look into the macro file to determine=
what my reference stickers are? Thanks
--0000000000008762db0576b996c2--