It has been suggested that an accordion-type menu be included in some way to allow common tasks to be more easily accessible. Such a menu might look like the attached

Parser cannot handle extensible field sets if there are more fields in the idf file being loaded than are provided by default in the IDD file.

Cut/Copy/Paste operations in and out of the editor don't behave as expected. Need to clarify intent for "copy" vs "copy for spreadsheet" vs "copy values", etc.

The CRUD actions do not notify the node graph of changes.

Saved files have inconsistent behaviour when viewed in notepad vs notepad++. Investigate and endure that line endings are correct and consistent.

Recent files and screen size/shape are not consistently restored from previous session.

Use networkx or similar to track relationships between IDF nodes similarly to the way networkx is used to track relationships for object references and object-lists. This is important and will allow more advanced features later such as visualizing, analyzing and validating air loops and plant loops.

I tries to open Exercise1A.idf from the example files of energyplus 8.2 while running your editor on windows 8.1:

Traceback (most recent call last): File "C:\Users\matt\Documents\idfplusnew\build\idfplus\out00-PYZ.pyz\idfplus.m ain", line 123, in open_file File "C:\Users\matt\Documents\idfplusnew\build\idfplus\out00-PYZ.pyz\idfplus.m ain", line 204, in load_file File "C:\Users\matt\Documents\idfplusnew\build\idfplus\out00-PYZ.pyz\idfplus.m ain", line 167, in load_idf File "C:\Users\matt\Documents\idfplusnew\build\idfplus\out00-PYZ.pyz\idfplus.p arser", line 851, in parse_idf TypeError: 'NoneType' object has no attribute 'getitem'

The IDD parser seems to ignore the "!" in some cases. If I try to import an idd file I get the error:

bob@alice:~/idfplus$ python idfplus.py
Traceback (most recent call last):
  File "~/idfplus/idfplus/widgets/setupwiz.py", line 135, in load_idd
for progress in idd_parser.parse_idd(dir_name):
  File "~/idfplus/idfplus/eplusio/parser.py", line 540, in parse_idd
set_length = int(obj_tag_dict['extensible:'][0])
ValueError: invalid literal for int() with base 10: '<'(idf)

Best,

Benjamin

Class ZoneHVACEquipmentConnections inclues the following classes which should be separate:

• Fans
• Coils
• Evaporative Coolers
• Humidifiers and Dehumidifiers
• Heat Recovery

"New" button and checkbox for "case sensitive" cause errors if used before an idf file is present.

The windows executables are not currently digitally signed. This causes warnings when users first run the file. Integrate code signing into the build process.

Currently only zip files are provided. Create an installer for windows (MSI?) and ubuntu (.deb?). Investigate MacOS as well.

Long comments without line breaks will be clipped. Need to automatically split them onto multiple lines when writing the idf file.

Comments are currently read-only. Allow editor to be read/write when ensure comments are formatted appropriately for saving.

The PySide website claims that it is now unmaintained. Should investigate moving to PyQt5.

Seems to be window-related and possibly network drives. Needs to be investigated

These operating systems appear to take 2-3 times longer to load idf files under some circumstances. Linux and Windows 7 appear to load files very quickly. More testing would be appreciated if anyone reads this!

Integrate help into a new widget and allow direct linking to topics through the context menu.

The first time and idd file of a specific version is needed the user is prompted for the location of the idd file. This is a confusing process and should be improved. Possibly incorporate this into a setup wizard. Each new version of idd that is required could trigger a "New IDD Wizard" to help users understand what is needed. Another good option would be to automatically search for EnergyPlus versions and process all found idd files.

The program will currently crash if the idf file isn't perfect. Instead, there should be a friendly error window describing what the problem is.

The log viewer widget appears to be broken on Windows. There are no errors associated with this, the window is simply empty.

I find it useful to see the units next to the fields when using the IDF Editor.

Add a way for the editor to notify a user if the file they are editing was modified by another program (like the official IDF editor does). Probably want to use QFileSystemWatcher.

Add a search and replace feature similar to what is offered in the official IDF Editor.

The current behaviour of text fields in the class table does not allow wrapping of long field values. Wrapping should be enabled and both width and height of cells should adjust depending on contents so that the contents is always fully available.

Need to refresh class to see the other fields.

IDF+ should use the standardized semantic versioning as described at http://semver.org/.

Hi Matt, I think this might be a bug, see the video attached. I am using Wndows 10 and Python 3.7.5. The model is in a folder on Desktop. Cheers, Yi

Copying/Pasting or Duplicating an object simply creates a reference to the object! This defeats the purpose because the values of all the fields will be linked. Need to deepcopy objects instead of shallow. This is a pain due to recursion errors so need to reimplement deepcopy().

The filename if the window title should display a * beside it if the file has been modified. Currently, the * is always present.

Standardize font faces, sizes and weights. Make them more consistent, predictable and allow them to be user definable.

The idd/idf is written entirely from scratch. It works, but is quite slow and probably fragile. The parser should be completely rewritten, probably using a well-established parsing library like PyParsing. This would be many times faster and more robust. A rewrite will likely be necessary anyway once EnergyPlus moves to the upcoming xml file format.

GUI stalls when opening an IDF with a single object (e.g. ZoneHVACFourPipeFanCoil) from a blank IDF.

If an existing IDF is open and user tries to open a single object IDF it causes an unhandled exception.

Investigate making the info widget an html widget to allow formatting and html links. Possible improvements would be to allow directly linking to the html help file for the current object.

It can be very slow when applying a filter to the object class view. This may be unavoidable, but more research is needed to identify the actual reason.

There is currently not test framework in place. Implement it and start writing tests. Incorporate tests into build process as well. Investigate continuous integration.

Gives error about not being able to find file. Error includes hard-coded file path from build directory for some reason.

(I come here every year or so to see the progress you're making on this utility and try it out briefly. Seems like you're gone a long way already, good job!)

The Transpose function (CTRL+T) is a great idea. It'd be great if one could copy and paste like in excel. I may want to copy the construction from one cell and paste into the others, eg:

Related to this would be to able to copy a range of cells from IDF+ to Excel and back. Currently it's copying the entire IDF text object

Files saved in windows vs unix-like systems have different end of line characters. This does not affect the idf file itself, but does affect comments and how they are displayed in the editor. It should be transparent and always behave in an "expected" way.

Clicking around in the class tree will crash idfplus. The error seems to be related to the delegate assignment. Happens only when clicking from item to item quickly, so there could be a race condition in the delegates code?

Hi,

Firstly nice project, cheers.

I'm having trouble opening an idf file. possibly due to the idd import tool having troubles.

I'll have a go installing this tool in ubuntu.

Mike

Add a button that opens the current file in the system's default text editor. Make the editor used customizable in preferences.

Building releases is currently manual and include multiple steps/operating systems. Automate the process!

The editor can currently have only one document open at a time. Add the ability to have multiple documents open at once. Use tabs, windows or allow the user to choose. Provide ways to switch between currently open files. This feature requires a significant modification to how the various parts of the editor address an idf file--they currently assume there is only every one.

IDD files are processed only once per version, however, there will be times when changes are made to the way IDF+ processes/reads the IDD files. This will require a way to force the IDD files to be re-processed, for example after an update of the editor.

schedule:compact does not convert units, for example. Fields don't have any tags that it catches - must make a special check for schedules?

It would be nice if you could jump to an object from the context menu. For example, you are in a SetpointManager:Scheduled object and trying to remember which schedule you need to assign. It would be nice if you could right-click while hovering over the Schedule Name drop down field and select "Jump to Object" to switch to the Schedule objects screen.

This is something that I tend to do often in the IDF Editor by selecting a specific schedule object then using the Find feature to jump to it.

The first time the program loads it is awkward and needs to be customized. It's also unclear how to use it. Improve initial user experience. Potentially create a "setup wizard" to explain a few things and possibly pre-process IDD files instead of the first time they are needed.