Activity for Alan Green
-
Alan Green posted a comment on ticket #567
Mmm, shouldn't the ethos be to fix the root cause rather than use plasters over the wound. There seem to be two of us saying there is a problem with the sourceforge rpm (for both 39 and 40), it just needs re-compiling properly.
-
Hi Dave, unfortunately I can't help at the moment because XtrkCAD is not installable on Fedora at present. Once bug #567 is fixed i'm happy to make a video, etc reproduce it for you.
-
Removal of user info from xtrkcad files
-
5.3.0GA RPM Install Error
-
Also see attached. Also creates nice effects on contours created by the Create Parallel Line tool. This time with a smaller drop shadow offset. Think having seen how it works so well with more than just buildings/platforms, it might be worth it being a per layer effect, rather than a per object offect, with the ability to dial in the drop shadow offset amount (and possibly colour) for each layer.
-
Full trace as requested. This one is coming from the beta2 so the version change from beta1 to beta 2 has had no effect (i.e. it was not a compile anomaly). I noticed when watching it that even if an outer offset is requested it always creates an inner offset ghost track first before scaling it up and sending it to the outer side as per the user request, is this possibly causing it, is the scaling up as it does this possibly resulting in dfferent x,y coords which makes the snap join function thinks...
-
Full trace as requested. This one is coming from the beta2 so the version change from beta1 to beta 2 has had no effect (i.e. it was not a compile anomaly). I noticed when watching it that even if an outer offset is requested it always creates an an inner offset ghost track first before scaling it up and sending it to the outer side as per the user request, is this possibly causing it, is the scaling up as it does this possibly resulting in dfferent x,y coords which makes the snap join function thinks...
-
Full trace as requested. This one is coming from the beta2 so the version change from beta1 to beta 2 has had no effect (i.e. it was to not a compile anomaly). I noticed when watching it that even if an outer offset is requested it always creates an an inner offset ghost track first before scaling it up and sending it to the outer side as per the user request, is this possibly causing it, is the scaling up as it does this possibly resulting in dfferent x,y coords which makes the snap join function...
-
Apologies created as anonymous by mistake
-
Stil getting unexpected effects when using Create Parallel Line function on polygons
-
Ability to apply drop shadow to selected objects
-
Text rotation angle not preserved after Ungroup
-
Text rotation angle not preserved after Ungroup
-
Manage > Custom Designed Parts > Move To does not remember last directory/folder path
-
Color picker eye dropper tool in Change > Properties not working
-
Filled polygon in Modify mode obscures X-Y scale/ruler markers
-
Filled polygon in Modify mode obscures X-Y scale/ruler markers
-
Finer selection feature
-
Ability to do multi-select using mulitple click and drag windows
-
Change Object Properties > Cancel saves unwanted changes to text
-
When using Join Tracks function over a polygon, the join creates a track without ties/sleepers
-
When using Join Tracks function over a polygon, the join creates a track without ties/sleepers
-
Apologies accidentally logged this as anonymous
-
Vertex editing - Equivalent of an 'ortho' mode when moving multipe vertices
-
Ability to rotate complex objects/groups by vertex
-
Ability to snao from vertex to grid when moving a whole object/group
-
P.S. running xtrkcad-beta --sync as it suggested does not provide any extra info when the crash occurs
-
Xtrk/cAD crashes when downsizing layout dimensions
-
Ability to increase line curve resolution when converting for modify/split/trim
-
Looks good, best way to shakedown test this is to try it across a number of use cases and see what happens. Will look forward to the release.
-
Attached
-
Here's the new trace, it has done it again. I watched it fully this time and wasn't a Terminal cut and paste issue. It really is flipping to the DrawNewTrack function 2924-2926 then back to 263. Can also confirm it did not join the tracks. Thread 1 "xtrkcad-beta" hit Breakpoint 1, CmdParallel (action=4, pos=...) at /storage/source/MR/xtrkcad/sf/v5.3.0b1/src-530b1/app/bin/cparalle.c:196 196 /storage/source/MR/xtrkcad/sf/v5.3.0b1/src-530b1/app/bin/cparalle.c: No such file or directory. (gdb) c Continuing....
-
Here's the new trace, it has done it again. I watched it fully this time and wasn't a Terminal cut and paste issue. It really is flipping to the DrawNewTrack function 2924 then back to 263. Can also confirm it did not join the tracks. Thread 1 "xtrkcad-beta" hit Breakpoint 1, CmdParallel (action=4, pos=...) at /storage/source/MR/xtrkcad/sf/v5.3.0b1/src-530b1/app/bin/cparalle.c:196 196 /storage/source/MR/xtrkcad/sf/v5.3.0b1/src-530b1/app/bin/cparalle.c: No such file or directory. (gdb) c Continuing....
-
Wierd it sent it via email, I noticed my last on this thread has moved to a Page 2 on your sourceforge website (possibly because of the length of that full trace). Yes that trace does look a bit spurious after Line 249, all I can thisnk is its a cut and paste error from Terminal, possibly because the trace was so long and left the page. I'll run it again, hopefully the shorter trace to 291 will work.
-
Sorry but I can't see it in the interface or the help files. A couple of observations: There is no Layer field/text box in the 'Change Object Proerties/Describe' dialog box for locos and rolling stock. If the loco/stock's layer is configurable like other object layers then it needs to at least i) show in the 'Change Object Proerties/Describe' dialog box for that object, and ii) ideally that Layer field is editable/pull down to choose/change the layer. As far as I can tell this leaves the only one...
-
Breakpoint 1 at 0x1f0d1a: file /storage/source/MR/xtrkcad/sf/v5.3.0b1/src-530b1/app/bin/cparalle.c, line 196. (gdb) r Starting program: /usr/local/bin/xtrkcad-beta [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Gtk-Message: 10:33:16.495: Failed to load module "pk-gtk-module" [New Thread 0x7fffe91d76c0 (LWP 9114)] [Thread 0x7fffe91d76c0 (LWP 9114) exited] [New Thread 0x7fffe91d76c0 (LWP 9115)] [New Thread 0x7fffe88f16c0 (LWP 9116)] [Thread...
-
Ability to hide/show rolling stock and locos when in Design Mode
-
I'm afraid its still not catching/logging any breaks Does the '(gdb) r -d track=3 -d endPt=2' command possibly need tweaking to work properly, because we could catch the ConnectTrack breaks before when just using the plain 'run' command without any options/arguments.
-
Can I just confirm the whole procedure with all the tweaks above. Is the below correct? gdb /usr/local/bin/xtrkcad-beta (gdb) break cparalle.c:248 (gdb) break ConnectTracks (gdb) r -d track=3 -d endPt=2 repeat the test case. When it hits the break point use next until it hits line 2017 (gdb) print d (gdb) print a (gdb) print connectDistance (gdb) print connectAngle next until hit line 2031 (gdb) print *epp0 (gdb) print *epp1 (gdb) print trk0 (gdb) print trk1 next until it exits ConnectTracks 249...
-
I'm afraid it didn't get as far as producing a long trace, the only feedback gdb gave was the below on startup. No trace or break was created when running the two Parallel commands. (gdb) break ConnectTracks Breakpoint 1 at 0x1743bb: file /storage/source/MR/xtrkcad/sf/v5.3.0b1/src-530b1/app/bin/track.c, line 1985. (gdb) r -d track=3 -d endPt=2 Starting program: /usr/local/bin/xtrkcad-beta -d track=3 -d endPt=2 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1"....
-
Ran Parallel on Long Track Thread 1 "xtrkcad-beta" hit Breakpoint 1, CmdParallel (action=4, pos=...) at /storage/source/MR/xtrkcad/sf/v5.3.0b1/src-530b1/app/bin/cparalle.c:196 196 /storage/source/MR/xtrkcad/sf/v5.3.0b1/src-530b1/app/bin/cparalle.c: No such file or directory. (gdb) cont Continuing. Ran Parallel on Short Track Thread 1 "xtrkcad-beta" hit Breakpoint 1, CmdParallel (action=4, pos=...) at /storage/source/MR/xtrkcad/sf/v5.3.0b1/src-530b1/app/bin/cparalle.c:196 196 in /storage/source/MR/xtrkcad/sf/v5.3.0b1/src-530b1/app/bin/cparalle.c...
-
Sure no probs, have gdb aeady installed. After running the 'break cparalle.c:196' command in the gdb shell i'm getting a question back, see below. Do want me to answer yes or no to it? break cparalle.c:196 No symbol table is loaded. Use the "file" command. Make breakpoint pending on future shared library load? (y or [n])
-
i'm content with you using UUIDs if you are, I know they are 'randomly' generated for any object and I use them in coding too when processing/analysing massive datasets. In reality there is no such thing as a randomly generated ID (or any kind of 'random' for that mater) but its close eenough for this application. The chances of two objects getting the same UID in XtrKCAD alone, let alone the whole operating system, are so slim. The operating system is full of these UIDs, one for every object. You...
-
Hi, i'm content with using UUIDs if you are, I know they are 'randomly' generated for any object and I use them in coding too when processing/analysing massive datasets. In reality there is no such thing as a randomly generated ID (or any kind of 'random' for that mater) but its close eenough for this application. The chances of two objects getting the same UID in XtrKCAD alone, let alone the whole operating system, are so slim. The operating system is full of these UIDs, one for every object. You...
-
Hi, i'm content with using UUIDs if you are, I know they are 'randomly' generated for any object and I use them in coding too when processing/analysing massive datasets. In reality there is no such thing as a randomly generated ID (or any kind of 'random' for that mater) but its close eenough for this application. The chances of two objects getting the same UID in XtrKCAD alone, let alone the whole operating system, are so slim. The operating system is full of these UIDs, one for every object. You...
-
Hi, i'm content with using UUIDs if you are, I know they are 'randomly' generated for any object and I use them in coding too when processing/analysing massive datasets. In reality there is no such thing as a randomly generated ID (or any kind of 'random' for that mater) but its close eenough for this application. The chances of two objects getting the same UID in XtrKCAD alone, let alone the whole operating system, are so slim. The operating system is full of these UIDs, one for every object. You...
-
Hmm, have just been trying different values in Preferences > Connection Distance. It starts connecting when the Connection Distance is set to the max allowed by XtrkCAD (2.5cm). I can put in any value of 2.499 or lower and it stops working again. This is fully repeatable. This seems like too much of a coincidence that it only accepts your arbitrary max value. Are you absolutely sure the connection distance feature is working properly in this latest version?
-
See attached vdeo just to assure you i'm not making this up. Happens regularly on curves and straights. I'm rnning this beta version on Fedora 38. Is a unique issue specific to this latest beta release. Just an idea, but if the magentic snap which is supposed to recognise and join these tracks during the Parallel cmd is set as default to 0.1"/2.54mm then could it possibly be a decimal places rounding error creeping in somewhere (e.g. a float value geting converted to an integer or smaller decimal...
-
xtr file attached as requested. Didn't join again.
-
Sure, attached are another 'before and after' example using a simpler curve to show this is not specifically an s-curve issue. Regularly happens on plain curves, s-curves, straights. Again the main difference in the xtc files is that the original curve before the parallel cmd is made up of an E4 and T4, and the new curves after the parallel cmd are made up of just E4s. I'm guessing if the mid-point had joined properly they would also have been made of an E4 and T4 too? The x-y coordinates are all...
-
Hi Adam, Yes sorry I wasn't sure whether it was an issue in old versions either or a new issue with the latest release, hence not being sure whether to raise it as a bug or freature request. I've used Run Trains mode a lot before but I think the difference this time is i'm trying to use XtrkCAD to test its suitabilty for a broad range of proper protoype car-load sequence operations/movements rather than just running a few random trains around it to check for clearances, spur lengths, etc. This issue...
-
Aha, this might help you. To emulate what the xtc code would look like when the two tracks have been joined using the magnetic snap, I took the file I sent you above, clicked and dragged one track away from the other using Move, then brought it back closer again so they snap together. Then resaved it as a new xtc file and compared it with the original. Comparison observations as follows: i) the third number field containing the 80 and 260 made no difference. Both files still had the 80 and 260 in...
-
Aha, this might help you. To emulate what the xtc code would look like when the two tracks have been joined using the magnetic snap, I took the file I sent you above, clicked and dragged one track away from the other using Move, then brought it back closer again so they snap together. Then resaved it as a new xtc file and compared it wiht the original. Comparsin observations as follows: i) the number field containing the 80 and 260 made no difference. They both still had the 80 and 260 in them. ii)...
-
Aha, this might help you. To emulate what the xtc code would look like when the two tracks have been joined using the magnetic snap, I took the file I sent you above, clicked and dragged one track away from the other using Move, then brought it back closer again so they snap together. Then resaved it as a new xtc file and compared it wiht the original. Comparsin observations as follows: i) the number field containing the 80 and 260 made no difference. They both still had the 80 and 260 in them. ii)...
-
Hi Adam, example xtc file attached. These are two curves created using the Create Parallel Track command, the offset distance being set to 17.5cm from the original tracks. I don't have a huge amount of experience interpreting the raw text fields in the xtc file but I think the second E4 is the common point on both curves where they should have auto-joined. The x y values look identical to 5 decimal places, but there is another number field after those x-y values (possibly a z-value?), one of which...
-
Hi Dave, In addition to the rc files, the main ones that spring to mind for me in .xtc files are the objects that refer to out to other files in the userspace (e.g. Draw >Notes > Document). I don't know if these are the only objects which do it, they just happen to be the ones I use most so know there are issues with their filepath showing the user's login name. You guys will hopefully know better than me if there are any others. Ref the suggested solution, that sounds like a great idea. Anything...
-
Hi Dave Yes it is the user space (as opposed ot system space) file paths which are the issue. Applies to both Windows and Linux. If your software is being used to its fullest extent then there are many examples sread across, for example, the rc file for example. A number of examples just from the file I am working on at present are: paths.bitmap /home/<login_username>/<rest of="" path=""></rest></login_username> Custom paramaters files paths /home/<login_username>/<rest of="" path=""></rest></login_username>...
-
Ability to convert text to drawing/poly for grouping
-
'Text can only be modified in Describe Mode' error stopping Modify/Extend working on track objects under a text bounding box
-
'Text can only be modified in Describe Mode' error stopping Modify/Extend working on track objects under a text bounding box
-
Pendng resolution of #544 for now here is a screenshot of what is happening. This is SM45 scale/gauge Outside offset of 20cm Some of the segments do not snap together. Whilst not visible in the image some of them have snapped together properly. The pieces which did not snap properly into place have been drawn/created correctly, it is purely something to do with their position. I can move them about until they snap to one end and then they auto snap to the other and fit into where they should be....
-
In 'Run Trains' mode, stock summary no longer displayed in Status Bar when left-click on object
-
In 'Run Trains' mode, stock summary no longer displayed in Status Bar when left-click on object
-
Removal of user info from xtrkcad files
-
Removal of user info from xtrkcad files
-
Not experiencing this issue anymore with the new 5.3.0beta1. Many thanks
-
Can cofirm fixed in 5.3.0 beta1. Many thanks
-
Hi, have been putting the 5.3. 0 beta1 through its paces a lot on a large and complex layout and the Parallel track function is generally so much more stable in this version (bar the drawing offset issue raised in a separate request). Not seeing this error occur anymore. Suggest closure/fixed, will raise again as new request if re-appears but so far looks like its gone. Many thanks.
-
It is simply your stock build of the beta but using the SM45 layout scale, the Parallel command does not work around 80-90% of the time.
-
Preset top speed of simulator to fast to get fine control for shunting/yard and branchline/shortline operations
-
Track ends do not join when using Parallel Track on more than one segment
-
Cannot create new prototype due to dialog box bugs
-
Extra Note for i) and ii). Could be put on the Train Control panel in an area with the odometer.
-
Edit to Note 2: One example of how this could be activated is using the right click menu as described in 1. Three options in the menu: Full, Full (Timer), Empty
-
Rolling Stock Empty/Full Status
-
Measuring Time
-
I can't reproduce it on your file either though yours is in N scale whereas i'm currently mostly designing in the large scales (e.g. 16mm SM45). Some ideas for lines of investigation for using the snap when tracks are near/over text boxes: Because of the physical size of these large scale layouts the track often has to be entirely designed and drawn with track displayed on the screen as a single line. Could this be affecting the snap? Note it is impractical to zoom right in until the track shows...
-
Tested it just now and does it when both clicking on the top-right X and when using File > Exit. Also forgot to mention the same issue occurs on 'Menu > Manage > Parts List' too.
-
Car Inventory and Add Car dialog box forget their sizing when opened
-
'Guard0 is hosed' dialog when using Create Parallel Track
-
Track Snap endpoint function stops working near lines/polygons/text boxes
-
'Guard0 is hosed' dialog when using Create Parallel Track
-
'Guard0 is hosed' dialog when using Create Parallel Track
-
No change detection or undo when text changed in Change Object Properties
-
Car Inventory and Add Car dialog box forget their sizing when opened
-
Color Draw reverts back to By Object after any change in Display Options
-
Error when trying to save as *.xtce file
-
Option for cut/copied objects ot keep their original Layer when Pasted
-
Join Two Lines/Polylines Layer Inheritance
-
Various Bugs in Comment/Plain Text box
-
Various Bugs in Comment/Plain Text box
-
Add Hyperleda .rpm package for ASTAP
-
Include Fedora 38 repo on ASTAP OpenSUSE repositories
-
Additional Track Gauges and Scales
-
Option in Export to Bitmap to print background image with track.
-
Extra Zoom Levels
-
Application icon missing in Linux Installations of 5.2.1a
-
Add 1:29 scale (Aristocraft) to layout options
-
Annotation icons visible at all zoom levels
-
Apologies, forgot to mention, if you use one of the options above to resolve it then the scale setting for stock would need to move from global (in Options - Layout) to a local level, e.g.. the Update Car dialog would need a combo box to select/change the scale for each car in the Car Inventory List. Perhaps defaulting to the global scale setting, then those who need change it can do so with the combo box.
1 >