Tag Info

New answers tagged

0

In standard C11, you cannot make GUI code, because standard C11 does not know about graphical user interfaces, or screens (you only have  stdout) or keyboards, or mouses. Any GUI code would use some non-standard thing. A common way to provide such non-standard things is by providing an API thru some library. Details are of course horribly platform and ...


0

GUIs are generally a platform-specific affair. On Windows, the creation of windows and the widgets within them are managed by the Windows GDI library. On Unix-like systems running the X Window System, that is done through xlib by creating windows within windows, and drawing on them. Libraries like GTK+, Qt, wxWidgets, etc., exist to abstract away these ...


4

Sure it is. Just put all the code that was used to write the libraries into your own program, and you can do anything they can do. In other words, having libraries is a convenience. Smaller source files are easier to work with, you don't have to know the intricacies of X (or if graphics drivers if you also want to go without X), reusing widget-drawing ...


1

Solution 1 is the one preferred by most users, based on my experience. The problem you described, "he user drops objects on the initial state of the worksheet probably assuming that the first object (a) was never inserted," can be mitigated with a temporary placeholder visual that indicates an object was dropped, but its state is not yet computed. I would ...


1

You could use the system used by Windows. If you open a dialog to edit multiple items, the entries where both pieces of data match is displayed with the data, where they differ a "" or similar string is displayed. The user must select an individual item to edit the multiple-value entries, or they can overwrite it which will replace the field on all items. ...


0

For legacy GUI applications you would benefit two ways: Business logic track: ask sb with business knowledge for descriptive info and write UI end-to-end automated tests. You get a good test suite for regression. Code contemplation track: if I were to write unit tests for legacy code I would do it only either for refactored or debugged code. IMHO there is ...


0

To problem with this projects is that you don't want to change the code without adding unit tests, but you usually can't and unit tests without changing the code. If your project is like a typical legacy project, than you have large classes with lot of really long functions, without a clear role. My strategy is the following: Try to identify the roles of ...



Top 50 recent answers are included