New features wanted!! Apply here!

[davidbgtx]

Good idea. These things may also be helpful:
1. Under the Window menu choose Cascade to put the ladder views into old-style MDI mode. This allows you to view multiple ladder views at once.
2. Dragging the little bar at the very top of a ladder view scroll bar will split each view into two panes, allowing you to view different areas of the same code block.
3. Right click on a rung and select Monitor Values, and there are options for automatically loading rung/instruction contents into a Data View.
[/quote]


Number 2 does help, did not know you could split a window into 2 panes (do you have D0-More for Dummies yet).

[mhw]

Please include the ability to enter the "Extra Info" and "Description" to the "Create Nickname" dialog box.

[BobO]

Please include the ability to enter the "Extra Info" and "Description" to the "Create Nickname" dialog box.

Already in the code. Will be in the DmD 1.4.

[Garyhlucas]

Speaking of editing, I find that when copying tags adding the leading underscore and a trailing digit wastes a ton of time when revising the tag. Typically when I copy a tag it is because most of it is useful and just the least significant characters get changed. Having to delete the leading underscore is a nuisance.

[Mike Nash]

Speaking of editing, I find that when copying tags adding the leading underscore and a trailing digit wastes a ton of time when revising the tag. Typically when I copy a tag it is because most of it is useful and just the least significant characters get changed. Having to delete the leading underscore is a nuisance.

Hear, Hear! Me too.

I wind up selecting the original tag to edit, highlighting what I need (all of it), canceling, then pasting as a new tag and editing that. Also a major waste of time though.

[BobO]

Sorry guys. Tags have to remain unique. The trailing digit is to ensure uniqueness. The leading underscore is to make it clear that these have been modified by the software and need user attention. Imagine copying a rung into a large project, and having 5 out of 500 tags modified for uniqueness. Needle in a haystack. The way we do it makes it easy to find and fix those.

[plcnut]

Bob, I have found the same as these other fellows. Could the underscore be added to the ending instead? The part that makes it such a pain is having to edit the first character AND the last character.

[BobO]

Bob, I have found the same as these other fellows. Could the underscore be added to the ending instead? The part that makes it such a pain is having to edit the first character AND the last character.

It isn't required. It was just there to make them stand out. We'll see if we can talk Mark into making that an option.

[Controls Guy]

Yeah, this one bugs me too.  I realize the nicknames must remain unique (because they can be used for alternate addressing), but the way it's done now feels very unwieldy, and if some more user-friendly idea could be found, I agree that it would make users lives easier.

Thanks!   

[Controls Guy]

Actually, rather than spend effort optimizing stuff like this, I'd vote for upgrading the doc Import/Export facility.  (Primarily by putting description line breaks in separate columns rather than embedding a control character.  Much easier to read and also much easier to use Excel drag-and-fill one column at a time if it's done that way).

For decades, I've used the external CSV copy as the official version of Allen-Bradley docs (Siemens too) and only import to the programming package, and not use the internal editor at all.  All that editing UI for tabular data is there for the using in spreadsheets, why not leverage it, instead of expending a lot of effort reinventing it?

[franji1]

Actually, rather than spend effort optimizing stuff like this, I'd vote for upgrading the doc Import/Export facility.  (Primarily by putting description line breaks in separate columns rather than embedding a control character.  Much easier to read and also much easier to use Excel drag-and-fill one column at a time if it's done that way).

For decades, I've used the external CSV copy as the official version of Allen-Bradley docs (Siemens too) and only import to the programming package, and not use the internal editor at all.  All that editing UI for tabular data is there for the using in spreadsheets, why not leverage it, instead of expending a lot of effort reinventing it?

It already does this as an option on export, and implicitly does this on import.

[Controls Guy]

Really?  Awesome!  When was this added?  That was a request of mine a long time ago and I didn't realize it was ever done.

Since you do have that, I'm not sure you need to change how the internal docs editor works.  It seems to me like that solves the problems of users like me who don't like the way the automatic nickname disambiguation works, just use Excel or Open Office for the docs editor.  Much better editing capabilities anyway, plus it doesn't know to differentiate the nicknames so it gives you the chance to do it yourself in whatever way you like before importing to DMD or DSoft.  (Plus the drag and fill may give you the opportunity to do it almost effortlessly anyway)

[Mike Nash]

I don't know. Does this mean we don't need spell check because we can always just look it up in a dictionary?

(Not that spell check works worth a darn, since people are usually using the wrong words to benign (sic) with.)

My vote goes to ditching the leading underscore - optional is fine. I usually don't do this type of thing wholesale anyway. Yes, if I do need to do a bunch, I use an external spreadsheet. In the days of old I would write a program in QuickBasic to do it.

But then it gets back to my wanting to have Drive1 Drive2, etc., for which I've already had my hand slapped. Maybe we could get smart-sorting that knows the proper order is DriveI DriveII DriveIII DriveIV, etc.? 

[BobO]

I don't know. Does this mean we don't need spell check because we can always just look it up in a dictionary?

(Not that spell check works worth a darn, since people are usually using the wrong words to benign (sic) with.)

My vote goes to ditching the leading underscore - optional is fine. I usually don't do this type of thing wholesale anyway. Yes, if I do need to do a bunch, I use an external spreadsheet. In the days of old I would write a program in QuickBasic to do it.

But then it gets back to my wanting to have Drive1 Drive2, etc., for which I've already had my hand slapped. Maybe we could get smart-sorting that knows the proper order is DriveI DriveII DriveIII DriveIV, etc.? 

Names have to be unique, but how we accomplish it is completely arbitrary. When we added the leading underscore, we did so to solve a perceived issue that clearly isn't as big a deal as the problem we caused doing so. We'll change it.

So who slapped your hand?

[Controls Guy]

I don't know. Does this mean we don't need spell check because we can always just look it up in a dictionary?

Well, I just feel that if there's already a superior tool for editing tabular data, why spend effort upgrading the runner up that could be spent on adding features that MUST be in the programming package?

My vote goes to ditching the leading underscore - optional is fine. I usually don't do this type of thing wholesale anyway. Yes, if I do need to do a bunch, I use an external spreadsheet. In the days of old I would write a program in QuickBasic to do it.

Yup, me too, though in my case it was VB and VBA.  I've even done AB code generation in VB.