I came with idea of a feature that may be very helpful for pol users

There could be a button in uofiddler 'Item' menu, that would create a basic itemdesc entry with info from tiledata (name, graphics, movable, weigth etc) for selected item and store it in clipboard, so user can easily paste it into .cfg

Or maybe allow creation of the entire itemdesc.cfg file with definitions of all the tiledata entries as well.

Yukiko wrote:Or maybe allow creation of the entire itemdesc.cfg file with definitions of all the tiledata entries as well.

One big itemdesc.cfg with all items from tiledata? That'd be evil :>
And it'd mess with itemdescs in packages.

But creating files would be nice indeed.
A 'select cfg file' option to select witch file we want to write to and then
select item in items window and
press a button (or a key, that'd be faster) to append item definition to selected file

If developers are following "good practices" they shouldn't be creating custom items in the graphic ID range. However I do see your point with regard to "pre-defined" items like doors and containers. That would be a problem. Maybe let us specify a range of graphic IDs to build into an itemdesc.cfg file. I like the idea of being able to do one at a time but I can see the need for being able to define a range as well as with walls, floor tiles and carpet etc.

*Hint*
activate testplugin and use the contextmenu inside item tab

Sweet :> But could you add a keybinding for that? It'd be much faster.

And a simple editor would be handy to create a .cfg entry template
something like:

Item @objtype
{
Name @name
Graphic @graphic
Script :pkg:scriptname
Newbie 1
Whatever whatever <- some properties that aren't in tiledata
Whatever2 whatever_2
Whatever3 lol
Weight 22 <- this would set weight to 22 instead of tiledata weight
}

where @something would be tiledata value of a property

Also a simple formula for objtype would be nice
like +x offset, or a starting number that'd increment with every item added to cfg