sact wrote:Overall responsiveness and speed. I know java applications and games can be somewhat unresponsive. But when I added all the possible stuff in to the picture, background image, dual mode, priority bands and ego, ego's speed got slow, with multiple pictures simultaneously, and addiotional stuff turned on, PICEDIT 1.3M6 got really slow.
The main culprit with that set up will be the dual mode. It is slow even when activated for a single picture and seems to get worse the higher the zoom factor. I've been aware of this for some time. The way it is implemented isn't ideal. I could make it a lot faster, so at some point I'll go back to that feature and rework it a bit. What I might do is add some timings around the various bits such as the dual mode, the background image, priority bands and then try different approaches to see what seems it up.
sact wrote:How about showing just one picture at the time. If showing multiple simultaneously is so resource consuming that PICEDIT turns slow, maybe PICEDIT could automatically create temporary backupcopies of each picture being edited, thus requiring resources for displaying only one picture at the time while not requiring user to save other pictures being edited, viewed and or tested with ego.
Thanks for the suggestion. It already does limit what it draws for the unselected pictures but I might be able to make that better.
sact wrote:Besides with full zoom, the only real option for 1920x1080 and above, other pictures currently just barely are visible from background and the only reasonable way access them is via Window-dropdown menu. Hotkey for switching between opened images and or those thumbnails shown in the sketch might be nice.
Nice suggestion. I will certainly add this.
sact wrote:
Ego
* It's a very spiffy feature, like you said, feels just like in the game, mouse control maybe as well?
* I hope in future there's an option to set.horizon?
* Could the views for the ego be chosen directly from AGI project in addition to possibility selecting from externals views?
* EGO's movement speed adjustable?
* Maybe some icon could blink etc if EGO steps on either green, cyan, and or blue control line. Option to toggle blue, conditional obstacle?
The horizon, view chooser and speed adjustment are all things I have on my todo list, so hopefully we'll see those features in a future milestone. I was trying to think of a way to show ego hitting the other control lines. Yeah, the blue obstacle needs to handled. I was playing around with Space Quest 2 the other day within PICEDIT and noticed that the obstacle lines were mainly blue. So I guess what we're suggesting here is some sort of ego settings dialog where we can change all these things, with speed maybe being handled with a hot key of some sort.
sact wrote:
Bug
* File -> Open Recent -> That file no longer exists.
The item, file that no longer exists, stays in the recently opened files nevertheless.
Thanks for the bug report. Should be easy to fix. I'm surprised that there weren't a lot more bugs. There was quite a bit of rework as part of the multi picture support and command list.
sact wrote:
PICEDIT has come a long way from mere picture editor. With the current direction it is going, I reckon the final version will be more like Java AGI IDE than mere picture editor. Which is not a bad thing. Thanks to ScummVM, AGI regardless it's age, works almost in every platform there is. And PICEDIT is a prime example that so can the tools... Well almost.
Yet another sketch based on the latest version...
<picture removed>
At one point during the development of Milestone 6 I did have a Pictures tab next to the Commands tab. The intention was to do what you suggested previously where all the pictures for either the current physical directory or a selected PICDIR would be displayed. But I ran out of time to implement that. I'll get back to it in a future Milestone.
Thanks for the feedback and sorry it took a while to get back to you. It is that time of year. With everything I've said that is on my todo list, it seems like I've got enough for a whole Milestone simply to tidy up the usefulness of the features I've already released. So maybe one of the next Milestones will be such a tidy up Milestone and won't introduce any new features as such.