[DataChanger] LF2 IDE v3.4.0

[Gad]

Ok. Seems pretty fantastic! Thank you very much. Now it's much easier
Right now I miss something that would allow me to jump from one frame to next using some shortcut or linked button.
Would be nice to get a shortkey for going to frame indicated in "next" and in the frame that is next just in line order.

Also, Yin's dcer has more intuitive rectangle editor. It would be perfect to be able to drag and edit existing rectangle without overdrawing it every time.

I've found one strange thing.
Your preview is somehow based on the values described in the brackets at the spritesheet declaring.

Code:

file(0-159): space_f\chopper.bmp  w: 104 h: 85  row: 10  col: 16
file(160-155): space_f\effects.bmp  w: 79  h: 79  row: 6  col: 1

If I write things in the brackets incorrectly (which i often do, since i don't need these for anything) then the app is calculating the sprites being used basing on the wrong values, not as the lf does. IMO these should be more invormative then being used, and real sprite should be calculated being determined by row,col values multiplied.

[A-Man]

Right now I miss something that would allow me to jump from one frame to next using some shortcut or linked button.

Ctrl+F -> type "> X", X being the frame number

[Gad]

This is not the short way.

[NightmareX1337]

LF2 IDE v3.1.1

Update Log (Click to View)

v3.1.1
Corrected sprite parser algorithm
Added more shortcuts
- Ctrl+B, Ctrl+Shift+B goes to next/previous frame
- Ctrl+Tab, Ctrl+Shift+Tab changes active document

Ok. Seems pretty fantastic! Thank you very much. Now it's much easier

You're welcome

Right now I miss something that would allow me to jump from one frame to next using some shortcut or linked button.
Would be nice to get a shortkey for going to frame indicated in "next" and in the frame that is next just in line order.

Implemented.

Also, Yin's dcer has more intuitive rectangle editor. It would be perfect to be able to drag and edit existing rectangle without overdrawing it every time.

You can move the rectangle by just clicking (without moving mouse). Making a rect-editor like YinYin's is quite a bit of work. You can try changing those text boxes for making pixel perfection.

I've found one strange thing.
Your preview is somehow based on the values described in the brackets at the spritesheet declaring.

Code:

file(0-159): space_f\chopper.bmp  w: 104 h: 85  row: 10  col: 16
file(160-155): space_f\effects.bmp  w: 79  h: 79  row: 6  col: 1

If I write things in the brackets incorrectly (which i often do, since i don't need these for anything) then the app is calculating the sprites being used basing on the wrong values, not as the lf does. IMO these should be more invormative then being used, and real sprite should be calculated being determined by row,col values multiplied.

Fixed.

You're lucky to have me on my holiday

[Gad]

I really appreciate all your work there!
There are few things to fix.
For instance (atm) I could tell you that cpoint cover is not fully fixed.

Details
Assume the tag written as "cover: XY" with X and Y being the values being displayed below:
X
[1] aligns the caught character to face the same direction.
[2] aligns the caught character to face the opposite direction.
Anything else does does not change the caught characters facing.
Y
[0] displays the caught character behind the catcher (z position -1).
[1-9] displays the caught character in front of the catcher (z position +1).

source: http://lf-empire.de/lf2-empire/data-chan...limitstart=

[NightmareX1337]

LF2 IDE v3.2.0

Update Log (Click to View)

v3.2.0
Improved and redesigned 'Solution Explorer'
Added an option to choose whether opoint viewer will be auto-loaded on startup
Fixed cpoint cover rendering

As I finally found some time... Enjoy!

[Xain A. Latif]

From Where can I get it? I already have YinYin's Visual Data Changer. But its not that cool. I hope your's will be.

[NightmareX1337]

From Where can I get it? I already have YinYin's Visual Data Changer. But its not that cool. I hope your's will be.

Just look at the first page of the thread.

[NightmareX1337]

LF2 IDE v3.3.0

Update Log (Click to View)

v3.3.0
Implemented document navigation
Fixed 'Jump To' problems when line wrapping is on
Focus follows mouse between Design panel and documents
Change behavior: F9 doesn't bring LF2 foreground anymore
Fixed file creating & renaming issues in Solution Explorer
Fix 'Jump To' not expanding folds
Added shortcut Ctrl+R for "jump to frame" of selected text as index
Added shortcut Ctrl+U for backward navigation
Added shortcut Ctrl+Shift+U for forward navigation
Better encoding support
Made text editor settings globally handled (rather than per document)
- Line wrapping
- Show white space & end of line characters
Fix image file loading: open detached
Fixed wrong shown area of startup-loaded files when line wrapping is on
Fixed 'Jump To' problems when line wrapping is on

And now, LF2 IDE is more useful than ever!

About Ctrl+R shortcut and Document Navigation
These are probably among the most time saver features of LF2 IDE. Frequently, data changers need to jump between frame indexes. Although LF2 IDE supports 'jump to frame index', this method of manually writing frame index is unnecessarily slow. Instead, Ctrl+R will immediately do it for you. How? Double click on an index so it gets selected. Then press Ctrl+R. For example: You want to jump to the DJA special move of some character. Seeing `hit_ja: 230` you understand it's starting at frame 230. Double click 230, press Ctrl+R and you just jumped to frame 230.
Now that's sweet. But what if you want to get back where you left? Simple! Either click "Navigate Backwards" button or use Ctrl+U shortcut. Document Navigation is there to serve you.

As usual, download links are on the first page. Feed back is highly appreciated!

[Som1Lse]

Double click on an index so it gets selected. Then press Ctrl+R. For example: You want to jump to the DJA special move of some character. Seeing `hit_ja: 230` you understand it's starting at frame 230. Double click 230, press Ctrl+R and you just jumped to frame 230.

Why doesn't it just figure out that the cursor is above a number automatically? Heck if it is over the hit_XY: part it could probably figure out I want the next number. Data changing is pretty well documented so it should be easy to figure exactly which tags designate a frame and which don't. There is the occasional gotcha such as

itr: kind: 8 dvx:

, but other than that it