pointer searching with Breeze

[dsrules]

The spacing is now consistent. Some users found the previous variable-length lines to be visually jarring. You actually prefer the old format?

View attachment 467803
Some data will need more space, for example here column 2 looks like can be smaller but column 4 has one entry that needs the space.

I meant can you make the value columns closer to each other in u32 view, like in u8 view (more spacing between address and 1st column, less spacing between each value cloumn)
currently it looks ok in handheld mode, but on a big screen tv, my left eye feels like going left and right eye feels like going right, very uncomfortable feeling

 

[TomSwitch]

I meant can you make the value columns closer to each other in u32 view, like in u8 view (more spacing between address and 1st column, less spacing between each value cloumn)
currently it looks ok in handheld mode, but on a big screen tv, my left eye feels like going left and right eye feels like going right, very uncomfortable feeling
View attachment 467892
View attachment 467893

Some data will take up more space. The data is left adjusted and always start at the same place.
Do you prefer the old simple line format?


How about I put back the ( ) ?

You like the arrow back too?




Check out the version with ( ) see if that feels like old Mr. Memory explorer

 

[dsrules]

View attachment 467902
Some data will take up more space. The data is left adjusted and always start at the same place.
Do you prefer the old simple line format?

View attachment 467904
How about I put back the ( ) ?
View attachment 467906
You like the arrow back too?
View attachment 467907

View attachment 467910
View attachment 467921
Check out the version with ( ) see if that feels like old Mr. Memory explorer

Thanks, after play around with it some more today, it actually feels ok now (probably need some time to get used to the new view)
if the current 4 to 5 characters spacing between each column can be cut down to 2 characters, the same spacing between the address and the first column then that would be nice, if not then just leave it as the Pre-release version

Post automatically merged: Oct 30, 2024

@TomSwitch, my bad, I meant keep the Pre-release 95g view setting if the column spacing can't be narrow further
( ) without the arrow makes it harder to navigate on the small screen , ( to [ very slight change

actually, the old memory explorer is very good in all views, u8,16,32,64, spacing are perfect in hex mode, why the sudden change? spacing in the new one are all different in every view, doesn't look that good especially in u32 and u64

@NeoGranzon, do you like the new breeze beta 95g memory explorer?

 

[NeoGranzon]

@NeoGranzon, do you like the new breeze beta 95g memory explorer?

@dsrules ,i'm still on version 95a,is there an update directly from the app?

 

[dsrules]

@dsrules ,i'm still on version 95a, is there an update,is there an update directly from the app?

I don't know, but you could look at the pictures above your post

 

[TomSwitch]

@dsrules ,i'm still on version 95a, is there an update,is there an update directly from the app?

I released beta96 today

 

[dsrules]

I released beta96 today

is it the same build as 95h?
my test results from 95h
"( ) without the arrow makes it harder to navigate on the small screen , ( to [ very slight change"

guess I will stick with 95f for now, I mostly use u32 hex view, the old memory explorer is much more comfortable for me
if the old explorer is 9 points, I could only give the new one a 5 max (user preference)

 

[TomSwitch]

is it the same build as 95h?
my test results from 95h
"( ) without the arrow makes it harder to navigate on the small screen , ( to [ very slight change"

guess I will stick with 95f for now, I mostly use u32 hex view, the old memory explorer is much more comfortable for me

Yes, it is 95h. I decided to release it as 96. Started to get people asking for support on atm1.8 and they get the latest release version and never think to check the date of that version. I decide to make a release version so people have a release version that support atm1.8

Two reason I skip the arrow, 1. It offset the digits, since it is left aligned text the addition of a extra character moves the digits. This makes it harder to check if there are any match with the value on cursor. Of course you can move the cursor so that is kind of a minor point. 2. I ran out of space on u8 display and there is going to be some overlap with the next byte

You made a good point, hex mode is mostly already aligned.

 

[dsrules]

Yes, it is 95h. I decided to release it as 96. Started to get people asking for support on atm1.8 and they get the latest release version and never think to check the date of that version. I decide to make a release version so people have a release version that support atm1.8

Two reason I skip the arrow, 1. It offset the digits, since it is left aligned text the addition of a extra character moves the digits. This makes it harder to check if there are any match with the value on cursor. Of course you can move the cursor so that is kind of a minor point. 2. I ran out of space on u8 display and there is going to be some overlap with the next byte

You made a good point, hex mode is mostly already aligned.

the biggest problem for me is the large gap, in the old one, when I open memory explorer, I could instantly distinguish which address is a pointer address because both u32 values are close to each other
on the new one, I always need to hesitate, look left and right between 2 columns before confirming
in u64 view, the whole middle screen (vertical) is like empty

 

[NeoGranzon]

I don't know, but you could look at the pictures above your post

@dsrules ,don't worry i checked in the app and updated.

 

[dsrules]

@dsrules ,don't worry i checked in the app and updated.

how is it? do you like the new memory explorer in u32 and u64 view?

 

[NeoGranzon]

how is it? do you like the new memory explorer in u32 and u64 view?

@dsrules i haven't tried it yet,i ust updated the app.

 

[TomSwitch]

@dsrules here is pre-prerelease with the [ ] removed, nothing is better than something that is similar

 

[dsrules]

@dsrules here is pre-prerelease with the [ ] removed, nothing is better than something that is similar

[ ] to none feels weird, like something disappeared instead of appear

I meant, the new gap between values are too big for me (been using memory viewers or hex editor for many years with small gaps)

I can't adapt to the new changes


old memory explorer

new memory explorer

old
new

 

[TomSwitch]

@dsrules you need to have caption on each image for the message you want to convey about the image, non of these images are giving any message to me. I know the space is not consistent and it is a choice I made to have them aligned by column.

I agree changing [ ] to nothing isn't much of an improvement. I shall let beta96 look marinate a bit and visit it again if needed.

 

[dsrules]

@dsrules you need to have caption on each image for the message you want to convey about the image, non of these images are giving any message to me. I know the space is not consistent and it is a choice I made to have them aligned by column.

I agree changing [ ] to nothing isn't much of an improvement. I shall let beta96 look marinate a bit and visit it again if needed.

I just want the old spacing between values, been using the same spacing format since the nds days, and I have never seen such large distance between values on any game system since game hacking tools has been invented, the new format is not suited for me

 

[TomSwitch]

I just want the old spacing between values, been using the same spacing format since the nds days, and I have never seen such large distance between values on any game system since game hacking tools has been invented, the new format is not suited for me

Here is a special one for you. You can toggle it. The short cut is ZR+L3

 

[dsrules]

Here is a special one for you. You can toggle it. The short cut is ZR+L3
View attachment 468407

Thanks! now, it's best of both worlds

 

[TomSwitch]

@dsrules I calibrated the gaps. I think now the toggle can be removed.

 

[dsrules]

@dsrules I calibrated the gaps. I think now the toggle can be removed.

cool! now, it looks way more comfortable than before