Activity for Dan Sebald
-
Dan Sebald committed [2fd174]
Implement colormap for axes objects in gnuplot (bug #48667).
-
Add documentation about PCRE library regexp stack overflow (bug #51589).
-
Require some plot object present to show legend for gnuplot (bug #50483).
-
Check for valid zoom region in qt graphics toolkit (bug #51645).
-
Supply missing axis labels for gnuplot toolkit (bug #51759).
-
Free variable editor QMainWindow memory upon delete (bug #51954).
-
Fix origin-axes-location line color in gnuplot graphics toolkit (bug #52063).
-
Clarify assert() test with the amount by which the test fails (bug #52004).
-
Change gnuplot-toolkit fprintf() sequence to handle single axis tic (bug #52140).
-
* liboctave/util/oct-rl-edit.h: Remove unused function declaration (patch #9459).
-
Handle x-axis and y-axis independently for proper axis lines and tick marks (bug #52141)
-
Remove persistent axes lines of gnuplot toolkit multiple plots (bug #52170, bug #52186).
-
Properly restore the input stream pointer at end of textscan (bug #52116 et al.)
-
Properly restore the input stream pointer at end of textscan (bug #52116 et al.)
-
Reuse constructor code of delimited stream.
-
Remove all delimiters from whitespace list in textscan function (bug #52479).
-
Fix textscan missing fields and number reads for cell-specified delimiters (bug #52550).
-
Simplify gnuplot toolkit scripts for image/non-image data plots (bug #52589).
-
Make gnuplot color have three components for interpolated edge color (bug #52595).
-
For gnuplot toolkit, do not map TrueColor data to colormap size (bug #52599).
-
Make gnuplot toolkit image color mapping consistent with OpenGL toolkits (bug #52624).
-
Set gnuplot color data to half output range when autoscaling zero input range (bug #52624).
-
Protect being-deleted objects on figure list from second deletion (bug #52666)
-
Correct a host of small formatting issues with Texinfo manual (bug #52774)
-
doc: Make code-example apostrophe in the manual cut-and-paste friendly (bug #52775).
-
Add a help entry and documentation for @ character (bug #52771).
-
Make documentation Sec 26.1 more consistent and Sec 25.4 clearer (bug #52685)
-
Clean up lookup() code and documentation with no functional changes (bug #52785).
-
Supply the OpenGL viewport setting for gl2ps_print context (bug #52940).
-
Use proper stylesheet syntax to avoid tooltip black background (bug #44554).
-
Range-check variable editor m_table_colors before using (bug #53137)
-
Remove unused hidden axes properties for camera view (bug #52940).
-
Add boundary tests on QLists associated with Qt inputdlg() routine (bug #53209).
-
Make the variable editor multi-panel via a QMainWindow layout (bug #53046)
-
Make variable editor code compile under Qt4 (bug #53259)
-
Create an icon for the variable editor (bug #53260)
-
subspace.m: Change BIST tests to more accurately test function (bug #53242).
-
Use OS GUI highlight backgroud color for variable editor name label (bug #53274)
-
Improve fullscreen action for variable editor panes (bug #53275)
-
Add a QFrame to the variable editor panels and adjust tooltips (bug #53275)
-
Fix history widget selecting two lines with one click (bug #53346).
-
Prevent openvar() crash when called twice with same variable (bug #53411)
-
Enable delete-on-close behavior of variable editor panels (bug #53467)
-
Enable delete-on-close behavior of variable editor panels (bug #53467)
-
Remove NoFocus policy from Variable Editor and restore highlight (bug #53410)
-
Prevent GUI drag-and-drop relocation freeze for some Qt versions (bug #53392).
-
Fix locked GUI panels for Qt 5.6.1 through 5.7.0 series versions (bug #53409)
-
Add a Ctrl+F unhide/hide in-page find footer to the Documentation window (bug #53006)
-
Add standard key bindings and actions to in-page Documentation find (bug #53006)
-
When Variable Editor is tabbed, activate that tab via openvar (bug #53443).
-
Focus variable panel when Variable Editor comes from hidden state (bug #53443).
-
Add focus proxy for Variable Editor to prevent loss of variable focus (bug #53410)
-
Do Variable Editor focus retention and titlebar highlight properly (bug #53410).
-
Restore Variable Editor focusWidget lost in dock/undock transition (bug #53410)
-
Change Documentation shortcut context to not interfere with Editor (bug #53640).
-
Fix OpenGL line-stipple bug manifested as Nouveau driver crash (bug #53644)
-
Use consistent gnuplot toolkit font syntax allow SVG fractional font size (bug #53737)
-
Make figure/waitbar window title behavior consistent among toolkits (bug #53793)
-
Use default title bar to preserve GUI float decorations (bug #53276)
-
Prevent hidden predecessor windows appearing when successor is floated (bug #53357)
-
Work around for Variable Editor unfloat/float on Ubuntu Unity (bug #53893)
-
Supply missing refloat function symbol when QTBUG-44813 is ignored (bug #54051)
-
Supply missing iostream declarations via <istream> (bug #54091)
-
Pair fclose() with all fopen() and prevent file-io.cc test fails (bug #54180).
-
Do not make floated widgets a Qt::Window to conserve title bar (bug #54078)
-
Remove residual ticks for gnuplot graphics toolkit (bug #50509, #55038).
-
Add shortcut keys for octave_dock_widget undock, dock and close (bug #54078)
-
Supply folder field for dir() on Windows UNC shares (bug #57664).
-
Restore editor x-offset after highlight-all-occurrences double-click (bug #58372)
-
Use UTF-8 encoding rather than Symbol font for gnuplot terminals (patch #8696).
-
I was just looking at this. My guess would be that /* I don't think any error checks on font name are possible; just set it */ SVG_set_font(""); appears after the int_error() rather than before the options loop. Everything else after the options loop is just output, not input.
-
svg terminal seg-faulting after partially failed "set term" options parsing
-
If you think that mods for 10, 12, 14 and 17-bit support might be robust enough to always be reporting original depth, we could make such a change and test for a while to see if anything bad starts to happen. But if you think the ->depth structure element is more a guide for the end-user, then yes I suppose that contextual meaning for that parameter could confuse the application programmer, i.e., the programmer does a Ping and sees one depth but then the Read produces something of wider depth. Terms...
-
It does get complicated trying to describe the depth in one variable, even prior to importing the image into GM memory and adding any processing. To summarize, there are File data depth: The underlying data in bits-per-pixel. From Octave's perspective, it seems this is a variable of importance. Octave has a data/colormap model, so it is worthwhile keeping the data and colormap distinct. File channel color depth: If there is a color map applied, it can (only) increase the number of bits of color depth....
-
BMP decoder forces image depth to 8 bits
-
STL.h readImages writes NULL of filename unchecked
-
I've added some supporting script files and C++ source files that will convert the gnuplot CVS repository using cvs2git, git, g++ and sed. I've placed all the files in their own git repository, but also the actual files are present, so just run tar -xzf git_translation.tar.gz and look through the README for instructions. The only thing done to enhance the cvs2git result is to use sed to put proper committer info in the cvs2git dump file and add author information to the cvs2git dump file. Otherwise,...
-
Here's a new Version 0.4 beta that does not stop at the first added line in the ChangeLog, but instead looks a little further for the first item in the addition block. An item has a star or colon in the line somewhere. The idea is to allow situations where the first addition might be a space or something similar while the author information is actually in the addition hunk a line or two later. Here are four cases that are corrected by this new version: commit <sfeam!2008-05-30T04:52:36+00:00Z> diff...
-
The physical layout of the plot is correct, but the generation of the contours is the question. I can better illustrate the issue with contours by removing the borders. Try set border 0 set contour splot x why is there no initial contour at the y = -10 level? It seems there should be. It could be some math rounding error, e.g., it computes a level of -10.00000000001 which is out of range. It could be an indexing start issue. Will have to wait a few weeks on this one.
-
I'm recalling this one. It seemed a really peculiar bug that came out of nowhere when there didn't appear to be previous issues. I'm guessing that contour levels utilize the tick-spacing code in some way, and I wonder if something was changed with tick marks in the past that influences the color selection. Note the missing contour level in example https://sourceforge.net/p/gnuplot/bugs/1603/#e770 Ethan's example showing the underneath surface has the same property, contours start at -80 when perhaps...
-
Here's what looks to be the relevant lines of code in the share/LaTeX/Makefile construct via configure: texdir = /usr/local/share/texmf/tex/latex/gnuplot install-texDATA: $(tex_DATA) @$(NORMAL_INSTALL) @list='$(tex_DATA)'; test -n "$(texdir)" || list=; \ if test -n "$$list"; then \ echo " $(MKDIR_P) '$(DESTDIR)$(texdir)'"; \ $(MKDIR_P) "$(DESTDIR)$(texdir)" || exit 1; \ fi; \ for p in $$list; do \ if test -f "$$p"; then d=; else d="$(srcdir)/"; fi; \ echo "$$d$$p"; \ done | $(am__base_list) | \ while...
-
Another tiny modification, but I think it has no ramifications on the final list. Version 0.3 beta.
-
I'm attaching a second version of the utility, version 0.2 beta. This version allows a second input file with a git-log containing the list of files that have changed. If provided, the utility will discard any entries in which ChangeLog was the only file that changed in the changeset. Example usage: git log --format='commit <%cE!%cIZ>' -p --unified=50 ChangeLog > CL.diff git log --format='commit <%cE!%cIZ>' --name-only > files.lst git_changelog_author CL.diff files.lst > author.txt
-
It's been requested that the gitID be modified from the SHA to the following format: <committer-id!yyyy-mm-ddThh:mm:ssZ> This can be done without a change in the code. Try the following sequence of commands instead: git log --format='commit <%cE!%cIZ>' -p --unified=50 ChangeLog > ChangeLog.diff git_changelog_author ChangeLog.diff > author.txt This seems to work nicely, distinguishing the commiter from the author.
-
C++ utility to aid in sorting out ChangeLog authorship for CVS-to-git repository conversion
-
You put into words what I was thinking, i.e., that maybe re-configuring with qt5 somehow cleared up a font issue. I distinctly recall a big gap of extra whitespace at the front of 1234567890 and a font of slightly different appearance.
-
I'm at a loss as to why there seems to have been an improvement in alignment for the CVS version. I rolled back to the code of cvs update -D 2017-07-03 but can't reproduce the text box offset. I noticed in the log that qt5 is in use, but I sort of remember qt4. I wondered if having done a re-configuration in the past week was an issue. But TERMLIBS="-lX11" /home/sebald/gnuplot/gnuplot/gnuplot/configure --with-qt=qt4 still didn't produce plots with the text box overlapping the text. Well, there's...
-
I can't seem to produce a plot near as bad as what I was seeing a week ago when the box was off so much that it landed on top of characters in a random fashion. Nor is there as much variance vertically either. Was there some kind of change made in the last week? My guess was that maybe font substitution caused computation problems. The only difference I now see is much more consistent balance with the patch versus the current version. The descenders, yes looks like just a single pixel of white between...
-
A screenshot for the following script: set label "1234567890" at 0,-0.4 boxed font "DejaVuSans, 5" noenhanced left set label "1234567890" at 0,-0.2 boxed font "DejaVuSans, 7" noenhanced left set label "1234567890" at 0,0 boxed font "DejaVuSans, 9" noenhanced left set label "1234567890" at 0,0.2 boxed font "DejaVuSans, 12" noenhanced left set label "1234567890" at 0,0.4 boxed font "DejaVuSans, 14" noenhanced left set label "1234567890" at 0,0.6 boxed font "DejaVuSans, 18" noenhanced left set label...
-
Give the attached patch a try. It works pretty well for me. The main issue, as I see it, is that positioning a bounding box, no matter how its height and width are determined separately from the text as currently done isn't going to work. The graphics systems knows about font positioning, kerning, etc., so it is the one that can get a precise fit of the frame. QGraphicsItem is a somewhat limited class, but it turns out there is a very convenient proxy system whereby widgets can be turned into QGraphicsWidget...
-
Thread vs. process: a lot of those advantages/disadvantages are obviated by systems with multiple cores. E.g., context-switching isn't needed so often if a process doesn't have to give up its CPU. (Although, in Linux processes sure bounce around a lot from CPU to CPU, but that could be just for compilation where one file finishes then another starts...which is typically when I'm sitting watching the system monitor.) We know pipes are slow, but are sockets too? Super-efficiency hasn't been a major...
-
Lightweight in what sense? Less memory? Certainly gnuplot is bigger when the WXT code is included within it. What I'm arguing is that the outboard driver for WXT is the model consistent with X11 (the original interface) and Qt. I recall on the discussion list going back to 90s or 00s about the terminal model that gnuplot uses and not deviating from that. I never said anything about discarding responding to events from user-visible program. Is there some difference between WXT and Qt that I'm missing?...
-
I'm not following your reasoning on this Bastian. How is it that the outboard driver is a lot of platform-specific code? The outboard driver should be almost completely wxWidgets, single-threaded, GUI in the main thread--the only thread. Doing so greatly simplifies things. Let's use Qt as an example of this: sebald@ ~/gnuplot/gnuplot/gnuplot/src/qtterminal $ grep WIN32 * grep: CVS: Is a directory gnuplot_qt.cpp:#ifdef _WIN32 gnuplot_qt.cpp:#if defined(_WIN32) grep: images: Is a directory grep: po:...
-
How will the Windows version be broken by making the WXT driver outboard? wxWidgets framework is designed to be cross-platform. The sockets functions are part of the framework, so we shouldn't have to struggle to make that work. I would have said something long ago had I known that WXT were to be integrated the way it was, and the result of going to an outboard model back then would have probably saved a lot of people a lot of work. There looks to be some tricky code in there for interrupt signal...
-
That's something possible to do, but I'm against that because it's then making gnuplot an all-out wxWidgets application. The model you describe is the model used for Octave's new GUI/framework. It uses Qt as the main process and puts the core program in a worker process. It's a good model for that, but not here because gnuplot is not a GUI.
-
I forget what the motivation for persist mode is, but why exit if one wants essentially the full featured rotation, etc.? The outboard driver is the model consistent with all other terminals--the historical terminal driver. The amount of code in qt_waitforinput has a lot to do with mousing issues. Perhaps it can be done better. I don't seen any reason that outboard client/server communications can't be made as fast as inboard, as far as the user drag-and-rotate perception is concerned. Qt isn't the...
-
OK, I've gotten over another hurdle by establishing a socket connection between wxt_term (the client) and gnuplot_wxt (the server). The client/server code is pretty simple in the end, but it was a bit tricky in the sense that the example programs have a main visible window and are interactive so that the server is well established before there's any attempt to access that server. Some things I had to do: Deal with a race condition between launching the external gnuplot_wxt process. The client Connect...
-
I'm attaching a ZIP file of a very rudimentary re-arrangement of the code in wxterminal subdirectory moving in the direction of adding a gnuplot_wxt outboard driver. It doesn't do a whole lot, sort of a "hello world" type of thing. But it is a step in that direction if we want to persue this further. The only sort of "diff" from the repository is in gnuplot-rearrange_wxterminal_compilation-djs2017jul08.patch which is the Makefile describing the files in the project. In incorporates file name changes...
-
I'm attaching a ZIP file of a very rudimentary re-arrangement of the code in wxterminal subdirectory moving in the direction of adding a gnuplot_wxt outboard driver. It doesn't do a whole lot, sort of a "hello world" type of thing. But it is a step in that direction if we want to persue this further. The only sort of "diff" from the repository is in gnuplot-rearrange_wxterminal_compilation-djs2017jul08.patch which is the Makefile describing the files in the project. In incorporates file name changes...
-
As T.M. mentions, WXT is much Windows like in look and feel. It has nice fonts too, very clean. The thing is, varied gnuplot terminals has the ability to sort of match other applications. For example, Octave uses a Qt GUI now and selecting gnuplot's Qt terminal makes it appear that the GUI and the plots it creates are the same application (when they really aren't). I can imagine someone writing an application in wxWidgets and wanting to integrate gnuplot WXT plots for a seamless match. Yes, it would...
1 >
