Koda

Welcome to Koda bug tracker!

At the moment you can post bugreports or suggestions anonymously. But registered users have some benefits: attaching files, commenting, voting, tracking tasks e.t.c.

Due some asshole started spamming tracker, now (at least for some time) it’s not allowed to create anonymous tasks. Sorry for unconvenience.

In edit fields you can use DokuWiki syntax for formatting.

Tasklist

FS#216 - Picture Editor: some observations

Attached to Project: Koda
Opened by Chris Haslam (c.haslam) - Saturday, 23 April 2011, 06:15 GMT+3
Type Bug Report
Category Application
Status Unconfirmed
Assigned To No-one
Operating System All
Severity Low
Priority Normal
Reported Version Development
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

See the doc for the way I understand it.

The Load | File Open dialog filter only offers .jpg, .jpeg, .bmp and .gif.

Via Load, I moused to, and selected, D:\WINDOWS\system32\setup.bmp. This appeared in Custom path to image, and the .bmp appeared in Selected image.

I then changed the path to @SystemDir\setup.bmp. Select image cleared. A bug?

In the course of this, I discovered that there is only one level of Undo here.

Thoughts

  • The File Open dialog filter may be too tight, e.g. .exe should be permitted, perhaps others; however it did allow me to enter F:\Program Files\AutoIt3\SciTE\Koda\FD.exe .
  • @ScriptDir should be permitted in Custom path to image. This would be helpful to a user who puts his .bmps, etc. in the same tree as his script. As Run (F9) is now, running the form would show a blank picture. Perhaps Koda could instead temporarily create a picture containing the file spec. Or one saying “File not available to Koda”. Being able to use @ScriptDir is hugely important to me!
  • Koda could, when it generates code, replace a path that begins !:\WINDOWS (where ! is any drive leter) with @WindowsDir. Similarly for @SystemDir and @TempDir I see no harm in this.

Perhaps a filename and ext should be generated by Koda as @ScriptDir\fnam.ext

  • I had a case a while back where picture being a %varaible would have been useful.

Some of these thoughts come from consideration of updating a form in a .au3. I would rather not have to change the file spec whenever I update the script.

  • Having only one input field for the file spec is not user-unfriendly for people like me who make mistakes! I suggest Custom path to image be replaced the fields in the screen shot attached.
This task depends upon

Comment by Chris Haslam (c.haslam) - Saturday, 23 April 2011, 06:24 GMT+3

Revised screen shot

Comment by Admin (Lazycat) - Tuesday, 26 April 2011, 16:54 GMT+3
I then changed the path to @SystemDir\setup.bmp. Select image cleared. A bug?

This should not be cleared automatically. At least it's not for me. This can be cleared after pressing "Test" button.

The File Open dialog filter may be too tight, e.g. .exe should be permitted, perhaps others; however it did allow me to enter F:\Program Files\AutoIt3\SciTE\Koda\FD.exe .

Exe is permitted when you work with icon control. What the reason to have it for picture?

ScriptDir should be permitted in Custom path to image. This would be helpful to a user who puts his .bmps, etc. in the same tree as his script. As Run (F9) is now, running the form would show a blank picture. Perhaps Koda could instead temporarily create a picture containing the file spec. Or one saying “File not available to Koda”. Being able to use @ScriptDir is hugely important to me!

The reason why this was not added - this macro only available when script running. Koda can't expand this macro to full path. So, the "Test" button will never show if this custom path correct.

I can add ScriptDir or other Autoit macro here, but testing will be uanavailable.

Koda could, when it generates code, replace a path that begins !:\WINDOWS (where ! is any drive leter) with @WindowsDir. Similarly for @SystemDir and @TempDir I see no harm in this.

I would not let to do that to automatic. Who know, maybe someone need absolute path. But with some additional button - maybe.

Having only one input field for the file spec is not user-unfriendly for people like me who make mistakes! I suggest Custom path to image be replaced the fields in the screen shot attached.

Ok, probably having source path visible (while non-editable) is ok.

Comment by Chris Haslam (c.haslam) - Tuesday, 26 April 2011, 21:20 GMT+3
Exe is permitted when you work with icon control. What the reason to have it for picture?

The screen shot in the doc shows icons in fd.exe :!:.

it did allow me to enter F:\Program Files\AutoIt3\SciTE\Koda\FD.exe .

Is being able to override the filter what you expect? Or is it Windoze?

I can add ScriptDir or other Autoit macro here, but testing will be unavailable.

@ScriptDir is desirable, for apps written in AutoIt which have their own pictures/icons. Disable Test button?

I would not let to do that to automatic. ... But with some additional button

OK

Comment by Chris Haslam (c.haslam) - Tuesday, 26 April 2011, 21:39 GMT+3

Is View list as a filter for icons? If so,

  • Should it be called Size filter?
  • Should it be disabled when the Editor is invoked from a Picture control?

(This stuff is on the edge of what I know!)

Comment by Admin (Lazycat) - Wednesday, 27 April 2011, 11:24 GMT+3
The screen shot in the doc shows icons in fd.exe .

Yes, this is case of Icon control. If you want, you can add image description, something like: "The screenshot show the dialog look for Icon control."

Is being able to override the filter what you expect? Or is it Windoze?

Windows. Any filter can be overriden if you enter name directly.

@ScriptDir is desirable, for apps written in AutoIt which have their own pictures/icons. Disable Test button?

Maybe, but it's require constantly checking of input box contents while editing. So, maybe message below input field, saying that testing with this macro unavailable.

Is View list as a filter for icons? If so,

No, it's just control the size of icons that will be displayed in left list. This is have not any effect outside this dialog.

Should it be disabled when the Editor is invoked from a Picture control?

Yes, it's disabled.

Comment by Chris Haslam (c.haslam) - Wednesday, 27 April 2011, 23:20 GMT+3
The screen shot in the doc shows icons in fd.exe .

Because we know that reading fd.exe causes an exception error, perhaps the screen shot should show icons from a different application. How about %SystemRoot%\system32\freecell.exe (on my PC, D:\WINDOWS\system32\freecell.exe). It only has one icon in it. It would be nice to have an example that has more.

maybe message below input field, saying that testing with this macro unavailable.

Yes

you can add image description, something like: "The screenshot show the dialog look for Icon control."

Done

Is View list as a filter for icons?

"View list as" doesn't make sense to me. How about renaming it "Size to view"?

Comment by Admin (Lazycat) - Wednesday, 04 May 2011, 10:34 GMT+3
How about %SystemRoot%\system32\freecell.exe

Ok.

"View list as" doesn't make sense to me. How about renaming it "Size to view"?

Ok, I will change.

Loading...