ATTENTION: You are viewing a page formatted for mobile devices; to view the full web page, click HERE.

DonationCoder.com Software > Screenshot Captor

Screenshot Captor 4.10 todo list

<< < (2/4) > >>

mouser:
Funny question since once of the features i had on my list to bump it to v5 was saving+loading object presets..  I'll have to check my todo list for any other major features planned.

Sometimes I try to only advance a major version when it heralds a bunch of big new features.. But occasionally I'll just look at the features added since last major version and decide it's time for a major version bump.  In other words, I don't have a well defined rationale for when to increase major version numbers -- other than the general idea that Version X+1 should have a ton of stuff that version X does not.

ScreenManiac:
Well, it's not quite what I was hoping for. No objections to saving the whole set, but to speed up workflows, such an ini-file would look more like this:

CustomTool_1
Caption="Red Arrow thick"
LineColor=#EA1C1C
LineWidth=8
CustomTool_2
Caption="Yellow Arrow thin
LineColor=#FFFF00
LineWidth=1
CustomTool_3
Caption="-----"
CustomTool_4
Caption="Textbox big"
FontSize=80

This would constitute its own user dropdown menu. CustomTool_3 is a separator with no other function than organizing the presets in the dropdown. The important thing to notice: You can have multiple presets for the same object (red arrow AND yellow arrow) within one ini-configuration.

You'd simply pick your "Red Arrow thick" and start drawing. Without having to worry what other (unwanted) object changes this change entails. Because it won't change any of the other objects. The next textbox will NOT come up with a totally weird and out-sized font just because you happened to need it one time only, unfortunately in that same session when you stored your arrow as a preset.

Your remedy to avoid this - manual tweaking of the ini-file - may be a tall order for some users, especially if English is not their native language. Non-progammers are not very comfortable with finding and deleting specific lines in ini-files.

Maybe I missed something and you had other advantages in mind that I fail to see? My expectations are primed by other software, which led to a certain workflow over the years. Always ready to ditch the old ways, so if you found a more efficient workflow, please explain.

TaoPhoenix:
Funny question since once of the features i had on my list to bump it to v5 was saving+loading object presets..  I'll have to check my todo list for any other major features planned.

Sometimes I try to only advance a major version when it heralds a bunch of big new features.. But occasionally I'll just look at the features added since last major version and decide it's time for a major version bump.  In other words, I don't have a well defined rationale for when to increase major version numbers -- other than the general idea that Version X+1 should have a ton of stuff that version X does not.
-mouser (October 10, 2014, 07:15 PM)
--- End quote ---

Your prog doesn't seem to be in range, but a lot of progs seem to be tied elsewhere, as in "we don't support below x". I know it's risking drifting off topic a bit, but looping back it seems each program goes through this. It's grand when it starts, yay a few updates, then it gets into support misery!

This is far from the thread to get too far into theory; it is just an attempt to get one specific local data nugget to chew on. Having just checked, I am on 4.85, but then I basically only needed that one little left click feature you put in ages ago, so I'm fine.

Just scouting out local-wide how a long running project develops.

mouser:
Maybe I missed something and you had other advantages in mind that I fail to see? My expectations are primed by other software, which led to a certain workflow over the years. Always ready to ditch the old ways, so if you found a more efficient workflow, please explain.
--- End quote ---

Well, I can envision rare cases where you want to save whole sets of object tool settings at once, BUT no, you didn't miss anything -- it would be better if the program let you choose which single object tool settings to save in the file at the time of saving, so you could choose without having to edit the manually edit the file.  Or I'll just make it so, if you are on a specific tool panel, it will only save that tool settings, but if the tool panel is closed, it will save all.

I will try to add this asap.

As far as more than one entry in a single file and custom separators -- that won't be possible the way i've done it.

mouser:
New beta uploaded;  this version only saves the currently selected tool settings in the preset file.  If you leave object mode or just get out of a specific object tool mode, it will save all.  You will get a hint about this in the Save dialog.
This should make it considerably easier to work with object tool presets.

Two other items to note:

* The Tool Preset menu, built from filenames, is sorted.  You can use this to help you arrange the menu in the order you want.
* In the More Interface Options tab, you can choose to show the Object Presets menu on the root main menu (instead of a submenu of the Objects menu); this may be useful for those of you who will be switching presets frequently.
Let me know how it works for you.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version