push
push
pop
pop
push
push
5 years agoDemo of exporter specific export routineexporter_ideaexporter_idea/demo-of-exporter-specific-expo
Demo of exporter specific export routine
XXX: Bitrotten - does not build
XXX: Bitrotten - does not build
refresh
refresh
refresh (create temporary patch)
refresh (create temporary patch)
Refresh of crasy-test
Crasy test
Note that this throws away code to draw pad and pin names
XXX: Bitrotten - not up to date w.r.t. BB Vias.
Note that this throws away code to draw pad and pin names
XXX: Bitrotten - not up to date w.r.t. BB Vias.
rebase (CONFLICT)
rebase (CONFLICT)
Crasy test
Note that this throws away code to draw pad and pin names
XXX: Bitrotten - not up to date w.r.t. BB Vias.
Note that this throws away code to draw pad and pin names
XXX: Bitrotten - not up to date w.r.t. BB Vias.
rebase
rebase
5 years agoFix indentation in one place (avoids spurious gcc warning)for_masterfor_master/fix-indentation-in-a-few
Fix indentation in one place (avoids spurious gcc warning)
Tidy up range check in misc.c
For consistnecy with other range checks involving max_copper_layer, and to
drive home the fact we are checking for exceeding max_copper_layer + 2.
NB: The +2 relates to the bottom silk and top-silk layers, whose numbers
are used to denote the bottom and top layer groups respectively.
re-write:
layer > max_copper_layer + 1
to become:
layer >= max_copper_layer + 2
For consistnecy with other range checks involving max_copper_layer, and to
drive home the fact we are checking for exceeding max_copper_layer + 2.
NB: The +2 relates to the bottom silk and top-silk layers, whose numbers
are used to denote the bottom and top layer groups respectively.
re-write:
layer > max_copper_layer + 1
to become:
layer >= max_copper_layer + 2
5 years agoFixup some bugs from the added soldermask layersfor_master/fixup-some-bugs-from-the-added
Fixup some bugs from the added soldermask layers
(TODO: Finish this fixup and merge it down into the relevant patches)
(TODO: Finish this fixup and merge it down into the relevant patches)
5 years agodraw.c: Opencode the mask layer object drawing functionsfor_master/draw-c-opencode-the-mask-layer
draw.c: Opencode the mask layer object drawing functions
Calling DrawLayer() did not render using the correct graphics context / colors.
NB: We're still using the "wrong" GC, but we now avoid selecting inappropriate
colors which prevent (say) PS export working correctly for mask layer objects.
Calling DrawLayer() did not render using the correct graphics context / colors.
NB: We're still using the "wrong" GC, but we now avoid selecting inappropriate
colors which prevent (say) PS export working correctly for mask layer objects.
5 years agoAdd support for a two soldermask layers, defining regions of removed maskfor_master/add-support-for-a-two
Add support for a two soldermask layers, defining regions of removed mask
File-format wise, these work similarly to how silk layers are supported now:
Layer (1 to n "[NAME]") # "ordinary" design layers
Layer (n+1 "silk") # bottom side silk
Layer (n+2 "silk") # top side silk
Layer (n+3 "bottom soldermask") # bottom side soldermask
Layer (n+4 "top soldermask") # top side soldermask
File-format wise, these work similarly to how silk layers are supported now:
Layer (1 to n "[NAME]") # "ordinary" design layers
Layer (n+1 "silk") # bottom side silk
Layer (n+2 "silk") # top side silk
Layer (n+3 "bottom soldermask") # bottom side soldermask
Layer (n+4 "top soldermask") # top side soldermask
5 years agoAvoid hard-coding the number of extra layers in use (for 2x silkscreen)for_master/avoid-hard-coding-the-number
Avoid hard-coding the number of extra layers in use (for 2x silkscreen)
We will shorty add support for soldermask layers, so this will need changing
NOTE....... IF THE parse_y.y patch in the stg series before this gets
dropped, there is one more case where + 2 needs to be replaced with EXTRA_LAYERS
We will shorty add support for soldermask layers, so this will need changing
NOTE....... IF THE parse_y.y patch in the stg series before this gets
dropped, there is one more case where + 2 needs to be replaced with EXTRA_LAYERS
5 years agoFixup incorrect usage of MAX_ALL_LAYERS and SILK_LAYER in GUIfor_master/fixup-usage-of-max_all_layers
Fixup incorrect usage of MAX_ALL_LAYERS and SILK_LAYER in GUI
These were incorrectly changed to be relative to MAX_ALL_LAYERS, and should be
relateive to MAX_LAYERS like they used to be. This is because we are counting
extra buttons past the number of copper layers (MAX_LAYERS).
Similarly, SILK_LAYER happens to be 2.. this is NOT why there are two buttons
in the GUI after the copper buttons, one is for the current silk layer, one is
for the rats layer.
These were incorrectly changed to be relative to MAX_ALL_LAYERS, and should be
relateive to MAX_LAYERS like they used to be. This is because we are counting
extra buttons past the number of copper layers (MAX_LAYERS).
Similarly, SILK_LAYER happens to be 2.. this is NOT why there are two buttons
in the GUI after the copper buttons, one is for the current silk layer, one is
for the rats layer.
find.c: The User varaible needs to die...
Reduce its usage to where absolutely necessary... oh, what a surprise,
another variable passing state down into add_object_to_list ()
Reduce its usage to where absolutely necessary... oh, what a surprise,
another variable passing state down into add_object_to_list ()
Add the drc flag as a parameter
Ok, this is nasty.. I'm obscuring setting of the global varaible... be careful!
Ok, this is nasty.. I'm obscuring setting of the global varaible... be careful!
Add the bloat as a parameter
Ok, this is nasty.. I'm obscuring setting of the global varaible... be careful!
Ok, this is nasty.. I'm obscuring setting of the global varaible... be careful!
5 years agofind.c: Refactor some common sequences into a helper functionfor_master/find-c-refactor-some-common-se
find.c: Refactor some common sequences into a helper function
5 years agoparse_y.y: Try to avoid two shift/reduce and reduce/reduce warningsfor_master/try-to-avoid-warnings-from
parse_y.y: Try to avoid two shift/reduce and reduce/reduce warnings
TODO: Check this matches up against our expected behavior.
Removing the parsedata section ("I think") has no effect, as elements
hit the alternative | element clause within parsepcb.
HOWEVER... I need to check whether there is any other valid syntax
inside an element file, or any backwards compatibility with old formats
which we may miss with the loss of parsedata.
TODO: Check this matches up against our expected behavior.
Removing the parsedata section ("I think") has no effect, as elements
hit the alternative | element clause within parsepcb.
HOWEVER... I need to check whether there is any other valid syntax
inside an element file, or any backwards compatibility with old formats
which we may miss with the loss of parsedata.
Play with grid snapping heuristics a little
Require the pointer to be inside the bounding box of a pin / pad / via before snapping.
This makse it MUCH easier to place vias in a regular grid spaced at the PCB grid spacing.
Require the pointer to be inside the bounding box of a pin / pad / via before snapping.
This makse it MUCH easier to place vias in a regular grid spaced at the PCB grid spacing.
Add hysteresis to grid-snapping
5 years agoRemove graphics pointer from HID structureapi_refactorapi_refactor/remove-graphics-pointer-from
Remove graphics pointer from HID structure
5 years agoPass a HID_DRAW * instance to hid_expose_callback() rather than a HID * pointerapi_refactor/pass-a-hid_draw_instance_to_hi
Pass a HID_DRAW * instance to hid_expose_callback() rather than a HID * pointer
Drawing should eventually be independent of the HID
Drawing should eventually be independent of the HID
5 years agoFixup draw.c not to special case based on HID name, use flags insteadapi_refactor/fixup-draw-c-not-to-special
Fixup draw.c not to special case based on HID name, use flags instead
5 years agohidgl: Provide more explicit management of rendering instancesapi_refactor/hidgl-provide-more-explicit-ma
hidgl: Provide more explicit management of rendering instances
Provide an (hidgl_instance *) pointer which is used to refer to a hidgl
instance when caling hidgl_* APIs that are instance, but not hidGC specific.
Various hidgl APIs now take the hidgl_instance as a parameter, or in the case
of hidgl_new_instance(), return a new instance.
Graphics APIs which previously had a hidGC parameter remain the same, as the
hidglGC structure now contains a link to the hidgl instance which created it.
This change paves the way to potentially having multiple hidgl instances active
simultaneously, and removes various global variables (such as "buffer" and
"global_depth") which were previously accessible to allow the gtk-gl HID to
draw using the hidgl internals.
The gtk-gl HID_DRAW graphics API now subclasses the hidgl HID_DRAW API, so the
gtk-gl HID can access the (non-private) gtk_gc->hidgl_gc.* fields.
Provide an (hidgl_instance *) pointer which is used to refer to a hidgl
instance when caling hidgl_* APIs that are instance, but not hidGC specific.
Various hidgl APIs now take the hidgl_instance as a parameter, or in the case
of hidgl_new_instance(), return a new instance.
Graphics APIs which previously had a hidGC parameter remain the same, as the
hidglGC structure now contains a link to the hidgl instance which created it.
This change paves the way to potentially having multiple hidgl instances active
simultaneously, and removes various global variables (such as "buffer" and
"global_depth") which were previously accessible to allow the gtk-gl HID to
draw using the hidgl internals.
The gtk-gl HID_DRAW graphics API now subclasses the hidgl HID_DRAW API, so the
gtk-gl HID can access the (non-private) gtk_gc->hidgl_gc.* fields.
TEMP: Fixup fallout from nogui change
*** Might be nicer to just implement a no-op end_layer function for each HID_DRAW?
*** Might be nicer to just implement a no-op end_layer function for each HID_DRAW?
push
push
Demo of exporter specific export routine
XXX: Bitrotten - does not build
XXX: Bitrotten - does not build
refresh
refresh
refresh (create temporary patch)
refresh (create temporary patch)
Refresh of crasy-test
refresh
refresh
refresh (create temporary patch)
refresh (create temporary patch)
Refresh of crasy-test
Crasy test
Note that this throws away code to draw pad and pin names
XXX: Bitrotten - not up to date w.r.t. BB Vias.
Note that this throws away code to draw pad and pin names
XXX: Bitrotten - not up to date w.r.t. BB Vias.
rebase (CONFLICT)
rebase (CONFLICT)
Crasy test
Note that this throws away code to draw pad and pin names
XXX: Bitrotten - not up to date w.r.t. BB Vias.
Note that this throws away code to draw pad and pin names
XXX: Bitrotten - not up to date w.r.t. BB Vias.
rebase
rebase
Fix indentation in one place (avoids spurious gcc warning)
Tidy up range check in misc.c
For consistnecy with other range checks involving max_copper_layer, and to
drive home the fact we are checking for exceeding max_copper_layer + 2.
NB: The +2 relates to the bottom silk and top-silk layers, whose numbers
are used to denote the bottom and top layer groups respectively.
re-write:
layer > max_copper_layer + 1
to become:
layer >= max_copper_layer + 2
For consistnecy with other range checks involving max_copper_layer, and to
drive home the fact we are checking for exceeding max_copper_layer + 2.
NB: The +2 relates to the bottom silk and top-silk layers, whose numbers
are used to denote the bottom and top layer groups respectively.
re-write:
layer > max_copper_layer + 1
to become:
layer >= max_copper_layer + 2
Fixup some bugs from the added soldermask layers
(TODO: Finish this fixup and merge it down into the relevant patches)
(TODO: Finish this fixup and merge it down into the relevant patches)
draw.c: Opencode the mask layer object drawing functions
Calling DrawLayer() did not render using the correct graphics context / colors.
NB: We're still using the "wrong" GC, but we now avoid selecting inappropriate
colors which prevent (say) PS export working correctly for mask layer objects.
Calling DrawLayer() did not render using the correct graphics context / colors.
NB: We're still using the "wrong" GC, but we now avoid selecting inappropriate
colors which prevent (say) PS export working correctly for mask layer objects.
Add support for a two soldermask layers, defining regions of removed mask
File-format wise, these work similarly to how silk layers are supported now:
Layer (1 to n "[NAME]") # "ordinary" design layers
Layer (n+1 "silk") # bottom side silk
Layer (n+2 "silk") # top side silk
Layer (n+3 "bottom soldermask") # bottom side soldermask
Layer (n+4 "top soldermask") # top side soldermask
File-format wise, these work similarly to how silk layers are supported now:
Layer (1 to n "[NAME]") # "ordinary" design layers
Layer (n+1 "silk") # bottom side silk
Layer (n+2 "silk") # top side silk
Layer (n+3 "bottom soldermask") # bottom side soldermask
Layer (n+4 "top soldermask") # top side soldermask
Avoid hard-coding the number of extra layers in use (for 2x silkscreen)
We will shorty add support for soldermask layers, so this will need changing
NOTE....... IF THE parse_y.y patch in the stg series before this gets
dropped, there is one more case where + 2 needs to be replaced with EXTRA_LAYERS
We will shorty add support for soldermask layers, so this will need changing
NOTE....... IF THE parse_y.y patch in the stg series before this gets
dropped, there is one more case where + 2 needs to be replaced with EXTRA_LAYERS
Fixup incorrect usage of MAX_ALL_LAYERS and SILK_LAYER in GUI
These were incorrectly changed to be relative to MAX_ALL_LAYERS, and should be
relateive to MAX_LAYERS like they used to be. This is because we are counting
extra buttons past the number of copper layers (MAX_LAYERS).
Similarly, SILK_LAYER happens to be 2.. this is NOT why there are two buttons
in the GUI after the copper buttons, one is for the current silk layer, one is
for the rats layer.
These were incorrectly changed to be relative to MAX_ALL_LAYERS, and should be
relateive to MAX_LAYERS like they used to be. This is because we are counting
extra buttons past the number of copper layers (MAX_LAYERS).
Similarly, SILK_LAYER happens to be 2.. this is NOT why there are two buttons
in the GUI after the copper buttons, one is for the current silk layer, one is
for the rats layer.
find.c: The User varaible needs to die...
Reduce its usage to where absolutely necessary... oh, what a surprise,
another variable passing state down into add_object_to_list ()
Reduce its usage to where absolutely necessary... oh, what a surprise,
another variable passing state down into add_object_to_list ()
Add the drc flag as a parameter
Ok, this is nasty.. I'm obscuring setting of the global varaible... be careful!
Ok, this is nasty.. I'm obscuring setting of the global varaible... be careful!
Add the bloat as a parameter
Ok, this is nasty.. I'm obscuring setting of the global varaible... be careful!
Ok, this is nasty.. I'm obscuring setting of the global varaible... be careful!
find.c: Refactor some common sequences into a helper function
parse_y.y: Try to avoid two shift/reduce and reduce/reduce warnings
TODO: Check this matches up against our expected behavior.
Removing the parsedata section ("I think") has no effect, as elements
hit the alternative | element clause within parsepcb.
HOWEVER... I need to check whether there is any other valid syntax
inside an element file, or any backwards compatibility with old formats
which we may miss with the loss of parsedata.
TODO: Check this matches up against our expected behavior.
Removing the parsedata section ("I think") has no effect, as elements
hit the alternative | element clause within parsepcb.
HOWEVER... I need to check whether there is any other valid syntax
inside an element file, or any backwards compatibility with old formats
which we may miss with the loss of parsedata.
Play with grid snapping heuristics a little
Require the pointer to be inside the bounding box of a pin / pad / via before snapping.
This makse it MUCH easier to place vias in a regular grid spaced at the PCB grid spacing.
Require the pointer to be inside the bounding box of a pin / pad / via before snapping.
This makse it MUCH easier to place vias in a regular grid spaced at the PCB grid spacing.
Add hysteresis to grid-snapping
Remove graphics pointer from HID structure
Pass a HID_DRAW * instance to hid_expose_callback() rather than a HID * pointer
Drawing should eventually be independent of the HID
Drawing should eventually be independent of the HID
Fixup draw.c not to special case based on HID name, use flags instead
hidgl: Provide more explicit management of rendering instances
Provide an (hidgl_instance *) pointer which is used to refer to a hidgl
instance when caling hidgl_* APIs that are instance, but not hidGC specific.
Various hidgl APIs now take the hidgl_instance as a parameter, or in the case
of hidgl_new_instance(), return a new instance.
Graphics APIs which previously had a hidGC parameter remain the same, as the
hidglGC structure now contains a link to the hidgl instance which created it.
This change paves the way to potentially having multiple hidgl instances active
simultaneously, and removes various global variables (such as "buffer" and
"global_depth") which were previously accessible to allow the gtk-gl HID to
draw using the hidgl internals.
The gtk-gl HID_DRAW graphics API now subclasses the hidgl HID_DRAW API, so the
gtk-gl HID can access the (non-private) gtk_gc->hidgl_gc.* fields.
Provide an (hidgl_instance *) pointer which is used to refer to a hidgl
instance when caling hidgl_* APIs that are instance, but not hidGC specific.
Various hidgl APIs now take the hidgl_instance as a parameter, or in the case
of hidgl_new_instance(), return a new instance.
Graphics APIs which previously had a hidGC parameter remain the same, as the
hidglGC structure now contains a link to the hidgl instance which created it.
This change paves the way to potentially having multiple hidgl instances active
simultaneously, and removes various global variables (such as "buffer" and
"global_depth") which were previously accessible to allow the gtk-gl HID to
draw using the hidgl internals.
The gtk-gl HID_DRAW graphics API now subclasses the hidgl HID_DRAW API, so the
gtk-gl HID can access the (non-private) gtk_gc->hidgl_gc.* fields.
TEMP: Fixup fallout from nogui change
*** Might be nicer to just implement a no-op end_layer function for each HID_DRAW?
*** Might be nicer to just implement a no-op end_layer function for each HID_DRAW?
push
push
pop
pop
push
push
Demo of exporter specific export routine
XXX: Bitrotten - does not build
XXX: Bitrotten - does not build
refresh
refresh
refresh (create temporary patch)
refresh (create temporary patch)
Refresh of crasy-test
refresh
refresh
refresh (create temporary patch)
refresh (create temporary patch)
Refresh of crasy-test
refresh
refresh
refresh (create temporary patch)
refresh (create temporary patch)
Refresh of crasy-test
Crasy test
Note that this throws away code to draw pad and pin names
XXX: Bitrotten - not up to date w.r.t. BB Vias.
Note that this throws away code to draw pad and pin names
XXX: Bitrotten - not up to date w.r.t. BB Vias.
Crasy test
Note that this throws away code to draw pad and pin names
XXX: Bitrotten - not up to date w.r.t. BB Vias.
Note that this throws away code to draw pad and pin names
XXX: Bitrotten - not up to date w.r.t. BB Vias.
Crasy test
Note that this throws away code to draw pad and pin names
XXX: Bitrotten - not up to date w.r.t. BB Vias.
Note that this throws away code to draw pad and pin names
XXX: Bitrotten - not up to date w.r.t. BB Vias.